App Read-Down
App Read-Down only reads, so it never changes an app in Okta. The changes that Provisionr can make to an app’s assignments are described in Provisionr Groups and Direct Assignments. The stage reads your apps in the steps below.1
Apps
Every app in your Okta org is read with its name, label, sign-on mode, and status. New apps are imported, and existing apps are updated.
2
Group Assignments
Each app’s group assignments are read along with their priority, which Okta uses to decide which group’s app profile wins when a person reaches the app through more than one group. Only the assignments to groups that Provisionr has imported are kept.
3
Direct User Assignments
Each app’s direct user assignments are read and matched to identities by their Okta user ID. People who reach the app through a group aren’t stored again for each app, because they’re already stored as members of that group.
4
Removed Apps
An app that no longer exists in Okta is retired, and its assignments are cleared. Its history is kept.
Provisionr Groups
Each app has one Okta group of its own that Provisionr controls, which we call the app’s Provisionr group. The relationship is one to one, so each app has exactly one Provisionr group, and each Provisionr group grants exactly one app. The group’s policy decides who belongs in it, in the same way as any other group that a policy manages, which means that the policy decides who has the app. Provisionr controls the app’s assignment to its Provisionr group. An app can also be assigned to other groups, such as a group that your team manages by hand or a group that’s pushed from another directory. Provisionr reads those assignments so that you can see them, but it ignores them, and it never changes or removes them. This allows you to move an app’s access over to its Provisionr group at your own pace, while the groups that people already rely on keep working.Direct Assignments
A direct assignment is access that no policy controls. Someone added it by hand, and it stays until someone removes it by hand. When you know which people reach an app directly instead of through a managed group, you can find the access that would survive a role change, or an offboarding that only touched groups. The usual next step is to move that access into the app’s Provisionr group. The person then keeps the app while they qualify, and loses it automatically when they stop. Once an app’s access has moved into its Provisionr group, the direct assignments that are left over are technical debt, because the group now decides who has the app. Cleaning them up is optional, and you can do it in either of these ways:- Remove the direct assignments yourself in the Okta Admin Console.
- Let Provisionr remove them as part of the sync, which needs the
okta.apps.managescope. Provisionr only removes a direct assignment for a person who also reaches the app through its Provisionr group, so the cleanup never costs anyone the app.
Scopes
App Read-Down runs when the integration’s app scope is read or write. With an app scope of none, apps aren’t read at all, and group management works exactly the same. The app scope also decides who changes an app’s assignments. With read, you assign each app’s Provisionr group to its app in Okta yourself, and you clean up direct assignments yourself. With write, Provisionr assigns the Provisionr group to its app, and it can remove the direct assignments that are left over. See OAuth2 Scopes for the Okta API scopes behind each one.Logging App Read-Down
When App Read-Down finishes, it records a summary event that counts the apps that were imported, updated, and removed.workspace.integration.sync.okta.apps.finished
Once you can see how access flows through groups and apps, the next question is what happens when a policy’s changes look more like a mistake than a decision. The next page explains how write-back holds those changes for review. Continue reading: Policy Incidents →