Manage organization team access#

Use organization teams when several organization members need the same project role. This guide is the right path when access should follow membership in a group, such as a release team or project maintainers team. For one person who should keep access even if team membership changes, invite them directly to the project instead.

Add people to a team from the organization, then grant that team access from each project’s Members page.

Before you start#

You need:

  • an approved organization

  • Owner access to the organization

  • the users already added as organization members

  • at least one Sysand project in the organization namespace

Organization managers can view teams, team membership, and project access. Only organization owners can create teams, change team membership, or change project access. For the role details, see Roles and permissions.

Create a team#

  1. Go to Organizations.

  2. Open the organization you want to manage.

  3. Open Teams.

  4. Under Create team, enter a team identifier such as release-team.

  5. Optionally enter a display name, such as Release team, and a description that explains who should be on the team.

  6. Press Create team.

The team appears in the organization teams table. A new team does not provide project access until you add members to it and grant it access to a project.

Add organization members to the team#

  1. Open the team from the organization teams table.

  2. Under Members, choose an existing organization member from Add organization member.

  3. Press Add member.

  4. Repeat for each person who should receive this team’s project access.

A team can contain only current organization members. If the user is not in the selector, invite them as an organization member and wait for them to accept before adding them to the team.

Add team access to a project#

Organization owners add an existing team to a project from that project’s Members page. Starting from the project keeps the project context visible while choosing access.

  1. Open the project’s Members page.

  2. Under Add team, choose an organization team.

  3. Select the project role:

    • Owner for people who should manage project members, trusted publishers, settings, and deletion.

    • Maintainer for people who should upload releases and manage project tokens without full project ownership.

  4. Press Add team.

Team project access is additive. It does not create direct project membership and it does not remove any direct project role the user already has.

Verify access#

Use checks that do not make further changes:

  1. On the team page, confirm the project appears under Projects with the expected role.

  2. Open the project’s members page and confirm the team appears under Teams.

  3. Ask a team member to open Projects and confirm the project appears there with their effective role.

If a user has both direct project access and team access, Sysand Index uses the highest project role; see Roles and permissions.

If someone cannot publish#

Check the access path before changing credentials:

  1. Confirm the user is a current organization member.

  2. Confirm the user is on the intended team.

  3. Confirm the team appears on the project’s Members page under Teams.

  4. Confirm the team role, or the user’s direct project role, is Owner or Maintainer.

Organization Owner access by itself does not grant upload or project-token access; see Roles and permissions.

Change or remove access#

To change a team’s project role, open the project’s Members page and update the role in Teams.

To remove team-derived project access, remove the team from Teams on the project’s Members page. Team members keep their organization membership and any direct project membership they already had.

To remove one person’s team-derived access, remove that organization member from the team. This does not remove them from the organization.

Recover from owner-continuity blocks#

Sysand Index blocks changes that would leave a project without an effective Owner; the full list of blocked changes is in Roles and permissions. If a team change is blocked, first add or promote another Owner path on the affected project’s Members page (a direct project Owner, or Owner access through another team), then retry the change.