Docs

Learn / Advanced

Set up approval policies for access requests and tool uses (video)

A three-minute video of the eight steps to build an approval policy, test it, attach it to an access rule and a tool, and see its approval requests in Slack.

Watch one approval policy set up in three minutes: two rules, a test, then the same policy on an access rule and on a tool, so access requests and tool uses go to the right approvers. Each step below links to its written guide.

Before you start, make sure you are an Org Admin: only Org Admins see Approval Policies. Rules that use IdP groups or profile fields, and the Test policy panel, need a connected identity provider.

The eight steps

  1. Open Approval Policies

    In the sidebar, click Settings, then Approval Policies. Org admins can see this page. See Approval Policies.

  2. Create a policy

    Click Create approval policy. Give it a clear name, like Standard approvals, and click Create policy. A policy is an ordered list of rules. Each request goes to the first rule its requestor matches. See Create a policy.

  3. Add a rule for engineering

    Click Add rule, and name it Engineering. Under Requestor group membership, choose Only requestors in specific IdP groups, and add your Engineering group. Under Approvals, choose Require approval. New rules start with No approval needed, so don't skip this. Pick Related IdP user, and enter the profile field that holds each person's manager, like manager_email. Then click Create rule. See Add a rule.

  4. Add a rule for everyone else

    Click Add rule again, and name it Everyone else. Leave Any profile and Any group, so this rule matches everyone. Choose Require approval, then Channel, and pick your IT approvals channel. Make sure Risotto is in that channel. Click Create rule. Order matters here. Requests that match no rule are denied, so keep a catch-all rule at the bottom. See How a policy resolves.

  5. Test the policy

    In Test policy, select a user. Risotto shows which rule they match, and who would approve. An engineer matches rule one, so their manager approves. Someone from sales matches rule two, so your IT channel approves. See Test a policy.

  6. Attach the policy to an access rule

    Go to Settings, then Applications, and open an app, like GitHub. Click an access rule, then Edit. In the Approval section, change Approval policy from No policy to Standard approvals, and click Save. The policy now decides who approves requests for this access. See Access Rules and Attaching a policy to an access rule.

  7. Attach the policy to a tool

    Open Tools, pick a tool, like Reset MFA, and click Edit. Turn on Requires Approval, choose Standard approvals as the Approval policy, and click Save. Without a policy, anyone in the agent channel can approve. With one, the first matching rule decides. See Require approval and Attaching a policy to a tool.

  8. See it in Slack

    When an engineer asks for GitHub access, their manager gets an approval request in Slack, with Approve and Deny buttons. Risotto grants the access only after it's approved. When someone from sales needs an MFA reset, the tool approval request goes to your IT approvals channel instead.

One policy now routes approvals for access requests and tool uses. When your rules change, edit the policy once, and every access rule and tool that uses it follows. Next, attach the same policy to your runbooks. For six advanced cases, watch Approval policies: advanced use cases.

Something wrong or missing? Report an issue · View as Markdown