Skip to main content
Eptura Knowledge Center

Application Setup

  1. Last updated
  2. Save as PDF
Application Setup provides guidance on the onboarding sequence, data imports, and product consumption

SSO and SCIM configuration

Understanding the relationship between SSO and SCIM

SSO and SCIM are independent features that can be configured separately or in parallel. However, SCIM-provisioned users require SSO to be set up before they can sign in. Remember that SSO can function on its own without SCIM, but SCIM cannot be used without SSO.

Onboarding Sequence

We recommend that you configure SSO before enabling SCIM.

As SSO setup often involves steps in your organization's Active Directory that may take time to complete, the following order is strongly advised to avoid disrupting access for your super users.

  1. Create a form user as a super user — During onboarding, a user with an email address in your AD is created as a form-based super user. This user can log in and access the platform immediately.
  2. Enable SSO — After SSO is configured in your AD, enable it on the Eptura platform.
  3. Transition users to SSO — Depending on whether you are using SCIM, proceed with one of the following paths:
    • Without SCIM: An admin can manually update each user's login type from Form to SSO. Once updated, the user can log in using their SSO credentials.
    • With SCIM: Enable SCIM to begin syncing users into the system. If a user's email already exists in the platform, their login type is automatically updated to SSO upon sync. They can then log in using their SSO credentials.

If SCIM is enabled before SSO is fully configured, users will be synced into the system but will be unable to log in until SSO is activated. To prevent this, always ensure SSO is working correctly before enabling SCIM.

Learn more in Authentication Overview and User Provisioning Overview.

Importing into Eptura

The table below describes the data that can be imported into Eptura. Additionally, it provides links to articles that describe what fields the Eptura products consume.

Import Product Consumption

People Data

Directory is where your people (users) and their access to the Eptura products are managed. Typically, your users (and groups) are provisioned using SCIM into Eptura, learn more in User Provisioning Overview. 

If your organization isn't using SCIM, then your Administrator can upload your people data into the directory, see Import People Data.

Groups and Group Member Data

Your groups can be managed using Eptura SCIM (User Provisioning) and this will also manage the users who are members of the groups.

If you don't use this, then your Administrator can set up the groups manually (or import them in) for your organization and they can assign a person as a member to a group with the desired app access to manage access rights uniformly as a group of users. Learn more in Import Group Data and Import Group Member Data.

Find out which Eptura products consume the people fields, see Person Fields.

Department Hierarchy Data

Your Administrator can upload the department hierarchy into the directory. Learn more in Import Department Hierarchy Data.
Eptura contains default space types.

Space Types

Find out which Eptura products consume the space types, see Space Type Fields.

Floor Plans

When you have a floor plan ready for upload, then you can use our plugins to publish the floor plan and spaces into Eptura. Learn more in Floor Plan Publishing.

Floor Plans

Floor Plans are consumed in Eptura Asset's  Asset Floor Plan Viewer ↗