Docs

Help desk / Access requests

Access Rules

Create access rules that decide how Risotto grants one level of access to an application, who approves the request, and for how long.

An access rule tells Risotto how to grant one level of access to an application: the identity provider group to add the person to (or another way to grant it), who must approve the request, and for how long the access lasts. An application has one rule for each level of access, for example Figma Viewer and Figma Editor.

To watch an access rule at work day to day, from a request in Slack to the grant on the Access Grants page, see the three-minute video. To watch a rule's reason instructions, allowed duration and renewal settings around an approval policy, see Approval policies: advanced use cases.

Create an access rule

  1. Open the application

    Go to Settings > Applications and open the application. Its page lists the application's Access Rules. Click Create rule.

    An application can have up to 100 rules. Create rule does not show once it has 100.

  2. Name the rule

    In the Create rule for dialog, enter a Name, for example Figma Editor, and click Create rule. Risotto shows "Rule created" and opens the new rule in edit mode.

    Each rule name must be unique within the application. Otherwise the dialog shows "A rule with this name already exists for this application."

  3. Choose how access is granted

    In the Access settings card, choose the Identity Provider Group that Risotto adds the person to. Open the picker, search for the group, and select it. You can also grant access with a license server, a script tool, or a manual grantor. See Access settings.

    A rule needs at least one way to grant access: an Identity Provider Group, a manual grantor, a Custom response, a license server, or a script tool. Otherwise the save fails with "Access rule must have at least one fulfillment method".

  4. Choose who approves

    In the Approval card, keep Approval policy on No policy to set approvers for this rule only, or select a shared approval policy. Without a policy, select Require approval under Approvals and add each approver with Add approval step. See Approval.

  5. Set the time limit

    In the Additional settings card, set Allowed Duration: the shortest and longest time a person can ask for. Turn on Reason required? to make the requestor give a reason. See Additional settings.

  6. Save the rule

    Click Save at the top right. Risotto shows "Access rule saved" and opens the rule's page.

  7. Turn the rule on

    A new rule is saved turned off, and Risotto does not use it. On the rule's page, turn on the Enabled? switch beside the rule's name. Risotto shows "Rule enabled".

The application page

Settings > Applications lists your applications. Open one to see its Access Rules table, with each rule's Name, Grant Method, and Enabled? switch. Click a rule's name to open it.

Grant Method shows how the rule grants access:

  • The identity provider and group, for example Okta / Figma Editors
  • The license server's name
  • The grantor's email address
  • Manually granted
  • Custom response only
  • Multiple, when the rule uses more than one of a group, a manual grantor, and a license server

The row's menu (⋮) has Edit access rule, Disable rule or Enable rule, Duplicate rule, and Delete rule…. On a rule's page, press ⌘K (Ctrl+K on Windows and Linux) to see the same commands. Duplicate rule makes a copy named "<rule name> (Copy)" and opens it. Delete rule… asks you to confirm ("People can no longer request access through this rule. This action cannot be undone.").

Only Org Admins and Managers can edit, turn on or off, duplicate, or delete a rule. For other users, the Edit button does not show and the Enabled? switch is unavailable. Rules that Risotto syncs from a Google Group are read-only and do not have these commands.

When the application's access is delegated to Okta Identity Governance or Opal, the page shows the delegated access summary instead of the Access Rules table.

Application details

The side panel shows Application details. Click the pencil icon beside a value to change it.

  • Business owner email: the person responsible for security reviews. The Business owner of the app approver asks this person.
  • External ID: the ID of the application in your identity provider.
  • Mutually exclusive groups: when on, adding a user to one of the application's groups removes them from its other groups.
  • Delegated Access: shows only when Okta OIG or Opal is enabled. Select Okta OIG, Opal, or Not delegated. When the application is delegated, the other application details do not show.

Under Default rule properties, Keywords holds a comma-separated list of keywords (for example figma, design tool) that new rules for this application start with. A rule can change its own keywords.

Admin Notes at the bottom holds notes that only dashboard users see.

