Skip to main content

SCIM provisioning between Okta and Fullview

This guide explains how to configure SCIM provisioning for the Fullview app in Okta. Once configured, Okta can create, update, deactivate, and optionally sync groups to Fullview automatically.

Written by Dorin

This guide explains how to configure SCIM provisioning for the Fullview app in Okta. Once configured, Okta can create, update, deactivate, and optionally sync groups to Fullview automatically.

SCIM provisioning is part of the SSO settings flow and is configured in two places: first in Fullview, where you enable SCIM and generate the connector details, and then in Okta, where you paste those details into the Fullview application configuration.

Requirements

  • Admin access to your Fullview workspace.

  • Admin access to your Okta instance.

  • An existing Fullview SSO application in Okta.

Step 1: Enable SCIM in Fullview

  • In Fullview, go to your organization’s SSO settings

  • Find the SCIM card and enable SCIM provisioning

  • Generate a SCIM token and copy its value

Keep the token somewhere safe while completing the Okta setup. Fullview shows the token value when it is generated, then masks it afterwards. Token deletion is not supported; if you need to rotate the token later, regenerate it instead.

Step 2: Enable provisioning in the Fullview app of your Okta instance

  • In Okta, open the Fullview SSO application

  • Go to the General tab

  • Under App Settings, find Provisioning

  • Select SCIM and Save

This enables the provisioning configuration tabs for the Fullview application in Okta.

Step 3: Configure the SCIM connection in Okta

Once SCIM was enabled switch to the Provisioning tab and configure the SCIM connection as follows, then Save:

Field

Value

SCIM version

2.0

SCIM connector base URL

Paste the SCIM endpoint URL from Fullview

Unique identifier field for users

email

Supported provisioning actions

Select all

Authentication mode

HTTP Header

Authorization

Paste the token generated at Sep 1 in Fullview as the Bearer token

Step 4: Choose what Okta should provision to Fullview

  • Go to Provisioning → To App, click Edit, and enable the actions you need:

    • Create users

    • Update User Attributes

    • Deactivate Users

  • Save

Step 5: Assign users or groups

  • Go to the Assignments tab and assign the Fullview app to the users or groups that should have access

  • If Create Users is enabled, Okta will create or link those users in Fullview when the assignment is applied

Final step: Push groups from Okta to Fullview

  • Go to the Push Groups click Push Groups, and select the Okta groups you want to sync with Fullview.

Once added, the groups will be pushed to Fullview and synced to Fullview’s identity system, users being automatically provisioned and visible in Fullview under Team. You can use this tab to review mappings, last push time, and sync status.

Did this answer your question?