Skip to content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Probo Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

Identity and access

Authenticate members with SSO and automate their lifecycle with SCIM

View as Markdown

Probo separates authentication from user provisioning. Use SAML single sign-on (SSO) to authenticate organization members through your identity provider, and use SCIM to create, update, and deactivate their access.

Single sign-on Configure SAML authentication, verify domains, and enforce SSO
SCIM provisioning Automate user provisioning and deprovisioning from your identity provider

How the capabilities work together

Section titled “How the capabilities work together”

SSO verifies a member’s identity when they sign in, but it does not create or remove organization memberships. SCIM manages those memberships and user records, but it does not authenticate users. Organizations commonly configure both against the same identity provider so that assignment controls access and SSO protects authentication.

Section titled “Recommended rollout”
  1. Verify the email domain used by organization members.
  2. Configure SSO as optional and test both service-provider and identity-provider initiated sign-in.
  3. Configure SCIM with a limited group and confirm provisioning, updates, and deprovisioning.
  4. Expand the SCIM assignment to the intended population.
  5. Require SSO only after confirming that expected members can sign in and that a recovery path is available.

Probo provides setup guides for Google Workspace, Microsoft Entra ID or Microsoft 365, and Okta under the SSO and SCIM sections.

Section titled “Related access controls”

Use access reviews to periodically verify accounts and permissions in Probo and connected applications. Access reviews record reviewer decisions; they do not provision, deprovision, or change authentication policies.