The rule page

A rule's page opens from the breadcrumb Applications › Figma / Access rules › Figma Editor. The rule's name sits at the top with its Enabled? switch. Click Edit at the top right (keyboard shortcut e) to change the rule, and then Save or Cancel.

The settings are grouped into three cards, in this order: Access settings, Approval, and Additional settings. Under them, the Access requests card lists the requests that matched the rule, newest first, with their Status, Type, Target user, Requested date, and Expires date. Click a row to open the request on the Access Grants page. The card shows only to users who can read tickets in at least one department.

The side panel shows the parent Application, the rule's User count, Created at, Last updated at, and Admin Notes.

Access settings

Identity Provider Group is the group that Risotto adds the person to once every condition is met. The picker lists your groups under each identity provider, with each group's ID under its name. Click Refresh groups at the bottom of the list to read the groups again. Click the X beside the picker to clear the group.

If the group list is slow to load, paste the group's ID into the search box and choose Use this group ID. The option appears when the text has no spaces and matches no listed group. The field shows the raw ID until the group list loads, then the group name. When you save, Risotto checks the ID with your identity provider. If the provider cannot find the group, the save fails with "Security group not found". The approver group picker does not accept a pasted ID.

If your organization has a license server, a License Servers card shows in Access settings. Select the Server, then the setting for that provider (for example Product Name for JetBrains). See License Servers.

Group members without a Risotto grant

Under Identity Provider Group, Risotto checks the group's members. It reads every member of the group from your identity provider and compares the list with the access that Risotto granted. The check works for Okta, Google, Microsoft Entra ID, and JumpCloud groups. It does not show when the rule has no group, or when the rule hands requests to Opal or Okta Identity Governance.

  • "All N members have a Risotto grant" means that every member got the access through Risotto.
  • "X of N members have no Risotto grant" means that some members got into the group another way, for example when an admin added them in the identity provider. Click Show members to see them. Risotto did not grant their access, so it will not expire or remove it.
  • "This group has no members." means that the group is empty.
  • "This Okta group is read-only. Risotto cannot add or remove its members." shows for an Okta group that Okta does not let Risotto change, for example an application group.

The check is read-only. It does not change who is in the group. A member without an email address always counts as having no Risotto grant. For Microsoft Entra ID, Risotto counts only users who are direct members, not members of nested groups. For Google, Risotto counts only users.

Risotto keeps the member list for up to one day. To read the group again, click Refresh members (the refresh icon). If Risotto cannot read the group, the check shows "Couldn't load group members." with a Try again button.

Script tool

In the Script tool card, select a published script tool under Script. Risotto runs the script to grant access after approval, and again to remove access when it ends. The script must take an action input (grant or remove) and a recipient_email input, which Risotto fills. A script that can't be used is greyed out in the list, with the reason under its name.

Under the selected script, set its other inputs. Risotto does not send an input that you leave unset, and the save fails while a required input is unset.

If the script tool has its own approval requirement, the card warns: "This tool has an approval requirement which will not be enforced when this access rule is used." Set approvers in the rule's Approval card instead.

Manual grantors

Some services either do not support SSO (IdP/SAML/oauth) or require additional manual steps to provision. Risotto can follow up to a human or team to take a manual step. The Manual grantors card holds two fields. Fill in one of them: entering a value in one turns the other off.

  • Grantor email: the person Risotto asks, by direct message, to grant the access.
  • Grantors channel: the Slack channel Risotto posts in, so that someone in it grants the access. Search for the channel by name, or paste its channel ID (for example C0123456789) and choose Use channel ID.

A rule can have an IdP group and a manual grantor together, for example when an Okta group gives SSO but someone must create the account in the app. After approval, Risotto adds the person to the group, then sends the manual step to the grantor.

