How can we help?

Configuring access governance policies

Uri Hershkovitz
Uri Hershkovitz
  • Updated
Torii Identity

Overview

 

This article explains how to set up and manage access governance policies and groups. It's part of the Access Governance guide. 

 

The Access Governance page

Access Governance has a dedicated page in Torii where admins can manage policies and review deviations. The page includes four tabs:

Policy Deviations 
A centralized table of users whose access does not match policy. See Monitoring and resolving policy deviations.

Grace Period 
A centralized table of users who keep temporary access during a job function change. You can read more about Torii's grace period here.

Governance Policies 
A table of all defined access policies.

Groups 
A shared groups experience used to define and manage the user groups referenced by policies. These groups are shared with the App Catalog.

To configure feature-wide settings, click Access governance settings at the top of the page. See Access governance settings. If you enabled automatic remediation, click Action log to see the actions Torii took automatically.

 

The Governance Policies tab

The Governance Policies tab is where admins create and manage policies for connected apps.

From this tab, you can:

  • View all policies in one table
  • Create, edit, or delete a policy
  • Enable or disable monitoring for a policy
  • Run policy monitoring manually

Each row in the table represents one policy. The table also shows the number of groups affected by the policy, the number of deviations found, the last policy evaluation time, and whether the policy is active. This makes it easy to see which apps are governed, which policies are enabled, and where issues are being detected.

 

Creating a policy

Here's an article that walks you through creating two governance policies.

To create a policy:

  1. Click + New policy.
  2. Under Governance scope, select the app you want to create a policy for.
  3. Under Governance method, select how the app is governed:

    • Direct integration (role-based): select the app account to monitor. Torii evaluates access using the app's native roles and permissions.
    • IdP group-based access (group membership-based): select the relevant IdP and account to compare access to.

    Note: If the app does not have a connected integration, only IdP group-based access is available.

  1. Under Access rules, choose which roles the policy monitors. 
    • Roles to review lists the roles Torii discovered that you haven't decided on yet. For each one, click Monitor or Don't monitor. Click the user count next to a role to preview who has it today.
    • Roles you've decided on are moved to Monitored roles or Unmonitored roles. To change your mind, drag a role to the other section or click on the menu button for that role.
    • By default, only roles under Monitored roles create deviations. Newly discovered roles, roles left in To review, and roles in Unmonitored roles are not monitored.


Note: You don't need to cover every role before enabling a policy. Start with your critical roles, such as Admin and Owner, see real deviations right away, and add roles over time.

For each monitored role, set who can have it. This You will have to assign at least one group or user for each role to be able to monitor it. You can always view or update your choices by clicking the role's rule summary button.

The available access types are:

  • Allowed: Users in the selected group are permitted to have this access.
  • Birthright: Users in the selected group should automatically have this access.
  • Denied: Users in the selected group must not have this access. This applies to app owners too. 


Each role shows a summary of its rules, such as "1 group, 2 users". Hover over it to see the breakdown by access type.

  • Anyone who has a monitored role but isn't covered by a group or user rule for it is flagged as a deviation. App owners are the exception: by default, they are allowed any access to the apps they own. See Access governance settings.
  • For IdP group-based policies, the same rules apply, but instead of checking roles in the app, Torii checks membership in the configured IdP group.
  • Individual rules (rules for specific users) take precedence. If a user has an individual rule for a role, it overrides any group rule that applies to them for that role, in both directions. For example, if the Engineering group is Denied the Admin role but Matt has an individual Allowed rule, Matt isn't flagged. If Engineering is Allowed but Matt is individually Denied, Matt is flagged.
  • To block the whole app for a group or user, whatever their role, use an app-wide deny rule. Enable to "Should any group be denied access app-wide?" toggle, and enter the denied group. 

 

