Automate User Management with SCIM Provisioning in Bynder

Summary

SCIM (System for Cross-domain Identity Management) is an open standard that enables your identity provider (IdP) to automatically create, update, and deactivate user accounts in other applications. While Single Sign-On (SSO) creates and updates accounts only when a user logs in, SCIM provides automatic synchronization that operates independently of user logins. This ensures your IdP remains the single source of truth for user identities and keeps your Bynder portal synchronized with your organization.

Who?

This feature requires IT administrators and Bynder portal administrators who manage identity providers such as Okta or Microsoft Entra ID (formerly Azure AD). You need administrator permissions in Bynder to configure SSO and generate the required SCIM credentials.

Why?

Automating user management with SCIM provisioning provides several benefits for your organization:

  • Better security: Departing employees lose access promptly. Without SCIM, an administrator must manually deactivate them in Bynder.

  • Less admin work: IT and portal administrators maintain user lists in one central location instead of two.

  • Consistent data: User details stay accurate across all connected systems.

  • Faster onboarding: New team members receive access to the portal immediately without requiring a support ticket.

How?

To implement SCIM provisioning for your Bynder portal, follow these setup steps:

  1. Confirm SSO is configured for your portal.

  2. Generate the SCIM credentials in Bynder.

  3. Configure the connection in your identity provider.

    • For Microsoft Entra ID, create a new enterprise application for SCIM rather than using the Bynder gallery application.

  4. Assign users or groups to the application.

    • Use IdP groups to control who gets provisioned.

    • We recommend testing the integration with a small group before rolling it out to your entire organization.

  5. Set a sensible default permission profile in Bynder, as new SCIM-created users receive it automatically.

  6. Review your user deactivation policies so they match your security requirements.

Related Articles

 

 

Updated