When the grantor confirms the step with I created the account, or I deprovisioned the account for a removal, Risotto closes the loop in the requestor's thread. It posts a short message, for example "Your Asana account has been created. ✅ I've sent you the details in a direct message.", resolves the ticket, and asks the requestor whether the run did what they expected. Details the grantor entered, such as a temporary password, go to the grantee in a direct message. If Risotto cannot send that direct message, it posts the details in the ticket thread instead. When the request was made for someone else, the message names that person's account instead.

The grantor can confirm I created the account after the request ended, for example when the requestor canceled it or the ticket was resolved or closed. Risotto then records the grant, but it does not change the ticket status and posts nothing in the requestor's thread. The grantee still gets the direct message with the details. A time limit starts when the grantor confirms. In Slack, the grantor's message says "The request had already ended. The grant is recorded; the ticket is unchanged."

If the request was denied, Risotto does not record a grant. In Slack, the grantor's message says "This request was denied, so no access was recorded. Remove the account if you already created it." In Microsoft Teams, Risotto replaces the card for everyone who can see it. The new card has no button. It says that the request was denied, that no access was recorded, and that the grantor must remove the account if they already created it. If Risotto cannot replace the card, the grantor gets a direct message with the same information.

To send the grantor instructions with each request, fill in Grantor message in Additional settings.

Approval

The Approval card sets who must approve a request, and which requestors the approvers apply to. In edit mode, the Approval policy field selects one of two modes:

  • A policy is selected: the card shows the policy's rules in a read-only table. Each request goes to the first rule the requestor matches. Requests that match no rule are denied. Click View policy to open the policy. To make a new policy, select Create a new policy, which opens Approval Policies in a new tab. See Approval Policies.
  • No policy: the card shows three settings for this rule only: Requestor profile, Requestor group membership, and Approvals.

If the selected policy was deleted, the card says "The policy this access rule pointed to has been deleted. Choose another, or create approval rules for this rule only."

Requestor profile

Select Any profile, or select Profile must match conditions to apply the approvers only to requestors whose IdP profile matches.

Each condition has a field name (for example department), a data type (String, Number, or Boolean), an operator, and a value. The field name is free text: enter the name your identity provider uses for the field. Field names and values are case-sensitive and must match your IdP exactly.

To match a custom attribute, enter its name as your identity provider stores it:

  • Okta: the attribute's variable name from the Okta profile editor.
  • Google Workspace: the custom schema name and the field name, joined by a dot, for example employmentData.projects.
  • JumpCloud: the custom attribute's name.

Rules cannot read a custom attribute from Microsoft Entra ID. For Entra, a rule reads only the standard profile fields. For Google Workspace and JumpCloud, a custom attribute that has the same name as a standard profile field (for example department) does not replace that field. The rule reads the standard value.

A field can hold more than one value, for example a Google Workspace field with many values or an Okta string array. The rule reads every value:

  • Equals, Contains, Starts with, Ends with, and the number comparisons match when one of the values matches.
  • Doesn't equal and Doesn't contain match only when no value is the one in the condition. For example, a user whose role holds admin and viewer matches role Equals viewer, but not role Doesn't equal admin.

When the rule does not match, the reason lists every value, for example User's `role` is 'admin', 'viewer', but must not equal 'admin'. A Related IdP user row reads only the first value of the field.

The rule builder works in two levels. With one condition, the header reads Must match this condition. With more than one item, it reads Must match with a selector: Any condition or Every condition (Any condition group or Every condition group when the items are groups). Each group has its own Any / Every selector and contains one or more conditions. Click Add condition to add a condition, and Add condition group to add a group. Click the remove icon to remove a condition, and the trash icon to remove a group.

For example, to allow full-time employees in either engineering or product, use two groups and set the header to Every condition group. In the first group, select Any and add department Equals engineering and department Equals product. In the second group, add employeeType Equals fte.

Below the builder, the Test profile rule card checks a user against the rule. Select a user, and the card shows Rule matches or Rule does not match.

Requestor group membership

Select Any group, or select Only requestors in specific IdP groups to apply the approvers only to requestors in the IdP groups you choose. Click Add group to add a group. With two or more groups, choose whether the requestor must be in Any group or Every group. The Test group membership card checks whether a user you select is in the required groups.

