Roles and Permissions

Codity combines provider permissions, the active account scope, Codity account roles and feature-specific access. Repository visibility alone does not authorize every dashboard action.

Access Model

  1. Provider identity and scope: provider-backed actions use the signed-in provider and selected account. Repository operations check the relevant account and enabled/access-eligible repositories.
  2. Provider permissions: GitHub installation permissions, GitLab project roles, Azure organization rights or Bitbucket workspace permissions determine what provider API calls can do.
  3. Codity access: account membership, seats, Analytics/admin access and plan availability control additional operations.

A token's scopes cannot grant access the token owner does not have. Conversely, being a provider organization owner does not replace a missing token or every feature-specific Codity access grant.

User Roles

Provider Account Users

Use VCS sign-in for repository and team workflows. Select the correct personal account, organization, group or workspace. Repository settings and data access remain subject to the feature's account/repository checks.

Installing the GitHub App or managing provider webhooks may require a provider administrator. Those provider permissions differ from a Codity email organization role.

Codity Account Admin

An admin in a Codity email organization can manage its permitted subscription, member invites, seats and CLI Analytics. API key management also requires subscription/account administration access. See Codity Accounts.

Codity Account Member

A member uses the CLI features available to their assigned seat. Email membership does not create a GitHub/GitLab/Azure/Bitbucket provider session or grant the member arbitrary repository access in the dashboard.

Account Administration and Analytics Access

Some shared mutations require Codity account-admin access: for example changing shared agent policies, modifying protected merge policy, spending or topping up Wallet, and managing self-hosted GitLab connections. Personal scope is treated separately from shared organization scope. For a shared account, the required Analytics/admin grant must be associated with that account.

Subscription and seat administration also checks the provider/account's ownership or administration rules, or an applicable granted account-admin tier. Do not assume the same rule applies to every Settings tab.

Permission Scopes

Task What to check
Read repository data or change repository settings Correct provider/account and repository scope; enabled/access-eligible repository
Install the GitHub App GitHub installation approval and selected repositories
Enable a hosted provider repository Correct account, usable credentials and provider webhook permissions
Enable a self-hosted GitLab repository Instance/scope connection, account-admin access and provider project rights
Create a Codity team Authenticated VCS account with a usable selected scope; repositories must be allowed in that account
Change shared agent policies or protected merge policy Account-admin authorization for that active account
Manage subscription, members or API keys The corresponding account/subscription administration authorization
Use a paid feature Applicable plan, seat and usage availability as well as operation permissions

Team creation does not require a separate Codity team-creator role. A team does not grant repository access, and adding a repository from another customer's account is rejected.

Common Permission Issues

Repository Not Found

Check the provider, selected account, repository connection and token/App access. A repository visible through another provider account is not necessarily in the current account's scope.

Cannot Configure Settings

Read the specific error and identify the operation. A read-only integration panel may need its configuring account; a protected policy change may require account-admin access. Broad advice to obtain repository admin rights does not resolve every Codity authorization failure.

Cannot View Metrics

Check the selected account/team, connected repositories and feature access. Analytics requires the applicable plan and seat access; empty metrics can also mean ingestion has not produced data yet.

Access Control Best Practices

Keep provider membership and Codity seat/admin grants current independently. When reporting an access problem, include the feature, provider, selected account and error message, without credentials.

Permission Examples

Repository Access Without Account Administration

A developer can read a company repository in the provider but receives an account-admin error when changing a shared agent policy. Check the account-admin grant for the selected Codity account. Granting broader repository access does not resolve that separate authorization check.

The same distinction applies when spending shared Wallet funds or changing protected merge policy. Personal-account scope has separate handling; do not use personal-account behavior as evidence of organization-wide access.

Account Administration Without Provider Write Access

An authorized Codity account administrator can configure a merge gate, but the provider identity may still lack permission to make its status check required in the repository's branch rules. Configure both parts with an appropriately authorized identity. See Merge Gates.

Similarly, a valid GitLab PAT can identify its owner and list projects while webhook creation fails for one project. Verify the owner's rights on that project as well as token scopes.

Email Membership Without a Provider Session

An invited member of a Codity email organization can use features available to their assigned seat. This invitation does not create a provider-backed repository session. Follow the provider sign-in and onboarding flow for repository workflows; do not assume an email organization role grants access to a similarly named VCS organization.

Resolving an Access Error

  1. Record the action that failed, such as enabling a repository, saving a policy or creating an API key.
  2. Confirm the provider identity, active account and self-hosted instance where applicable.
  3. Check repository membership and the integration credential's access for provider operations.
  4. Check the action's Codity seat/admin authorization and plan feature independently.
  5. Retry the specific action after the relevant access changes, then verify the saved state or completed result.

For example, if reading review results succeeds but updating a shared policy returns admin_required, investigate the account-admin grant. If enabling a repository returns a provider permission error, investigate webhook rights. These failures have different owners and remedies.

Reviewing Access Over Time

When someone changes teams or leaves, review provider membership, Codity seats/admin grants and shared credential ownership. Removing a Codity team member does not remove provider access. Removing an active seat does not itself reduce purchased capacity or billing; see Managing Seats.

For a suspected credential exposure, use the issuer's revocation process and check affected integrations. For planned rotation, verify the replacement before retiring a still-needed credential. See API Keys and Tokens.