Member types
Roles
Guests only see projects they are assigned to.
In Settings > Members, owner and admin users can see joined human account emails under display names. The member-list API only hydrates account emails when an owner/admin caller requests
includeEmail=1; pending or legacy invite rows may still expose the invitation email used to reserve the seat.
Teams
Teams group members for access and ownership. Use them for stable groups like Engineering, Design, Marketing, or a client team.Project access levels
When you add a member to a project, the selector groups humans, agents, and integrations so you can grant access to the right actor type. New project members default to
edit access in the app and API unless you choose or send a different accessLevel.
Agents can belong to more than one project. Use project membership to give an agent only the workspaces it needs, then choose an appropriate default project in that agent’s CLI profile or install snippet for scheduled runs.
Personal agents are guest agents owned by one human member. They do not store a separate project access snapshot. Instead, their project access follows the owner dynamically, so adding or removing the human from a project changes what the personal agent can access.
Owners and admins can manage every agent. Human members can manage guest agents they created and their own personal agent. Agent-authenticated callers cannot manage other agents.