Back to Blog
Blog

How do you provision field app access through SSO without a second manual invite?

How do you provision field app access through SSO without a second manual invite?

When field app access depends on someone sending a separate invite, new starters often wait days to get in and people who leave keep access longer than…

When field app access depends on someone sending a separate invite, new starters often wait days to get in and people who leave keep access longer than they should. The invite usually depends on a supervisor remembering to ask and an administrator finding time to set up the account, so a new technician can spend their first week unable to open the procedures or permits they are supposed to be learning.

The leaving side is the bigger risk, since accounts created by hand are rarely removed by hand with the same care, and a contractor whose engagement ended months ago may still be able to sign in and view site information. Tying access to the company’s single sign on setup removes that manual step, because a person who can no longer sign in to company systems also cannot sign in to the field app.

Ideally, users are created and removed automatically based on groups in the company’s identity system, so adding someone to the right group gives them access with the right role. Many identity providers support automatic provisioning, often through a standard called SCIM, which lets the field app receive new users, role changes and removals as they happen rather than waiting for someone to update a list.

That keeps access in line with employment status and saves administrators from managing users in two places. When someone moves from operations to maintenance, changing their group membership updates their role in the field app as well, and access reviews become simpler because the identity system is the single place that shows who has access to what.

A practical setup starts by agreeing which identity groups map to which roles in the field app, such as operator, supervisor, permit issuer and administrator, and keeping that mapping short enough to maintain. It also helps to plan for contractors and shared devices, since contractors may sit in a separate directory and some crews share tablets, and both need a clear approach before the manual invite process is switched off.