Skip to content

Teams and access

Last updated:

On Codebahn, access to repositories is managed through organizations and teams. You invite people to your organization, assign them to teams, and teams control what they can do in which repositories.

Crew organizations support teams, member management, and fine-grained permissions. Everything on this page applies to Crew.

Solo accounts are single-user. Repositories under your Solo account are yours alone; there is no way to grant another person access. If you need to share repositories, create a Crew organization.

A team is a named group of people with a shared set of permissions on a set of repositories. Every organization starts with an Owners team. You create additional teams for different roles.

OwnersCustom teams
CreatedAutomatically with the orgBy any org owner
PermissionsFull access to everythingYou choose per feature
RepositoriesAll current and futureAll, or specific repos you pick
Can create reposYesOptional
Can be deletedNoYes
Minimum members10

The Owners team cannot be renamed or deleted. The organization must always have at least one owner.

Each team has an overall permission level:

  • Read. Clone and browse code, view issues and pull requests.
  • Write. Everything Read allows, plus push (subject to branch protection), create and edit issues and pull requests, and trigger CI.
  • Admin. Everything Write allows, plus repository settings, branch protection rules, and managing team membership for the repo.

Teams below Admin can set permissions independently for each repository feature:

FeatureWhat it controls
CodeClone, browse, push
IssuesView, create, edit, close
Pull RequestsView, create, review, merge
ReleasesView, create, edit
PackagesView, push, delete
ActionsView CI runs, approve, re-run

Each feature can be set to None, Read, or Write independently. A team with Write on Code but Read on Issues lets members push code but not edit issues. Admin teams get Admin on all features; the per-feature settings do not apply.

When a person belongs to multiple teams with different permissions on the same repository, the highest level wins, resolved per feature.

Each team covers either:

  • All repositories, including ones created after the team. New repos are automatically accessible.
  • Specific repositories that you select from the team’s repository tab.

A repository can belong to multiple teams.

Invites are team-bound. To add someone:

  1. Open the team you want them to join
  2. Go to the Members tab
  3. Enter their Codebahn username or email address

They receive an email with a link to accept. Accepting adds them to the team and to the organization. For email invitations, the recipient must have that address verified on their Codebahn account.

Removing someone from all teams removes them from the organization.

Small team, everyone contributes to everything. One team with Write on all repos. The Owners team handles settings.

Developers and ops. A “Developers” team with Write on Code and Pull Requests, Read on Actions. An “Ops” team with Admin on deployment repos, Read on the rest.

Contractor on two repos. A team scoped to specific repositories, with Write on Code and Pull Requests, None on everything else. Remove the team or its members when the engagement ends.

Read-only stakeholder. A team with Read on all repos. They can browse code and follow issues without write access.

The org’s Members tab shows everyone with access to your repositories and which teams they belong to. Because all access goes through organization membership:

Git history records every push. CI logs are retained for 90 days. Deployment events are logged when you use environments. Membership, team, and policy changes are recorded in the security log and audit log. Codebahn does not offer audit log streaming.