Practise the standard verbs for provisioning and deprovisioning access through Okta.
0 / 5 completed
1 / 5
Fill in: 'We ___ new employee accounts automatically through Okta on their first day, so access to every core application is ready before they even open a laptop.'
We 'provision accounts' — the standard, established SSO collocation for automatically creating application access for a new user. The other options aren't the recognised term here.
2 / 5
Fill in: 'Relying on manual account creation instead of automated provisioning can ___ a new hire waiting days for access to a tool their entire first week of work depends on.'
We say manual provisioning will 'leave' a new hire waiting for access — the standard, natural collocation for the resulting delay. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ group membership in Okta directly to role-based access in downstream applications, so a single directory change flows through instead of needing per-app edits.'
We 'map membership' — the standard, simple collocation for linking a directory attribute to an application permission. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every application's SSO integration quarterly against the current employee roster, so a departed contractor's account doesn't quietly remain active somewhere.'
We 'audit' an integration — the standard, simple collocation for periodically reviewing access against reality. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every application access the instant an employee's termination is recorded in Okta, rather than letting deprovisioning trail behind by hours or days.'
We 'revoke access' — the standard, established collocation for immediately removing a departed user's permissions. The other options aren't the recognised term here.