Skip to main content
Not seeing the content you are looking for? Log in with your EliseAI credentials
Sign in

SCIM Provisioning

  • Updated

As an alternative to just-in-time (JIT) provisioning, EliseAI supports System for Cross-domain Identity Management (SCIM) provisioning. With SCIM enabled, user accounts are automatically created and updated based on changes in your identity provider (such as Okta or Azure AD). In this case, users do not need to log in before launch to be provisioned.

SCIM provisioning is configured by your EliseAI implementation team. Contact your EliseAI representative to enable SCIM for your organization.

 

Key Differences from JIT

  • User accounts are created automatically when added in your identity provider, without requiring a first login.
  • User profile updates (such as role or group changes) sync automatically from your identity provider.
  • User removal from your identity provider triggers automatic deprovisioning in EliseAI.

 

User Deprovisioning

When a user is removed from your identity provider, SCIM initiates deprovisioning in EliseAI. The behavior depends on the user's active assignments:

  • No active assignments: The user account is removed immediately.

  • Active assignments (voice hub routing, rotations, or agent schedules): The deletion is deferred until an administrator reassigns those responsibilities through the user management interface.

    For more information on this process, see Reassigning Schedules When Deleting Users.

 

Enablement Steps

Azure

Step 1: Open the EliseAI App in Microsoft Entra ID

  • Log in to the Microsoft Entra admin center (or Azure Portal) as an administrator. 
  • Navigate to Identity > Applications > Enterprise applications. 
  • Select your existing EliseAI application from the list.
    • If EliseAI is not listed, click New application, choose Create your own application, name it "EliseAI", and select "Integrate any other application you don't find in the gallery").
       

Step 2: Configure Provisioning Settings

  • Click on Provisioning in the left-hand navigation menu. 
  • Click Get started (or Edit provisioning). 
  • Change the Provisioning Mode from Manual to Automatic.
     

Step 3: Enter EliseAI Credentials

  • Expand the Admin Credentials section.
  • In the Tenant URL field, paste the SCIM endpoint URL provided by EliseAI.
  • In the Secret Token field, paste the Bearer Token copied from the EliseAI platform.
  • Click Test Connection to verify that Entra ID can successfully communicate with EliseAI.
  • Once the test succeeds, click Save at the top of the screen.
     

Step 4: Map Attributes (Optional / Default)

  • Expand the Mappings section below the credentials.
  • Click on Provision Microsoft Entra ID Users to review how user fields (like email, name, and status) align with EliseAI attributes.
  • Adjust or save the default mappings based on your organizational structure.
     

Step 5: Assign Users and Scope

  • Navigate to Users and groups from the application's left menu.
  • Click Add user/group to assign the specific employees or departments that need access to EliseAI.
  • Return to the Provisioning tab and click Edit provisioning settings.
  • Under Settings, choose whether to sync Only assigned users and groups or All users and groups in the Scope dropdown.
     

Step 6: Activate the Sync

  • Locate the Provisioning Status toggle at the bottom of the page.
  • Switch the toggle to On. 
  • Click Save at the top of the interface.
    • Entra ID will now start the initial synchronization cycle, which typically runs every 40 minutes.

 

Okta

Step 1: Enable Provisioning in the EliseAI App

  • Log in to the Okta Admin Console. 
  • Navigate to Applications > Applications in the left sidebar. 
  • Click on your existing EliseAI application.
    • If EliseAI is not already added, click Browse App Catalog, search for "SCIM 2.0 Test App" or use a custom SAML/OIDC app template, and name it "EliseAI"
  • Go to the General tab of the application, click Edit, check the box for SCIM under Provisioning, and click Save.
     

Step 2: Configure SCIM Connection Settings

  • A new Provisioning tab will appear at the top. Click on it.
  • Select Integration from the left-hand menu under the Provisioning tab.
  • Click Edit and fill in the following details:
    • SCIM connector base URL: Paste the SCIM endpoint URL provided by EliseAI.
    • Unique identifier field for users: Enter userName (this maps to the user's email/username).
    • Supported provisioning actions: Check the boxes for Push New Users, Push Profile Updates, and Push Groups (if applicable).
    • Authentication mode: Select HTTP Header from the dropdown menu.
       

Step 3: Enter the EliseAI Bearer Token

  • In the HTTP Header section, locate the Authorization or Bearer Token field.
  • Paste the Bearer Token copied from the EliseAI platform.
  • Click Test Connection to ensure Okta can successfully communicate with EliseAI.
  • Once the test passes, click Save.
     

Step 4: Enable App Provisioning Features

  • In the same Provisioning tab, click on To App under the Settings menu on the left.
  • Click Edit next to the provisioning features..
  • Check the Enable boxes next to the actions you want to automate:
    • Create Users.
    • Update User Attributes.
    • Deactivate Users (Crucial for auto-deprovisioning ex-employees).
  • Click Save.
     

Step 5: Assign Users and Groups

  • Navigate to the Assignments tab at the top of the EliseAI application page.
  • Click the Assign dropdown and choose either Assign to People or Assign to Groups.
  • Select the users or groups that need access to EliseAI and click Done
    • Okta will immediately queue these users and begin pushing their accounts to EliseAI in real time.

Related to

Related articles