Insights

45%autosolved (504 of 1,120 tickets in the last 90 days)
90automatable, of 264 classified tickets
  • Autosolved504 · 45%
  • Automatable today29 · 2.6%
  • Automatable with setup61 · 5.4%
  • No automation path found174 · 15.5%
  • Not classified352 · 31.4%

Tickets that cite an opportunity, last 90 days

Opportunity
Type
Tickets
Action
Access: Salesforcerequested: read-only (9) · plain access (14)
Create access rule23
Runbook template: Okta Password Reset
Use runbook template17
Tool: Add to Google Group
Did not auto-resolve29
Tool: Create Slack Channeldisabled
Finish setup21Enable tool

Assistant

Check whether Risotto has an application and access rules for Salesforce, and create what is missing to cover the 23 tickets that cite it. Requested: read-only (9 tickets); plain access (14 tickets).

Salesforce is in your app catalog, but no access rule covers it. Here are two rules with manager approval. New rules start as drafts, so they grant nothing until you turn them on.

Tool approvalAwaiting Approval

Risotto wants to run this action. Approve to continue, or deny to skip it.

Tool
Create Access Rules
Rationale
Two Salesforce rules: the requester's manager approves, then Risotto adds them to the Okta group for read-only or standard access.
Parameters
rules
[
  {
    "software_name": "Salesforce (read-only)",
    "approvers": [
      {
        "type": "approver_profile_field",
        "value": "manager"
      }
    ],
    "security_group_name": "Salesforce Read Only",
    "id_provider": "okta"
  },
  {
    "software_name": "Salesforce",
    "approvers": [
      {
        "type": "approver_profile_field",
        "value": "manager"
      }
    ],
    "security_group_name": "Salesforce Users",
    "id_provider": "okta"
  }
]

Both rules are saved as drafts. Turn them on, and the next Salesforce request goes to the requester's manager, then into the right Okta group.