Scimify by Veraproof

Set up SCIM provisioning in your IdP or identity governance platform just as you would for any other app.
Scimify's pre-built connectors translate SCIM requests into each app's native API calls, enabling seamless user and group provisioning — even for apps without native SCIM support.

See our configuration guides for Okta, Lumos, and other SCIM 2.0 platforms (Entra ID, SailPoint, and more).

Scimify supports prebuilt SCIM connectors for popular SaaS apps — including Slack Enterprise, GitHub, Adobe Creative Cloud, Jamf Pro, OpenAI, Buildkite, SendGrid, ClickSend, and many more — plus Custom HTTP mapping for niche or in-house APIs.

See the full catalog on our Scimify integrations page. More apps are added regularly — contact us if you don't see yours.

Scimify automates user & group provisioning across all your SaaS applications, eliminating manual setup and reducing security risks. Instead of managing users individually in each app, you control everything from your central identity provider using SCIM - even for applications that don't natively support SCIM.

Key benefits:

• Automated joiner, mover, and leaver event handling
• Reduced SaaS license costs through automated deprovisioning
• Saves time and reduces manual overhead for IT teams
• Instant access when requests are approved in your identity governance system
• SCIM support for apps that don't natively support enterprise provisioning

Only provisioned users count toward your subscription quota.
If a user is provisioned to multiple apps or groups through Scimify, they're deduplicated - meaning each unique user is only counted once.

When you remove an integration, all configuration data, user mappings, and group associations stored in Scimify are deleted.
However, users and groups in the downstream app remain untouched, ensuring continuity in your target systems.

Scimify only stores the minimum required data to perform SCIM operations, including:

• User email addresses and display names
• Group names and unique identifiers
• Integration API tokens (encrypted at rest and in transit)

We never store passwords, and all data is processed under least-privilege access principles.

Yes.
Scimify can import users and groups from apps into Okta, allowing you to link existing app resources with your Okta directory - perfect for onboarding legacy users or aligning external accounts.

Absolutely.
For many in-house or niche SaaS products, you can use Custom HTTP yourself: define how each SCIM operation (create, update, delete, group membership, and so on) maps to your app’s REST endpoints—method, URL, headers, body templates, auth (for example API keys or OAuth client credentials), and how to read IDs and fields back from JSON, XML, or query-style responses. Your IdP still speaks standard SCIM to Scimify; Scimify turns that into the HTTP your API expects.

When you need a fully managed, productized connector (deeper semantics, edge cases, or we maintain it for you), we can also build custom integrations at no additional cost for paying customers. If you have an active subscription and want either path, contact us and we’ll help you choose the best fit.

Yes.
Scimify supports renaming groups in the IdP, allowing you to keep your group names consistent across all applications. Idp configuration will determine if a group rename in the Idp will be reflected in the downstream app. Okta supports group renaming by default, so Scimify will automatically reflect any group name changes in the downstream app.