Teams and project permissions
Invite teammates and distinguish organization access from project roles.
An organization owns the subscription and its team. A project has its own membership and testing configuration. Manage both scopes deliberately.
Invite an organization member
- Open Account settings → Team.
- Enter the teammate's email and choose an available role.
- Send the invitation and have the teammate accept it.
- Check the membership state after acceptance.
Pending invitations and enabled accounts are different states. If an invitation does not arrive, check the address, mail filtering, and any displayed limits before sending another copy.
Add project access
Open Project setup → Members. Add an existing teammate or invite someone to the project, and choose Admin, Member, or Viewer as appropriate.
Use the least access the person needs for their work. Review memberships when a teammate changes responsibilities or leaves the team.
Understand ownership
The organization owner handles subscription changes. Project administrators manage the project actions available to their role. Membership in one project does not establish access to another.
If an action returns a permission error, confirm the selected organization, project, and role with an administrator. Plan seat limits and role permissions are separate checks.
Review organization controls
Use the available two-factor and SSO settings to configure team sign-in. Check Audit logs when investigating membership or configuration changes.