SCIM
Your Workforce, Provisioned.
Added. Updated. Removed.
FormsPro uses SCIM provisioning to keep users and access in sync with your identity provider. People are added when they join, updated when their role changes, and removed when they leave, without anyone retyping a user list.
How identity syncs
Change it once in your directory. FormsPro follows.
Your identity provider is already the record of who works for you and what they do. SCIM keeps FormsPro in step with it.
When someone joins a group in your directory, their FormsPro account is created with the access that group carries. A promotion or transfer updates their permissions. When they leave, their access is removed. IT makes the change in one place, and the field platform never drifts out of date.
- Ana R. added to Field TechsIn your identity providerAccount createdFormsPro, with field tech access
- Ben K. moved to SupervisorsIn your identity providerPermissions updatedFormsPro, now with approver access
- Cara M. removed from directoryIn your identity providerAccess removedFormsPro account deactivated
The gap
Inviting 2,000 users one at a time is not a rollout plan.
Switching forms platforms usually stalls on the least interesting step: getting everyone into the new system.
Without provisioning, IT exports a user list, cleans it up, imports it, and then maintains a second directory by hand for as long as the tool is in use. New hires wait for accounts. Transfers keep old permissions. And people who left last quarter can often still sign in, which is exactly the finding every security audit is looking for.
What you get
How does FormsPro SCIM provisioning work?
Provision from your identity provider
Users are created in FormsPro from your existing directory, so onboarding a crew is one change in one system instead of a list of invitations.
Bring a whole workforce at once
Move thousands of users into FormsPro during a migration without exporting spreadsheets or sending invitations person by person.
Access that follows role changes
When someone moves teams or takes on a new role in your directory, their FormsPro access changes to match.
Access removed when people leave
Deprovisioning in your identity provider carries through to FormsPro, closing the gap between an employee leaving and their access ending.
One source of truth for identity
Your directory stays the system of record for who has access. FormsPro never becomes a second user list to reconcile.
Built on an open standard
SCIM is the open standard enterprise IT teams use for identity provisioning, and it is increasingly a line item on software procurement checklists.
Use case in focus
A field services company is replacing its mobile forms tool. It has around 2,000 field users across several regions, and the old platform needed every one of them invited by hand.
2,000 users. One directory. No invitation emails.
During the last migration, IT spent weeks building user lists and chasing technicians who never clicked their invitation. Months later, accounts for people who had left were still active.
IT connects FormsPro to the identity provider.
Using SCIM, the open provisioning standard.
Field groups sync into FormsPro.
Technicians, supervisors, and planners arrive with the access their groups carry.
A new hire joins a field group.
Their FormsPro account exists before their first shift.
A technician is promoted to supervisor.
The directory change updates their FormsPro permissions.
A contractor’s engagement ends.
Removing them from the directory removes their FormsPro access.
Identity managed in one place. Access correct everywhere.
Compare
“User management” means different things.
| Identity component | Manual user management | FormsPro |
|---|---|---|
| Adding users | Invitations sent one at a time | Provisioned from your identity provider |
| Role changes | Updated by hand, if someone remembers | Follow the change in your directory |
| When someone leaves | Account stays active until noticed | Access removed through deprovisioning |
| Source of truth | A second user list in the forms tool | Your identity provider |
| Migrating a workforce | Spreadsheet exports and imports | Groups synced in one step |
SCIM ProvisioningAutomatic DeprovisioningGroup SyncOne Source of TruthOpen Standard
Your directory
The identity provider you already run stays in charge.
Your roles
FormsPro access follows the groups you manage.
Your environment
Users land in your single-tenant Azure environment.
Common questions
FormsPro SCIM FAQ
What is SCIM provisioning?
SCIM (System for Cross-domain Identity Management) is an open standard for automatically creating, updating, and removing user accounts across applications. Your identity provider sends user changes to connected apps, so IT manages access in one place instead of in every tool.
Does FormsPro support SCIM?
Yes. FormsPro supports SCIM provisioning, so users and their access can be managed from your identity provider instead of being invited and maintained by hand inside FormsPro.
Which identity providers work with FormsPro?
FormsPro works with identity providers that support SCIM provisioning. Confirm your specific provider and configuration with the OmniByte team during scoping.
What happens when an employee leaves?
When the user is deactivated or removed in your identity provider, the change carries through to FormsPro and their access is removed, so former employees and contractors do not keep working accounts.
Can SCIM assign roles and permissions in FormsPro?
Yes. Group membership in your identity provider can determine the access a user receives in FormsPro, so a role change in your directory updates their permissions.
How does SCIM help when switching from another forms platform?
Instead of exporting, cleaning, and importing user lists, you sync the relevant groups from your identity provider. Your workforce arrives in FormsPro with the right access, and new hires keep arriving the same way.
Stop managing users in two places.
See how quickly your field teams can be in FormsPro when your identity provider does the inviting.
Keep reading