Roles
Sharing a resource with someone gives them access to that resource only. It never moves the
resource out of your team or exposes your team’s credentials and files.
Invite people
In Settings → Members, admins select Invite members, paste email addresses as a column or separated by commas, choose a Role, and send the invitations. Each person gets an email to join the team. Pending invitations are listed on the same page, where admins can revoke them. To give someone access to a single taskset without adding them to the team, invite them to the taskset instead.Manage members
Settings → Members lists everyone on the team. Search by name or email, filter by role, and sort by date added or role. Your role shows your own. Admins change a person’s role or remove them from their row, or select several people to:- Set role to Admin, Member, or External.
- Add to project, with a project scope.
- Copy emails.
- Remove them from the team.
Team settings
Settings → General holds the team’s logo, name, slug, and ID. The slug is used in invitations and team references; the ID is the team’s UUID for API calls and integrations. Only admins can change them. The other team settings have their own pages:API keys and secrets
Keys for the CLI, SDK, and API; secrets and provider keys for runs.
Billing and usage
Plans, credits, usage, and spend limits.
Limits
Rate limits, runtime caps, and size limits.