Workspaces and teams
Keep repository security work with the right team, manage invitations and roles, and review your organization's security agreement.
Choose the workspace before you actPermalink to Choose the workspace before you act
Your personal workspace and an organization's workspace are separate contexts. Repositories, scans, findings and notification destinations belong to the selected workspace. Check the workspace switcher before connecting a source, starting a scan or creating an automation rule.
An organization keeps its security work with the team. Changing a person's membership does not transfer the organization's repositories or assessment history into that person's personal account. If expected work is missing, first check the selected workspace and your membership rather than creating a duplicate connection.
Give people the access they needPermalink to Give people the access they need
| Role | Team administration |
|---|---|
| Owner | Manage the organization and accept its security agreement. Owner roles are not edited from the team roster. |
| Admin | Manage invitations and eligible members, including changing member/admin roles. Cannot accept the security agreement on behalf of the owner. |
| Member | Access the workspace according to membership, view the roster and leave the organization. |
Organization roles do not grant permissions at GitHub, GitLab or Bitbucket. A repository must also be accessible through its source connection. If a source action is refused, check the relevant connection rather than broadening every teammate's role.
Invite and maintain your teamPermalink to Invite and maintain your team
Select the organization
Open Settings and choose the organization team or invitations screen.
Invite the person
As an owner or admin, enter their email and the appropriate available role. A pending invitation does not grant access until accepted.
Review the roster
Confirm membership after acceptance and review access when people change responsibilities.
Remove access when it is no longer needed
Remove an eligible member from the team screen. Members can also leave; their organization work stays in the organization. The last owner must arrange another owner before leaving.
Review the security agreementPermalink to Review the security agreement
Organization settings includes the security agreement when it is available for the organization. An owner reviews the current documents and plan before accepting. Other roles can read the agreement, but cannot accept it on the owner's behalf. If the documents change, review the current version rather than relying on an older acceptance.
Owners and admins can download the acceptance receipt when the current agreement offers one. Use the actual documents and receipt for procurement or security review; product documentation is not a replacement for your agreement.