How it works Docs Prices
Login Sign up
Browse documentation

Teams and membership

A team is an organization-scoped group of existing Codinamo users. Teams reduce repeated access assignments: grant a role to the team and every current member receives that access.

Teams do not contain workspaces. A team can receive different roles on multiple workspaces, projects, pipelines, or other resources in the same organization.

Create a team

  1. Select the organization in the context switcher.

  2. Open Teams.

  3. Enter a name and, optionally, a slug.

  4. Select Create team.

Team slugs are unique inside the organization. They contain lowercase letters, numbers, and internal hyphens. The canonical team identifier begins with TEM-.

Creating and changing teams requires the corresponding team and membership permissions. A user without management permission can still inspect teams made visible by their assigned roles.

Add members

  1. Open the team.

  2. In Add member, enter the email address of an existing Codinamo account.

  3. Select Add member.

Adding a user to a team also makes the team a source of effective access for that user. Codinamo does not expose the role’s protected data merely because the user can see the team name; every operation is still authorized against the effective permissions.

The account must already exist. Team membership is not an invitation mechanism.

Remove a member

Open the team and select Remove beside the member. Removing a member immediately removes access supplied by that team, but preserves:

  • the user’s organization membership;

  • roles granted directly to the user;

  • access received through other teams.

Review effective access before removing a member when the team controls production or credential-related resources.

Grant access to a team

There are two equivalent starting points:

  • open Access > People & Teams, select the team, and choose Grant access;

  • open Access > Resources, find the resource, and choose Grant access.

Select a role, scope, and optional expiration just as you would for an individual user. The resulting grant has its own canonical GRA- identifier.

Team management and resource access are independent. Permission to add members to a team does not automatically grant that team access to projects or pipelines.

See Manage access for the complete grant workflow.