Team
Invite people by email, manage pending invitations, remove members, and understand how membership and sign-in work across workspaces.
People belong to an organisation, not to a workspace. Everyone in the organisation can open every workspace in it, build and change pipelines, run them, read data and edit settings. The Team tab in Settings is where you add and remove people.
Membership is organisation-wide
The tab opens with the notice Team is managed at the organisation level. All members of your organisation get access to every workspace in it. Adding or removing someone here affects every workspace, not just this one.
If you need to keep two groups of people apart, put their work in two organisations. From the workspace switcher, Organisations → New organisation creates one; you are its first member and can invite from there. See Workspaces.
Inviting someone
Under Invite team members, a line confirms that new members get access to all of the organisation’s workspaces.
- Type their email address in the field (Email address…).
- Press Invite or Enter. The invitation is sent by email and the address appears under Pending invitations.
- Tell them to look for the invitation email. When they sign in with the invited address, they join the organisation. See How sign-in works for invitees.
An invalid address is rejected with Valid email is required. Invite as many people as you like; there is no seat count.
Pending invitations
An amber Pending invitations card lists every address that has been invited but has not yet accepted, each marked Invitation pending. The Revoke button withdraws the invitation; the link in their email stops working. To send it again, invite the address afresh.
Members
The Members list shows everyone in the organisation: an initial avatar, their name (or the name derived from their email), the email underneath, and (you) on your own row. A small crown marks a Jsonify platform administrator, which is a Jsonify-wide flag rather than something you can grant here.
Remove on another member’s row asks Remove name? and then removes them from the organisation at once. They lose access to every workspace in it. You cannot remove yourself; ask another member, or leave the organisation by moving your work elsewhere.
Roles
Every member has the same rights. There is no owner, editor or viewer role, and no per-workspace permission. Anyone in the organisation can:
Per-workspace roles are not available. If some people only need to read, turn on link access for the workspace instead (Settings → General → Sharing), optionally with a password. Visitors need no account, cannot change anything, and can ask Jason questions. See Sharing a workspace.
How sign-in works for invitees
Sign-in is by email. An invitee does not set a password:
- Open the link in the invitation email. It opens the Jsonify sign-in dialog.
- Enter the invited email address and the six-digit code that is sent to it. The code expires in 10 minutes.
- Add their name the first time (First name required, Last name optional).
Signing in with a verified address accepts every pending invitation for that address at once, and opens the organisation that sent the newest one. Someone who was invited does not get an empty organisation of their own as well. The same happens with Google or single sign-on, as long as the address matches the invitation.
Organisations that require Google, single sign-on or multi-factor authentication are sent to Secure Sign-in automatically; the dialog explains why. See Your first pipeline for the sign-in dialog step by step.
Choosing an organisation
Someone who belongs to several organisations may see Choose your organisation — Your email is verified. Choose where you’d like to continue. after entering the code. Each organisation is listed with its icon and the names of up to two of its workspaces, plus (+n more) when it has others. The one used last is marked Last used and listed first. Organisations with no workspaces are folded behind More (n). Pick one and press Continue.
They can switch organisation later from the workspace switcher. See Workspaces.
Who can do what by email and from other tools
Membership also governs the other ways into a workspace:
| Channel | Who |
|---|---|
| Email to the workspace’s Jason address | Current organisation members only, with a verified sender domain. Others are ignored. |
| Your own agent over MCP | A member who has connected their agent. See Connect your agent. |
| The command line | A member who has signed the CLI in. See Command line. |
| Share link | Anyone with the link, when link access is on: read-only, and they can ask Jason questions. See Sharing a workspace. |