Team & roles

Invite members

1. Open Team in your workspace. Only owners and admins can manage the team.
2. Choose Invite, enter an email address and pick a role (admin, publisher or contributor).
3. The invitee gets an email with a link. Signing in or creating an account from that link adds them to the workspace.

From the same page you can resend or revoke pending invitations, change a member’s role, remove a member and (as owner) transfer ownership to another member.

Roles

Every member can view the workspace, create artifacts, push versions and manage their own AI connections. Beyond that:

	Owner	Admin	Publisher	Contributor
Create artifacts and push versions	Yes	Yes	Yes	Yes
Submit versions for review	Yes	Yes	Yes	Yes
Publish, unpublish, review submissions	Yes	Yes	Yes	No
Create share links, file artifacts under clients and spaces	Yes	Yes	Yes	No
Create and edit clients and contacts	Yes	Yes	Yes	No
Manage members, invitations, branding	Yes	Yes	No	No
Export data, delete the workspace, transfer ownership	Yes	No	No	No

There is exactly one owner per workspace.

Client access levels

Within those roles, you can narrow what a teammate can do on a particular client (or on one of its spaces). Each level includes the ones before it:

Level	Allows
View	Open published work and comment.
Contribute	Also push new versions and edit details.
Approve	Also publish and share with the client.
Admin	Every client. Reserved for owners and admins.

How grants work:

• The role is the ceiling. A grant narrows what a role allows, never widens it. Publishers reach at most Approve, contributors at most Contribute.
• Without a grant, a member keeps their role’s ceiling on that client.
• With a grant, only what it covers is in reach: a whole-client grant covers every artifact of the client; a space grant covers the artifacts filed under that space.
• Ethical walls. Turn on a client’s wall and only members with a grant on that client (plus owners and admins) can see it at all.
• Artifacts with no client are open to every member.

Anything out of a member’s reach simply doesn’t exist for them, including over MCP.

Note

AI connections act as the member who created them, so they inherit both the member’s role and their client access. See Connect an AI tool.