Best Practice: Once you've made a monitoring decision for each role for an app, we recommend enabling the "Should users in roles you haven’t reviewed count as deviations?" toggle. This will start monitoring any role you haven't made a specific decision about (i.e. roles in To review, and newly discovered roles), and flag them as deviations. This will make sure you are aware of unexpected new roles assigned in the app, and keep you on ahead of access changes in the app. 

  1. Under Enforcement settings, choose a Remediation level. By default, the policy uses the level set in Access governance settings (shown as Default configuration). To override it for this policy, choose:
    • None: Torii monitors the policy for deviations but takes no action except for email alerts.
    • Open task: Torii automatically opens a task for the app owner to fix discovered deviations.
    • Automatic remediation: Torii tries to fix discovered deviations by adjusting the user's access to match the policy. If it can't find a safe action, or the action fails, it opens a task instead. Learn more about automatic remediation.
       
  2. Click Review & Save.
  3. Choose whether to save the policy as Inactive (save without turning it on) or Active (turn it on immediately), then click Confirm & save.

 

Important notes

  • For direct integration policies, user access is reviewed at the app role level. For connected apps that don't provide role data, you can either upload user data manually.
  • For IdP group-based policies, user access is compared to the defined IdP groups. A user with access to the app (as reported by the IdP) who isn't in the correct IdP group is out of policy.
  • Only monitored roles create deviations, unless the "Should users in roles you haven’t reviewed count as deviations?" toggle is enabled. Within a monitored role, rules act as an allowlist: anyone with the role who isn't covered by a group or user rule is out of policy, except app owners when Allow app owner access is on.
  • A user's individual rule for a role always overrides their group rules for that role. Individually allowed users are treated as compliant in both deviations and access reviews.
  • A policy must include at least one fully defined rule on a role or IdP group before it can be saved.
  • The same app and account can have only one role-based policy, but can have both a role-based policy and an IdP group-based policy. Combine them to monitor (and fix) issues with both IdP group membership and actual app role.

     

Best practices

  • For non-integrated apps, you can upload a user file and then create a governance policy for the app. You can do the same with Google Sheet integrations and custom integrations (including data uploaded via Torii Sheets).
  • If you govern access today using IdP groups (for integrated or non-integrated apps), use IdP group-based policies to match your current processes for these apps.
  • Start small. Monitor your highest-risk roles, such as Admin and Owner, first, then add roles as you confirm the results. Enable the "Should users in roles you haven’t reviewed count as deviations?" toggle only once the policy covers every role.
  • Use groups for access that follows a person's department, team or location. Use individual users only for one-off exceptions, so policies stay easy to review.
  • If you're working with others on a complex policy, save it between updates but don't activate it until the configuration is final.
  • Test your policy with the remediation level set to None. Once you're happy with the results, change it to Open task, and then to Automatic remediation once you're confident. See Automatically remediating access policy deviations for guidance.

 

Other actions in the Governance Policies tab

When you hover over a policy in the Governance Policies tab, you'll see additional actions:

  • Edit policy: Edit an existing policy using the same flow as policy creation. Once a policy is created, you can't change the app and account it refers to.
  • Delete policy: Deletes the policy completely. Any open deviations are marked as resolved.
  • Evaluate now (active policies): Runs the policy evaluation immediately.

 

The Groups tab

The Groups tab is where users view and manage the groups used in Access Governance policies. These groups are also shared with the App Catalog.

Groups are the main way to define governance policy eligibility in Torii. They define which users a policy applies to based on their attributes, such as department, team, location, or any other user segment you want to govern. When you create a policy, you choose groups, individual users, or both, and define what access they should have for a specific app and account. Use individual users for one-off exceptions that don't need a group of their own.

From the Groups tab, admins can:

  • View existing groups
  • Create, edit, and delete groups used in governance policies
  • View the users in each group

This makes it easier to reuse consistent user segments across policies instead of redefining eligibility each time.

 

Creating a group

To create a group:

  1. Click + Add group on the Groups tab.
  2. In the sidebar that opens, name the new group.
  3. Select filters to fine-tune the list of users in your group.
  4. Preview the user list by expanding Users found.
  5. Click Save.

You can also create groups directly from the policy configuration page using a similar experience.

 

Permissions and availability

Creating and editing policies and groups requires the Access Governance: Take Action scope. 

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request