- Getting Started
- Code Review
- Platforms
- Agentic Coding
- Configuration
- CI integrations
- Design Tools
- Developer Tools
- Web Projects
- Get Notified
- API
- Single Sign On
- Self-host
SCIM lets your Identity Provider (IdP), such as Okta or Microsoft Entra ID, manage who has access to Screenshotbot. When you assign someone to Screenshotbot in your IdP, they get access, and when you unassign or deactivate them, they lose it.
SCIM only manages users. Users still sign in with SAML or your other sign-in method.
SCIM needs to be enabled for your organization. Contact us to enable it.
You'll need to be an Owner of your organization.
Go to Settings | SCIM and click Create Token. Copy the token, since you won't be able to see it again.
Configure your IdP with:
In Okta, enable SCIM provisioning on the app you created for SAML, then on the Provisioning tab:
Some things aren't synced:
You can create more than one token. To rotate a token, create a new one, update your IdP to use it, and then delete the old one in Settings | SCIM . Once a token is deleted, any IdP still using it will start failing.