Approvals

Select No approval needed, or select Require approval to set approvers. Each approval step has a type and a value. Click Add approval step to add a step, and click the remove icon on a step to remove it. The approver types are:

  • Direct message: a specific person, by email address.
  • IdP group: any member of the selected identity provider group.
  • Channel: any member of a Slack channel. Search for the channel or paste its ID.
  • Related IdP user: a user named in a field of the requestor's IdP profile, for example manager_email. The field must hold the approver's email address. Enter the field name exactly as your identity provider spells it. The match is case-sensitive, so managerId and managerid are different fields. If the name does not match, Risotto treats the field as empty.
  • Business owner of the app: the Business owner email set on the application. This type works for access requests only. If the application has no business owner email, Risotto cannot ask this step. With All of them, Risotto then cancels the request and escalates the ticket. Set the email in Application details.

With one step, the header reads One approval step. With two or more steps, it becomes Ask steps [In order | At the same time] and require [Any one | All of them]:

  • In order (the default) asks approvers one at a time in the listed order, and you can drag steps to reorder them. At the same time asks every approver at once.
  • Any one (the default) grants access as soon as one approver approves. All of them waits for every approver.
  • In order and Any one together let Risotto pass an unanswered request on to the next approver after the delays in Notifications. An approver who was passed over can still approve. Any one approval grants access.
  • The order and the requirement apply to the whole chain. You cannot ask some steps in order and other steps at the same time.
  • Every approver gets Approve and Deny. There is no notify-only step for a person who should see the request but not decide it.
  • An approver must click Approve or Deny in the approval message. A reply such as "Approved" typed in the ticket thread does not record a decision and does not grant access. While the request waits for approval, Risotto does not act on new messages in the thread.

For a Related IdP user step, Risotto reads the field from the IdP profile of the person who receives the access. If the field is empty, does not hold an email address, or names a person who is not in your chat workspace, Risotto skips the step:

  • With Any one, Risotto asks the other approvers. It escalates the ticket only if it cannot ask any approver.
  • With All of them, Risotto cannot get every approval. It cancels the request, escalates the ticket, and notifies org admins ("Approval routing failed").

Two switches at the bottom are off by default:

  • Require a reason on denial makes an approver give a reason when they deny the request.
  • Prevent self-approval stops the user the request is for from approving it. Risotto compares each approver with the person who receives the access, not with the person who opened the request. A manager who requests access for a direct report can approve it. The direct report cannot. See Approval policies for what happens when every approver is skipped.

If no one responds

Turn on If no one responds to ask one more approver when nobody answers, and then escalate the ticket. The setting reads: After [48 hours] also ask [approver]. If still no answer after [24 hours] then Escalate the ticket. Set each wait in minutes or hours, from 15 minutes to 7 days, and choose the extra approver from the same types as an approval step.

The switch is off and can't be turned on for a chain of two or more steps set to In order and Any one, because that chain already passes an unanswered request to the next step. Add the extra approver as the last step instead.

Additional settings

  • Reason required?: when on, Risotto asks the requestor for a reason for access. The reason is logged in the ticket and passed on to the approvers.
  • Reason instructions: shows when Reason required? is on. Describe what an acceptable reason must cover, for example "The reason must name the project or customer the access is for." Risotto asks the requestor for these specifics and checks their reason against them.
  • Allowed Duration: the shortest and longest time a requestor can ask for. Select each value from 1 hour, 8 hours, 1 day, 1 week, 1 month, 3 months, or Custom (a number of hours, up to 8,760). Set the longest to Unlimited for no limit. To fix one duration, set both to the same value. A new rule allows 1 hour to Unlimited.
  • Renewal prompts: shows only when the longest Allowed Duration is not Unlimited. On by default. When on, the expiry reminder offers a one-click extension. When off, the reminder tells the user to ask for an extension in a new request, which goes through this rule again, approvals included. See Renewing time-limited access.
  • Require approval on renewal: shows only for time-limited rules with Renewal prompts on. Off by default. When on, the one-click extension runs this rule's approvals again instead of extending the access at once. It has an effect only when the rule requires approval.
  • Max users allowed: the most people who can have this access at once (0 is unlimited). When a request comes in and the group is above this number, Risotto escalates the request to a person. Set it at or near your contracted license count, so your team can step in before licenses run out.
  • Keywords: a comma-separated list of words that help Risotto match a request to this rule. For example, if people ask for the "OKR tracker" when they mean Asana, add okr tracker. When you name a rule that has no keywords, the keywords fill in with the name in lowercase. A keyword of one rule matches that rule only, not every rule of the application.
  • Grantor message: the message Risotto sends the manual grantor with each request, for example a reminder of what they need to do.
  • Custom response: a message Risotto sends the requestor after access is granted, or at once when the rule has no group and no manual grantor.

