Team

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:

1. Type their email address in the field (Email address…).
2. Press Invite or Enter. The invitation is sent by email and the address appears under Pending invitations.
3. Tell them to look for the invitation email. Accepting it creates their account (or links an existing one) and adds them to the organisation.

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:

• create, rename, move and delete workspaces,
• chat with Jason and change pipelines,
• run pipelines and change schedules,
• read, query, export and share datasets,
• edit settings, including the monthly collection cap and the Jason email allowlist,
• invite and remove members.

Per-workspace roles are not available. If you need read-only access for some people, share a public link to specific resources instead (Settings → General → Sharing); viewers of a share need no account and cannot change anything.

How sign-in works for invitees

Sign-in is by email. An invitee does not set a password:

1. Accept the invitation from the email. It opens the secure sign-in page.
2. Enter their email address and the six-digit number that is sent to it.
3. Add their name the first time (First name required, Last name optional).

The next time they sign in, the organisation is already in their switcher. Someone who belongs to several organisations chooses one at sign-in (the last one used is marked) and can switch later from the workspace switcher.

Organisations that require Google, single sign-on or multi-factor authentication are sent to the hosted secure sign-in page automatically; the email flow explains why. See Your first pipeline for the sign-in dialog step by step.

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.
Public share link	Anyone with the link, read-only.

What’s next