# Approval policies: advanced use cases (video)

A four-minute video of six approval policy cases: one policy for several audiences, approvers from the profile, a fallback when no one responds, the access rule around a policy, policies on tools, and what happens when your identity provider can't be reached.

Watch an org admin at Northwind handle six real cases with approval policies, access rules and tools. Each case is set up in the dashboard, then seen at work in Slack. This video picks up after [Set up approval policies](https://www.tryrisotto.com/docs/guides/approval-policies-video), so it doesn't show how to create a policy. Each case below links to its written guide.

[Video: Approval policies: advanced use cases](https://media.tryrisotto.com/videos/approval-policies-advanced-desktop.mp4)

Before you start, make sure you are an Org Admin: only Org Admins see **Approval Policies**. Rules that use profile fields or IdP groups, and the **Test policy** panel, need a connected [identity provider](https://www.tryrisotto.com/docs/guides/initial/idp-setup).

## The six cases

1. **One policy, several audiences**

   The Production access policy has two rules. Engineering managers need no
   approval. That rule uses two condition groups: the department is
   Engineering, and the title contains Manager or Director. Everyone else needs
   their manager. Now contractors. Click **Add rule**, and match
   `employmentType` equals `Contractor`, a custom attribute from Okta. Require
   their manager, then the IT Security group, **In order**, and require **All
   of them**. The new rule lands at the bottom, under the catch-all, so it
   would never match. Drag it to the top: most specific first, catch-all last.
   Then test it. Luis, a contractor, matches rule one. Chris, an engineering
   manager, matches rule two, with no approval. And Priya, an engineer, matches
   rule three, so her manager approves. See [How a policy
   resolves](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#how-a-policy-resolves),
   [Add a rule](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#add-a-rule), [Test a
   policy](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#test-a-policy) and
   [Requestor
   profile](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#requestor-profile).

2. **Approvers from the profile**

   The manager step is a **Related IdP user**: Risotto reads the manager's
   email from the profile of the person who gets the access. For access
   requests, a step can also ask the **Business owner of the app**. On the
   Contractors rule, turn on **Require a reason on denial** and **Prevent
   self-approval**. Prevent self-approval compares each approver with the
   person who gets the access, not the one who asked. So when Chris asks for
   production access for Luis, Chris still gets the request as Luis's manager,
   and can approve it. Luis couldn't. Then Nina, in IT Security, denies it, and
   Risotto asks her for a reason first. See [Approval
   requirements](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#approval-requirements)
   and [Approvals](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#approvals).

3. **If no one responds**

   On the Everyone else rule, turn on **If no one responds**. After 48 hours,
   also ask a fallback approver, here Elena. If there's still no answer 24
   hours later, escalate the ticket. So when Priya's request sits with her
   manager for two days, Elena gets it, marked "Waiting", with how long it
   waited and who didn't answer. One approval from Elena completes it. If she
   doesn't answer either, Risotto escalates the ticket through the department's
   [escalation
   routing](https://www.tryrisotto.com/docs/dashboard/settings/departments#escalation-routing). See [If
   no one
   responds](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#if-no-one-responds).

4. **The access rule around the policy**

   Open AWS, and the rule AWS Production, up to 1 month, which uses this
   policy. In **Additional settings**, turn on **Reason required?**, and add
   **Reason instructions**: name the incident, ticket or project. Risotto asks
   the requester for those specifics, and checks the reason against them.
   **Allowed Duration** runs from 1 hour to 1 month. **Renewal prompts** offer
   a one-click extension, and **Require approval on renewal** sends it back to
   the approvers. In Slack, Priya's reason names no project, so Risotto asks
   her for one. And when she extends, her manager approves again. An approval
   can't depend on the duration someone asks for. So permanent access gets its
   own rule, AWS Production, permanent, with its own approvals. See [Additional
   settings](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#additional-settings) and
   [Renewing time-limited
   access](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#renewing-time-limited-access).

5. **Approvals on sensitive tools**

   Without a policy, anyone in the agent channel can approve a tool. Reset MFA
   needs more, so give it a Sensitive tools policy, which asks IT Security.
   Nina's **Tool Approval Request** shows the ticket, the requestor, the
   agent's rationale, and each parameter. In a runbook, one tool reference can
   use a different policy: in the Lost phone runbook, set that row's
   **Approval** to Help desk approvals. The Assistant can add an approval
   requirement to a tool, but never remove one. When an access rule runs a
   script tool, the access rule's approval applies instead, and the tool page
   says so: **Approval not enforced for access rules**. See [Attaching a policy
   to a
   tool](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#attaching-a-policy-to-a-tool),
   [A different policy for one tool
   reference](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#a-different-policy-for-one-tool-reference)
   and [Require approval](https://www.tryrisotto.com/docs/dashboard/tools#require-approval).

6. **When Okta can't be reached**

   If Risotto can't read Luis's profile, it can't tell whether he's a
   contractor. So it doesn't fall through to the catch-all, where only his
   manager would approve. It stops at the rule it can't evaluate, grants
   nothing, and escalates the ticket, with the reason on it. See [When a
   condition cannot be
   evaluated](https://www.tryrisotto.com/docs/dashboard/settings/approval-policies#when-a-condition-cannot-be-evaluated).

That's one policy for every audience, with a fallback when no one answers, and no step skipped in an outage. Next, [set up your department's escalation routing](https://www.tryrisotto.com/docs/dashboard/settings/departments#escalation-routing), where these escalations land.

Source: https://www.tryrisotto.com/docs/guides/approval-policies-advanced-video
