Following the introduction of Security Assertion Markup Language (SAML), we're happy to share that our enterprise users can now also use System for Cross-domain Identity Management (SCIM) to control user access and authorisation to incident.io.
Both SCIM and SAML can be used independently of each other, but they are often used in combination. SCIM complements the authentication capabilities of SAML, by adding automatic provisioning, deprovisioning and authorisation control.
This means that you can now use identity providers like Okta or Google Workspaces to centrally control (1) user access to incident.io and (2) what the users are allowed to do once they are logged-in to the dashboard.
SCIM can also be used in combination with the recent improvements to our role-based access control (RBAC) capabilities. For example, a group in Okta can be both automatically provisioned and automatically assigned the appropriate RBAC role in incident.io, whether the role is a custom role or a base role. You can read more about configuring users permissions here.
If you use an Identity Provider (IdP) other than Okta SCIM, please get in touch. While we are able to support other IdPs promptly on demand, functionality might be limited.
For more information on how to get started with SCIM, please refer to our help centre article.
assigneeas an attribute to the follow-up webhooks payload.