Skip to main content
Providers are connected through the Console using Connected Apps, Credentials, Connectors, and each repository detail page. The recommended path is Connected Apps whenever the provider offers one, because the Console can track authorization, status, and reauthorization for you. Connecting a Connected App is an authorization handoff, not an app registration. Acrity publishes and manages the provider app (the GitHub App, the GitLab or Bitbucket OAuth app, the Azure DevOps app registration, and so on) per deployment. You never create an app, configure a callback URL, or grant individual API permissions yourself. You sign in on the provider, choose the account or organization, select the repositories the app may reach, and approve.

​
Choose a connection method

Most providers connect through a Connected App. Use a manual credential or a local connector only when a Connected App does not fit.
MethodBest whenWhere
Connected AppThe provider offers an official app or OAuth. Preferred for centralized authorization and reauthorization.Console > Connected Apps
Manual credentialThe use case needs a specific token, password, or app password.Console > Credentials
Local connectorThe VCS is private, self-hosted, or must be reached from your own network.Console > Connectors
Credentials and Connectors require a Workspace admin (platform admins also have access). Roles are fixed capability sets defined by Acrity, so no other role can create or manage them. See Credentials and Connectors.

​
Connect a provider

Pick the provider below. In every case the flow is the same: open Connected Apps, get redirected to the provider, choose the account or organization, select repositories, and approve. Acrity manages the underlying provider app for you.
Use the GitHub App to connect GitHub Cloud accounts and organizations.
1

Open Connected Apps

Go to Console > Connected Apps and choose the GitHub App.
2

Authorize on GitHub

Acrity redirects you to GitHub. Sign in if prompted.
3

Choose the account or organization

Select the personal account or organization where the app should be installed.
4

Select repositories

Choose all repositories or a specific subset the app may access. You grant access to the app Acrity already publishes—there is nothing to register.
5

Approve and return

Approve the requested access. GitHub returns you to the Console; confirm that the installation appears as active, then connect the target projects in Console > Repositories.
The GitHub App is registered and managed by Acrity per deployment. You never create the app or configure a callback URL.
If Acrity is used as a merge gate, configure GitHub branch protection rules to require the check published by Acrity.

​
Validation checklist

After connecting a provider:
  1. Confirm that the installation appears as active in Console > Connected Apps.
  2. Connect at least one repository in Console > Repositories.
  3. Open the repository detail page and validate credentials, webhook, and readiness.
  4. If a PM integration is present, confirm task fields, comments, and project linking.
  5. Open a test PR or MR and track the first review in the Ops dashboard (see Review flow).