User Permissions
Permissions on GitHub
Qlty Cloud uses a GitHub App to integrate with GitHub. The installation and authorization of the GitHub App occurs on the GitHub side based on GitHub Organization settings. Depending the GitHub organization’s settings, an approval step may be necessary on the GitHub side.
All authentiction uses GitHub OAuth, and we use the GitHub identity of the user to determine access to Qlty Cloud as described below.
Repository selection
The GitHub App can be installed with access to either all repositories within the organization or selected repositories. Updates to the repository selection can be done at any time on the GitHub side. Qlty Cloud can only access repositories that it has been authorized to access on the GitHub side.
Migration from Code Climate Quality
In order to ease migration from Code Climate Quality, Qlty Cloud will attempt to use the Code Climate GitHub OAuth App when needed to access repositories that were previously authorized to Code Climate Quality.
For the best experience, we recommend that you authorize the new Qlty Cloud GitHub App as soon as possible. Once you have authorized the new Qlty Cloud GitHub App for all of the repositories you want to use with Qlty Cloud, you can remove the legacy Code Climate Quality GitHub OAuth App from your GitHub organization.
Workspace-level permissions
Workspaces correspond to GitHub organizations or user accounts. For Workspaces corresponding to GitHub users, the user has full access to the workspace.
For Workspaces corresponding to GitHub organizations, permissions are determined by the GitHub permissions as described in this table:
Project-level permissions
Projects correspond to GitHub repositories. Permissions are determined by the GitHub repository role as described in this table:
* Only GitHub Repositories that have been authorized for access by the GitHub App