Team members and permissions
Invite teammates, manage pending invitations, and distinguish workspace-wide administrators from project-scoped members and viewers.
View as MarkdownTeam Members shows the people who can access the selected project, including workspace owners and admins. Before inviting someone or changing access, confirm both the selected project and the intended role.
Understand role scope
| Role | Access and responsibilities |
|---|---|
| Owner | Workspace-wide project access and administration. Owner entries do not have role or removal controls on this page. |
| Admin | Workspace admins can access every project and manage workspace billing and team access. |
| Member | Can view and edit the project they were invited to; cannot manage project settings, billing, or team access. |
| Viewer | Read-only access to the project they were invited to. |
Inviting an Admin grants workspace-wide access. Inviting a Member or Viewer grants access only to the selected project. Those invitations do not give access to unrelated projects.
Only workspace owners/admins can grant workspace admin access. A project-only administrator does not automatically have authority to manage the entire workspace's billing or administrators.
Invite a member
- Open Team Members for the intended project.
- Choose Invite member.
- Enter Email address.
- Choose Role, checking the scope above.
- Choose Send invitation.
The invitation appears in the pending list until accepted, revoked, or expired. It is not the same as an active member. Invitations expire after seven days.
Synthetic example: invite a fictional analyst to the example project as Viewer if they only need to review its results. Choose Member if they should maintain prompts and competitors. Do not choose Admin merely to avoid a missing project permission.
You cannot invite a new Owner through this role selector.
Manage pending invitations
- Resend sends a replacement invitation with a new expiry. Ask the recipient to use the latest message.
- Revoke withdraws a pending invitation. It does not remove someone who already accepted and has active membership.
A project-only administrator cannot manage workspace Admin invitations. If an invitation is unavailable to manage, ask a workspace owner/admin rather than sending a second higher-privilege invitation.
Change a member's role
Use the member's role control, then review the result in the list. Role changes are access changes, not just labels.
- Promoting a person to workspace Admin gives access across the workspace.
- Demoting a workspace member to project Member or Viewer replaces workspace-wide access with the selected project's access.
- You cannot change your own role here.
- Owner entries do not expose role changes on this page; do not use it as an ownership-transfer workflow.
Confirm the intended outcome with the team before using demotion to restrict access. For billing administration, the relevant permission is workspace owner/admin—not simply access to a project.
Remove a member
Use the removal action and confirm the intended person and scope:
- Removing a project-only member removes that person's access to the selected project.
- Removing a workspace member removes their workspace membership and project memberships throughout that workspace.
You cannot remove yourself using this control. Owner entries have no removal action on this page.
If the person also connected an AI assistant, future data access is checked against their current permissions. Review AI Assistant Access when ending an assistant connection; revoking access cannot retrieve information already shared.
Troubleshooting
- Missing project after acceptance: confirm the account email and that the invitation targeted the correct project.
- Pending invite not working: check whether seven days have elapsed, then resend and use the latest link.
- Admin option unavailable: the current account may not have workspace administration rights.
- Cannot change your own role: ask another authorized owner/admin.
- Viewer cannot save: read-only access is intentional; an authorized admin must change the role if editing is needed.
- Unexpected users in a project: workspace owners/admins have access to all workspace projects and can appear alongside project members.