A requestor can ask for a duration in minutes (for example, "for 30 minutes"). The ticket and the Access Grants page show the exact duration (for example, "10 minutes"). The Allowed Duration values stay in hours and days, so a request shorter than the shortest duration is refused.

An approval cannot depend on the duration that the requestor asks for. To require a different approval for longer access, make two rules for the application, each with its own Allowed Duration and approvals, for example "Tier 1, up to 30 days" and "Tier 1, permanent". Give each rule a name that tells requestors which one to ask for.

Risotto also matches a request that names the rule's Identity Provider Group by its name in the IdP (for example, "can I get access to og_aws_standard"). You do not need to add the group name as a keyword. Risotto stores the group name when you save the rule and refreshes it nightly, so a group you rename in the IdP matches under its new name after the next refresh.

If a request for access matches more than 50 access options, Risotto does not guess. This can happen when a broad word such as "Billing" partly matches many apps, for example in a large Opal catalog. The agent first searches again with the application name and the access type that the request names. It asks the requester for the exact access type name only when the request names none. This limit applies to requests for new access only. A request to remove access still searches every rule.

Renewing time-limited access

When 70% of a time-limited grant has passed, Risotto sends the person who has the access one direct message in Slack or Microsoft Teams. For example, for an 8-hour grant the message comes about 2 hours and 24 minutes before the access expires. It says when the access expires and asks "Would you like to extend your access by another" duration, with the buttons Yes, extend access and No.

What Yes, extend access does depends on the rule:

Rule settingsWhat happens
Renewal prompts on, Require approval on renewal off (the default)Risotto grants the same access again for the same duration, counted from the click. Approvers are not asked again.
Renewal prompts on, Require approval on renewal onRisotto sends the rule's approval requests again, with the original duration and reason. The user sees "Renewing your access to ... requires approval". The current access keeps its expiry while the approval is pending. When approved, the new period starts at the approval.
Renewal prompts offThe reminder has no buttons. It ends with "You can extend access by requesting an extension in a new thread." A button from a reminder sent before you turned the setting off replies "Sorry, this access can no longer be extended from the reminder."

If the ticket of a renewal that waits for approval is resolved, closed, or marked as a duplicate, Risotto cancels the renewal and sends the person a direct message, for example "Your request to renew your access to Figma was cancelled because its ticket was resolved. Your current access still ends on ... Start a new request if you still need access." If Risotto cannot send a direct message, it replies on the ticket.

No closes the reminder and makes no change. When nobody responds, Risotto removes the access when it expires and adds the comment "Time-limited access has expired and has been revoked." to the ticket.

Users who are already in the group

Risotto does not remove members that it did not add. To see these members, use the check in Group members without a Risotto grant. When a time-limited grant that Risotto made expires, Risotto removes that person from the group. Risotto does not add the person back to a group that they were in before the request.

If a person who is already in the group requests access:

  • With a time-limited rule, Risotto records the grant with its expiry. When the grant expires, Risotto removes the person from the group, even though they were in the group before the request.
  • With a rule that is not time-limited, the request fails because the person already has access.

To put existing members on a time limit, ask them to request access through the time-limited rule.

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