People and access

Access in Jinn works at two levels. Being in the workspace gets you in the door. Being on a project gets you to its content — unless the project is open to everyone in the workspace, in which case the door was already unlocked. You can use Jinn alone and never touch any of this. It matters the moment a second person needs to see a meeting.

Invite someone to the workspace

Workspace owners and admins can invite people. Click Invite in the workspace menu, or open Settings → Members and click Invite members. Both open Invite team members, with two ways to bring people in:

• Email Invite — type one or more addresses, separated by commas, and click Send Invites. Jinn reports how many went out, and lists any address that was already invited.
• Invite Link — pick how long it lasts under Link expiration, from 1 to 30 days, click Generate, then Copy and send it however you like. Anyone with the link can join until it expires. To stop it working sooner, click the ✕ beside the link.

To invite a whole list at once, click Import CSV on Email Invite and pick a .csv file with one email per row. With a header row, two optional columns are read too: name, and role with member or admin. A blank role means member, and anything else is invited as a member. One file takes at most 512 addresses; split a longer list. Only the workspace owner can invite admins. If an admin imports a file with admin rows, Jinn refuses it with Only the workspace owner can invite admins. Change those rows to member, or ask the owner. You can also invite someone straight into a project: type their whole email address in the project’s Share window, as described in Share a project. That needs Full access on the project as well as workspace admin rights. Whichever way you invite, people arrive as members of the workspace. They can see open projects, and nothing else until you add them somewhere. Until they accept, they’re listed as Pending under Settings → Members; Revoke invitation in their row’s menu cancels the invitation.

Private and open projects

Every project is one or the other, chosen when you make it and changeable later. Private — only you and the people you add. Someone in the workspace who isn’t on it can’t find it or open it. Open — anyone in the workspace can find it and work in it. Nobody needs adding; being in the workspace is enough. Open is the right default for work your team should stumble across. Private is for the project you’d be uncomfortable about a colleague opening by accident.

Access levels

Three levels, and the labels say what they mean: In an open project, everyone in the workspace gets Can edit unless you say otherwise. That’s the setting under General access in the project’s Share window — Everyone at your workspace, with Can edit or Can view — and it’s worth a look before you put anything sensitive in an open project. Full access is never handed out automatically. Even in an open project, managing members is something you grant to a named person. Nobody inherits it.

Share a project

Everything about who reaches a project happens in one window. Click Share next to the project’s name — or on its card in the projects list — and Share and the project’s name opens.

1. In Add people by name or email, start typing a name. Pick people from the workspace, or an agent to put it on the project.
2. To bring in someone who isn’t in the workspace yet, type their whole email address and pick Invite with their address. They get an invitation to the workspace and to this project at once. Until they accept, they’re listed as Invited.
3. Choose the access level for everyone you picked, and click Invite.

Under People in this project you see who’s on it and at what level; open View all for the full list, split into All, Workspace and Agents. Change a level from the list, or remove someone with Remove access — Jinn confirms first, because it’s not obvious from the outside what someone loses. Agents in this project works the same way, with Remove from project. General access at the bottom decides who else can open the project: Private, or Everyone at your workspace with Can edit or Can view. Copy link copies the project’s address and tells you who can open it. To step out of a project yourself, choose Leave project. In a private project, someone with Full access has to add you back.

When someone can’t open something

Two messages mean two different things. You do not have permission to access this resource — they’re not on the project, or the project is private and nobody added them. You do not have permission to perform this action — they’re on it, but at a level that doesn’t allow what they tried. Usually Can view where Can edit was needed. Agents are separate again. Only workspace admins can create, edit and delete them. Putting an agent that already exists on a project, or taking it off, needs Full access on that project — a workspace admin who isn’t on the project can’t do it. See managing agents.

Where to go next