Skip to main content

Configure SSO and Automated User Provisioning in Appspace

  • Nov 18, 2026 10:33 PM UTC
  • 0 replies
  • 2 views

Dawn Wayland
Employee
Forum|alt.badge.img+9

Choose the right SSO and provisioning setup for Microsoft Entra ID or Okta

Appspace can integrate with a SAML 2.0-compatible identity provider to simplify authentication and help your organization manage user access at scale.

This article introduces the available authentication and provisioning options and helps you choose the configuration path that fits your organization.

 

How Authentication and Provisioning Work Together

 

Authentication and provisioning serve different purposes within an identity integration:

Capability What It Does When It Happens
Single Sign-On Allows users to authenticate to Appspace using credentials managed by your identity provider. When a user signs in.
Just-in-Time Provisioning Creates an Appspace user when that person signs in with SSO for the first time. During the user’s first successful sign-in.
SCIM Provisioning Synchronizes users and, optionally, groups from your identity provider to Appspace. Automatically as identities and assignments change.

 

Choose a Provisioning Method

 

Appspace supports several ways to create and manage users.

Manual Provisioning

Administrators create and manage users directly in Appspace. This approach may be appropriate for small teams or users who require occasional access, but it becomes difficult to maintain as the organization grows.

Just-in-Time Provisioning

Just-in-Time provisioning creates a user in Appspace when that person signs in through SSO for the first time. It reduces initial account setup but does not provide the same ongoing user lifecycle or group management capabilities as SCIM.

SCIM Provisioning

SCIM automatically synchronizes user information from your identity provider to Appspace. Depending on your configuration, it can support:

  • Creating new users
  • Updating user information
  • Deactivating users who should no longer have access
  • Provisioning groups and group memberships
  • Supporting role- or location-based onboarding workflows

Recommended: Use SCIM when you need scalable user lifecycle management or want identity provider groups to help organize users in Appspace.

 

Choose Your Identity Provider

 

Microsoft Entra ID

Use the Microsoft Entra ID configuration guides to connect Appspace to an Entra enterprise application and configure the appropriate SAML claims, provisioning settings, and group assignments.

Okta

Use the Okta configuration guides to create an Appspace application integration and configure SAML authentication, SCIM provisioning, and group assignments.

 

Plan Access Before You Begin

 

Before configuring the integration, decide which users should be provisioned and which users should be permitted to sign in.

Provisioning a user does not always grant that user access. Your identity provider may separately require users or groups to be assigned to the Appspace application before they can authenticate.

Consider defining groups based on:

  • Appspace administrative roles
  • Locations or regions
  • Content creation and publishing responsibilities
  • Licensed Appspace capabilities
  • Departments or business functions

This can support staged rollouts, role-based access, and more consistent onboarding and offboarding.

 

Additional Configuration and Governance

 

After establishing SSO and provisioning, use the following guides to complete and maintain your identity integration:

 

Important Considerations

 

  • Use a test account. Test authentication before applying an SSO-only policy to the entire account.
  • Protect provisioning credentials. Treat the SCIM bearer token as sensitive information and do not include it in screenshots or support posts.
  • Review assignments. Confirm which users and groups are assigned to the Appspace application in your identity provider.
  • Plan for offboarding. Understand how removing a user from the provisioning scope affects that user in Appspace.
  • Separate administrative duties. Avoid allowing an administrator to delete a provisioning group that controls their own access.