Introducing Support for SCIM

IntegrationSCIM stands for System for Cross-domain Identity Management. It is an open standard for the automated exchange of user identity information, such as names, email addresses, phone numbers, etc.

The SCIM API of 4me makes it possible for organizations to get their identity provider (like Azure Active Directory, Okta, OneLogin, Google Cloud Identity, etc.) to act as a provisioning client so that the people records in their 4me directory account get updated automatically.
To start making use of 4me’s SCIM API, the owner of an organization’s 4me account needs to pick up the account’s SCIM token from the ‘Apps’ section in the Settings console.

SCIM in Apps section of the 4me Settings console
The developer documentation explains how to set up the integration between a provisioning client and 4me. Once the SCIM integration has been established, the user information is imported and automatically updated in the new ‘SCIM Users’ section of the Settings console.

SCIM users in the 4me Settings console
There, an automation rule ensures that the user information is properly mapped to the fields of a 4me person record.

SCIM user data mapping
This default automation rule can be adjusted as needed by an administrator of the 4me account.
SCIM also provides group data. A SCIM group is typically a department, a site, a team or an access profile. The SCIM groups are automatically imported and updated in the ‘SCIM Groups’ section of the Settings console. By default, two useful automation rules are already defined to help account administrators convert the group information into 4me organization and site records.

Automation rules for converting SCIM groups to 4me organizations and sites