PermuteDocs
Go to Permute

Identity and access

SSO and provisioning

Configure employee sign-in through your identity provider and manage directory users with SCIM.

Organization SSO uses SAML 2.0 for sign-in and SCIM Users for provisioning. Owners and organization admins configure it in Organization Settings → Enterprise identity. Confirm availability in your target environment with Permute before rollout.

Sign-in and provisioning

SAML verifies employee sign-in through your identity provider. SCIM provisions directory users and their active status (it does not provision groups, roles, or resource permissions). Link directory identities to existing Permute accounts before requiring SSO. Local MFA remains required after SAML sign-in.

Source permissions, app grants, and action invocation permissions remain separate. Follow Permissions and sharing to arrange resource access.

Set up organization SSO

  1. Open Enterprise identity and start in Optional mode.
  2. Configure your identity provider using Permute’s service-provider details and save its issuer, sign-in URL, and signing certificates in Permute.
  3. Provision directory users through SCIM and link them to their existing Permute accounts.
  4. Test administrator sign-in, a second user, deactivation, and owner recovery before selecting Required mode.

Identity provider requirements

Providers must support sign-in initiated from Permute, signed SAML responses, and a persistent NameID that matches the directory user’s SCIM externalId. Just-in-time account creation and sign-in initiated from the identity provider are not supported.

For Google Workspace, use a custom SAML app; automatic user provisioning still needs verification. Work with Permute to verify Microsoft Entra ID or Okta sign-in, provisioning, and offboarding in your tenant before requiring SSO.

Offboarding

Verify that SCIM deactivation prevents the person from accessing the organization. Review direct sharing, owned resources, and connections as part of offboarding. Machine API keys and app grants retain their own access controls; review and revoke them separately where needed.