SCIM
InfoSCIM user provisioning requires SSO/SAML to be enabled. See prerequisites below for more details.
SCIM (System for Cross-domain Identity Management) user provisioning allows you to synchronize team member accounts from your identity provider, such as Google Workspace or Okta, to emulator.wtf. In the SCIM flow, emulator.wtf acts as the Service Provider (SP), while your SSO/SAML provider serves as the Identity Provider (IdP).
Our current SCIM implementation supports the following features:
- User provisioning (create user)
- User deprovisioning (delete user)
- User attribute updates (name, email)
- New users are assigned to the role configured during SCIM setup (
triageby default) - Username/password-based accounts alongside SCIM are allowed. We strongly recommend keeping at least one owner account configured this way to recover access if there is an issue with your IdP configuration.
We don’t support the following:
- Group-based role mapping (coming soon)
- Bulk provisioning (coming soon)
Prerequisites
To configure SCIM, your organization must be on the Enterprise plan with SSO/SAML already set up. If you haven’t configured SSO/SAML yet, refer to the SAML guides first. To kick off SCIM configuration, you’ll need owner-level access to emulator.wtf and administrator level access to your IdP. In many companies, IdP administration is handled by an internal IT team.
Configuring SCIM
Follow one of the following guides to set up SCIM depending on your corporate identity provider (IdP):
Other identity providers should work as well, but we haven’t tested them yet. If you have any questions or issues, contact us at support@emulator.wtf.
Signing in as a SCIM provisioned user
On the emulator.wtf sign-in page click the Sign In with SSO button, fill in your work email address and click Sign In. If the user does not exist yet in emulator.wtf then ask your administrator to add you to the emulator.wtf app on your IdP provider.