Skip to main content
Now that you understand how policies work and how qualification decides who should have access, you can start to think about the groups and resources that you want to manage with Provisionr. Every group or resource that we know about has a policy, and the mode of that policy decides how much Provisionr does with it, from simply knowing that the group exists to adding and removing its members. This page explains each of those modes, how a policy treats members who were added outside of Provisionr, and how you can create new groups and resources from Provisionr.

Managing Existing Groups and Resources

When you connect an integration to Provisionr, we import a list of all of the groups and resources that are available in the integration API and create a placeholder policy for each one. The integration’s default_ruleset_mode decides which mode each new policy starts in, which is monitored unless you change it to ignored. This allows you to have a single source of truth for all of the groups and resources that are available across all of your connected integrations, and you can choose which ones you want to manage with Provisionr. We don’t make any changes until you explicitly choose to manage a group or resource by changing its policy to the additive or authoritative mode. Once a group or resource is monitored, you can start adding rules and conditions to its policy. Rules are created in the staged state, so you can design and configure them, and preview the people they’ll match, before they’re activated. A rule can only be activated when its policy is additive or authoritative, which means that a monitored group can’t be changed by accident. When you activate a rule, the people who match its conditions are added to the group or resource in the integration. Changing a policy’s mode requires the wks.policy.rule.activate permission in addition to the permission to edit the policy, because a mode can give Provisionr write access to a group. A policy can only be additive or authoritative when the integration has proven that it can add and remove group members. Some groups can’t be managed by a policy at all, because their membership is controlled somewhere else. In Okta, for example, an app group is read-only because the app or directory that it was imported from owns its membership, and Okta itself adds every user to the built-in Everyone group, so Provisionr reads these groups but never manages them. Okta Groups describes each type of Okta group.

Ignored Groups

When a group’s policy is in the ignored mode, we know that the group exists, and we can show its ID, name, and description in a list, but we don’t read the members assigned to it, which we also call its attached users. We only fetch a group’s members when its policy is monitored, additive, or authoritative. An ignored group is hidden from most lists to reduce clutter. We never write to it.
If you’d rather choose which groups we read, one at a time, set the integration’s default_ruleset_mode to ignored. New groups then stay ignored until you’ve chosen to monitor or manage them.

Monitored Groups

When you want Provisionr to give you read-only visibility into your groups and their members, and to track how their membership changes over time for audit events and observability, you can change any group’s policy to the monitored mode. We use those members to recommend rules and conditions, so when you’re ready to bring the group under a policy, we can suggest rules that match the people who are already in it. While a group is monitored, we fetch the list of members and their roles from the group or resource during each sync. Every new member, removed member, and changed role is recorded in the workspace event log. This gives you complete reporting of who has access, without Provisionr managing the policy. A monitored group is also a good place to draft a policy. You can add rules and conditions, which stay in the staged state so that you can preview who they’d match, and you can activate them once you’ve changed the policy to additive or authoritative.
Many customers monitor their groups rather than ignoring them, because the membership changes show where their biggest manual provisioning workloads are, which helps them decide which groups to create Provisionr policies for first.

Additive and Authoritative Groups

When a group is additive or authoritative, Provisionr is responsible for provisioning and deprovisioning users in that group, based on the rules and conditions that you’ve configured. During each sync, the group sync compares the policy’s manifest with the members in your vendor and writes the difference. With Okta, a policy only writes to Okta when the integration has proven that it can add and remove group members, and the first time a policy writes to a group, nothing is written until an admin confirms the changes. After that, safety checks can hold changes that look like a mistake in a policy incident for someone to review. When a user is added to the group outside of Provisionr, for example by hand in the vendor or by other automation, their Policy User is in the unmanaged state. What happens to them next depends on the policy’s mode. If the policy is authoritative, any users in the unmanaged state are removed from the group during the sync, to maintain least privilege access. If the policy is additive, users in the unmanaged state are not removed from the group during the sync. This ensures that pre-existing users who were added outside of Provisionr aren’t removed, and that the policy only applies to users in the active state. In other words, an additive policy isn’t the source of truth for who should have access to the group, but it still provides value by ensuring that everyone who matches the policy is added to the group. You can change a group to authoritative later, after you have rules and conditions in place and you’ve given your team time to adjust to the new provisioning process. This allows you to move to Provisionr for all of your groups and resources gradually, without disrupting your users. Okta Groups shows how each kind of policy decides which members to remove in Okta, and the reason that it records for each removal. Whichever you choose, a grace period protects people whose attributes changed, not people who have left. A person who leaves your organization is removed from every group that a policy manages on the same sync that imports their departure, whatever the grace period. Removing Access for Leavers walks through each step.

Changing a Group Back to Monitored or Ignored

If you change a policy from additive or authoritative back to monitored or ignored, its active and expiring rules move to the paused state at that moment. A paused rule stops granting access, so nobody new is added through it. The people it already granted keep their Policy Users. No grace period starts, because they haven’t stopped qualifying, and a grace period that was already running doesn’t end during the pause. A paused rule keeps its expiry date if it had one. When you change the policy back to additive or authoritative, its paused rules return to active, or to expiring if they have an expiry date. If that date passed during the pause, the rule expires at that moment.

New Groups and Resources

Creating groups and resources from Provisionr is planned and isn’t available yet. The Feature Roadmap is where we share planned work.
When this is available, we’ll create the group or resource in the integration first, so that we have its vendor ID, and then create a policy that manages it. The group will start out empty, and its rules will start in the staged state, which will allow you to design the rules and conditions and see the list of users who qualify. Nobody will be added to the group until you activate a rule.

Control Plane Considerations

Over time, you can choose to make Provisionr your single pane of glass for provisioning groups and resources, and restrict the number of administrators who can create groups and resources directly in the integration. This gives you better control over, and visibility into, the groups and resources that are being created, and ensures that each of them is created with the appropriate policies and access controls in place.
With groups configured and policies defined, the last piece is understanding how and when Provisionr actually syncs these changes to your connected systems. Continue reading: Scheduled Sync →