Learn how to manage access to your Chromatic account and projects.
Sign in to Chromatic via OAuth, email, or SSO.
Chromatic supports the cloud versions of GitHub, GitLab, or Bitbucket on our self-serve plans.
What OAuth scopes does Chromatic request?
Depending on your Git provider, Chromatic will request a set of OAuth scopes when you first sign in. Chromatic uses these permissions to enumerate your list of repositories, set PR statuses, and retrieve users for assignment to review. Chromatic will never read/write source code.
|Git provider||OAuth Scopes|
What permissions does the GitHub App request?
Chromatic’s GitHub App enables UI Review for pull requests. We need additional permissions to access pull request information and add PR checks.
- ✅ Read access to metadata
- ✅ Read and write access to checks and pull requests
- ✅ Read access to organization members (for collaborators)
- 🔒 We do not request access to your code
How do I request access from my GitHub organization admin?
Chromatic requests the minimum permissions needed to use the tool. With GitHub, we request permissions for “OAuth” and “GitHub app” respectively. This allows organizations to expand permissions incrementally as they use more features.
If your GitHub organization requires an admin to approve apps, you’ll need to request access inside of Chromatic and track their status inside of GitHub (below).
Email and password authentication is available on all accounts. It’s a popular authentication method for external collaborators like designers, PMs, and other stakeholders.
If you’re setting up Chromatic for your team as the account owner or administrator, there are some boundaries to be aware of:
- Email accounts can use Chromatic as normal
- Collaborators are manually managed
- Pull request checks are manually setup via your CI system
We recommend signing up with email for projects that are not on GitHub, Bitbucket, or GitLab. For example, projects on services like Azure DevOps, AWS, etc. Read the setup instructions for these types of projects here.
Single Sign-On (SSO)
Single Sign-On (SSO) is available to enterprise customers. To sign-in, make sure to navigate to your team’s custom Chromatic URL, for example,
If you don’t know the Chromatic URL for your team, you may need to ask the account or project owner.
A Chromatic organization mirrors its counterpart GitHub Organization, Bitbucket Group, or GitLab Team. Open the account menu to swap between organizations or add a new organization.
There are two types of Chromatic projects: linked and unlinked.
Linked projects are associated with a repository on GitHub, Bitbucket, or GitLab. That allows Chromatic to sync collaborators, badge pull requests, get pull request metadata for UI Review, and keep track of UI Test baselines.
By creating a linked project in Chromatic, you automatically have at your disposal:
Collaborators synched automatically based on your Git provider.
The visibility of your published Storybook will be synced with the visibility of your GitHub repository
UI test notifications are enabled via automated webhooks for third-party integrations.
Automated PR badging is configured automatically via OAuth permissions granted by the Git provider.
Chromatic’s GitHub App provides a faster UI review process and PR metadata retrieval.
Improved handling of rebasing and squash & merge commit strategies enabled with Chromatic’s GitHub App.
You can link a project during the project creation process or afterward on the project’s Manage page within the Collaborators tab.
An unlinked project is perfect for teams that self-host Git or have enterprise Git providers (that aren’t on Chromatic’s enterprise plan). Unlinked projects are not linked to a repository on GitHub, Bitbucket, or GitLab. They do not automatically sync collaborators or badge pull requests.
The characteristics of an unlinked project include:
- You’re using an email/password account OR a personal OAuth account.
- Chromatic runs as a CI-only job.
- Collaborators are manually managed via an invite list.
- PR badging is manually configured in your CI provider.
- Notifications are manually setup via Chromatic’s custom webhooks.
Learn how to create an unlinked project here.
How do I create an unlinked project on my existing GitHub, Bitbucket, or GitLab account?
- ❌ You can’t create unlinked projects on GitHub org, Bitbucket workspace, or GitLab group connected accounts.
- ✅ You can create unlinked projects on personal GitHub, Bitbucket, or GitLab accounts.
- ✅ You can create unlinked projects on email/password accounts.
If your account is currently connected to a GitHub org, Bitbucket workspace, or GitLab group, you’ll need to create a new email/password account to set up an unlinked project. Your teammates can access this account by sharing credentials (for example, with a password manager).
To share billing between an existing connected account and an email/password account, message us via in-app chat.
How do I link a project to a Git provider using my email/password account?
Email accounts are not connected to a Git provider by default. This means you can only create unlinked projects.
Follow these instructions to link your project to a Git provider:
- Go to your profile (
/profile) and connect to your Git provider.
- Go to the project’s Manage page » Collaborate tab.
- Click to “sync collaborators with a Git repository”.
This connects your Chromatic email/password account with your Git provider account, allowing you to set up a linked project.
Note: Your personal account must have access to the repository in order to connect in Chromatic. You may need to ask an administrator to grant you additional permissions.