Supported OAuth providers
Sign in with any Google or Google Workspace account
GitHub
Sign in with your GitHub personal or organization account
How OAuth login works
When you choose to log in with Google or GitHub, ButterCMS never receives or stores your password. Instead, the provider authenticates you and issues a short-lived token that confirms your identity.- Click Sign Up With Google or Sign Up With Github on the ButterCMS signup page
- You are redirected to the provider’s authorization screen
- Grant ButterCMS permission to read your basic profile and email address
- You are redirected back to ButterCMS and logged in automatically
ButterCMS only requests read access to your public profile and verified email address. It does not access your repositories, files, calendar, or any other provider data.
Sign in with Google
Requirements
- A Google account or Google Workspace (formerly G Suite) account
- Cookies and JavaScript enabled in your browser
Steps
- Go to app.buttercms.com/join/
- Click Sign Up With Google
- Select the Google account you want to use
- Review the requested permissions and click Allow
- A ButterCMS account will be created for you, and you will be redirected to your ButterCMS dashboard
Google Workspace considerations
| Scenario | Behavior |
|---|---|
| Personal Google account | Works for any ButterCMS plan |
| Workspace account | Works; your Workspace admin does not need to pre-approve ButterCMS |
| Workspace with app restrictions | Your admin may need to add ButterCMS as an allowed app |
Sign in with GitHub
Requirements
- A GitHub personal account or membership in a GitHub organization
Steps
- Go to app.buttercms.com/join/
- Click Sign Up With GitHub
- If prompted, authorize the ButterCMS OAuth application
- If prompted, provide an email address
- An account will be created for you, and you will be redirected to your ButterCMS dashboard
GitHub organization considerations
If your GitHub organization has OAuth app access restrictions enabled, a Workspace admin must approve the ButterCMS OAuth application before members can use GitHub login.- A member attempts to sign in with GitHub
- GitHub shows an “Access restricted” screen
- The member can request access from their organization owner
- The organization owner approves ButterCMS in GitHub Settings > Organization > Third-party access
Account matching
When you log in with OAuth for the first time, ButterCMS matches on email address:| Scenario | Result |
|---|---|
| Email matches an existing ButterCMS account | You are logged in to that account; the provider is linked automatically |
| Email does not match any account | A new ButterCMS account is created |
| Email matches but is unverified at the provider | Login is blocked until the provider email is verified |
Security considerations
| Topic | Details |
|---|---|
| Password not required | OAuth accounts do not need a ButterCMS password, but you can set one in Profile settings |
| Token expiry | OAuth tokens are short-lived and refreshed automatically; ButterCMS never stores your provider password |
| MFA | Enabling MFA on your Google or GitHub account also protects your ButterCMS login |
| Revoking access | You can revoke ButterCMS’s OAuth access from your provider’s security settings at any time |
Revoking access from your provider’s side will prevent future OAuth logins to ButterCMS with that provider, but does not delete your ButterCMS account or content.