Organizations and Teams

Codity separates the active account from the active team. Choose the account first, then a team inside it.

Organizations in Codity

Sign-in Account scope
GitHub Personal account or selected organization
GitLab.com Personal projects or selected group
Self-hosted GitLab Instance plus personal projects or selected group
Azure DevOps Selected Azure DevOps organization
Bitbucket Selected workspace
Codity email account Codity organization membership

The provider, account and, for self-hosted GitLab, instance identify the data scope. Matching repository or organization names on another provider do not grant access.

Switching Between Organizations

After provider authorization, complete the welcome flow and select the offered account scope. From the dashboard, open the account menu and use Switch Account to select another available account. Some provider changes use a dedicated selection screen.

Check the active account after switching. Repository listings, team records and supported account settings follow that selection. Configure credentials for the intended provider/account; changing a team does not change credentials.

Multi-Organization Access

An identity can belong to several provider accounts. Codity operates in the selected one rather than exposing a combined organization-wide view across every account you can reach. Subscription, seats, policies and repository enabling remain associated with their account; switching does not transfer them.

For GitLab, personal projects and group repositories are different scopes. For self-hosted GitLab, the instance also matters. Follow the self-hosted guide before choosing a group.

Team Access

A Codity team groups developers and repositories for supported views and analytics. It is not a provider team or a grant of repository permissions. Adding someone to a Codity team does not add them to a GitHub organization, GitLab group, Azure project or Bitbucket workspace.

Use the team switcher to select a team or All repos inside the active account. Team repository operations still check account/provider scope. See Creating and Managing Teams.

Organization-Level Settings

Settings can apply to the active account or an accessible repository. The controls and authorization depend on the feature. Shared agent policies, merge policy, subscription management and ordinary review settings do not all share one universal permission rule. See Roles and Permissions.

Common Scenarios

Personal and Company GitHub Repositories

Suppose you use Codity for a personal project and for repositories owned by example-company:

  1. Complete GitHub sign-in and select the account you intend to configure.
  2. Install or authorize the Codity GitHub App for that account and select the intended repositories. A personal installation does not grant access to the company's repositories.
  3. Open the dashboard account menu and use Switch Account when moving between the personal and company scopes.
  4. Verify the current account before changing review settings, creating teams or managing subscription seats.

The company's teams and usage remain associated with the company account. Selecting a company team does not move a personal repository or its credentials into that account.

GitLab Personal Projects and Groups

If your GitLab identity can access both personal projects and a group, choose the intended personal/group scope after authorization. Configure the applicable PAT and enable projects through GitLab Repositories.

A token may see projects outside the currently selected group. That visibility alone does not make them part of the active Codity account. If enabling a project fails, compare the project's namespace with the selected account and check the token owner's project rights.

For self-hosted GitLab, check the instance as well as the scope. A group named engineering on one instance is different from a group with that name on another instance or GitLab.com.

Multiple Azure DevOps Organizations

Select the intended Azure organization before opening Manage Repositories or managing its shared PAT. Check that the token and repository belong to that organization. Switching to another organization does not transfer enabled repositories, purchased seats or account settings.

Use the Azure DevOps guide for the token form and replacement rules. A member who can view an organization is not necessarily allowed to replace its shared token.

Teams Within One Account

For example, the company account can contain separate Payments and Infrastructure teams. Select Payments to filter supported views to that team's repositories, then select All repos to return to the account-wide view. The active provider account stays the same.

Adding a developer to Payments changes the Codity team's membership. Grant any required provider repository access separately. See Creating and Managing Teams for repository assignment and branch-conflict behavior.

Account Administration Checklist

  • Confirm the current provider/account before changing shared configuration.
  • Maintain provider membership, Codity seat assignments and account-admin grants independently.
  • Record who manages shared credentials and their expiration without recording the secret in documentation.
  • After repository transfers or membership changes, verify repository visibility and a permitted review in the intended account.
  • Review teams and repository assignments inside each account rather than assuming a global team list.

Troubleshooting

Account missing: check provider membership and the identity used to sign in. Reauthorize if membership or OAuth access changed.

Repository visible elsewhere but rejected here: confirm the active provider/account and, for self-hosted GitLab, instance. A different account's access does not transfer automatically.

Team disappeared after switching: return to the account where it was created. Teams are scoped to accounts, not global personal shortcuts.

Account appears but settings cannot be changed: identify the exact setting and its authorization error. Provider membership, an Analytics seat and account administration are distinct checks. Ask the administrator for that account to verify the relevant grant.

Same repository name appears in two places: compare the provider, owner/namespace and instance before selecting it. Names alone do not identify the account scope.