Docs

Admin / People and roles

Permissions System

How organization roles and department roles combine in Risotto, and why ticket access always comes from department membership

Overview

Risotto controls access at two levels:

  • Your organization role (Admin, Manager, or Member) is one role for the whole organization. It decides who sets up Risotto: organization settings, integrations, tools, departments, automations, and campaigns.
  • Your department roles (Supervisor or Agent) are set per department. They decide which tickets you see and what you can do with them, plus each department's analytics, runbooks, articles, settings, and members.

Tickets and analytics come only from department roles. An Org Admin who belongs to no department sees no tickets. An Org Admin can add themselves to any department, and then sees its tickets like any other member.

Organization roles

  • Admin: full organizational control, including the members of every department and automations.
  • Manager: manages organization settings, integrations, tools, and departments, but cannot add or remove department members.
  • Member: no organization setup. Everything else comes from department roles.
PermissionAdminManagerMember
Manage organization settings✅✅❌
Create and delete departments✅✅❌
View and edit department settings✅✅As a department Supervisor
Add and remove department members✅ (any department)As a department SupervisorAs a department Supervisor
Map directories to departments (Directory Sync)✅❌❌
Connect integrations and create tools✅✅❌
Create, test, and publish script tools✅✅❌
Manage the Credential Vault✅✅As a department Supervisor
Use the Assistant✅✅As a department Supervisor
Set the Assistant approval mode limit✅✅❌
See all Assistant sessions✅❌❌
Remove ticket comments and notes✅❌❌
See, create, edit, and run automations✅❌❌
View and edit draft campaigns✅✅✅
Create, launch, and delete campaigns✅✅❌
Create and edit runbooks✅✅As a department Supervisor
Read knowledge base articles✅✅✅
Create, edit, and delete org-wide articles✅✅❌
Export articles to Guru✅✅❌
Connect an MCP client with OAuth✅✅✅ (Member scopes only)

Department roles

  • Supervisor: full control within the department: tickets, analytics, runbooks, articles, settings, and members.
  • Agent: handles tickets and views analytics, but cannot change department settings or members.
PermissionSupervisorAgent
See and update the department's tickets✅✅
Delete tickets✅❌
Move tickets to another department✅✅
View analytics✅✅
View the department's runbooks and org-wide runbooks✅✅
Create and edit the department's runbooks✅❌
Create, edit, and delete the department's articles✅❌
View department settings✅✅
Change department settings✅❌
Manage the department's vault credentials✅❌
Use the Assistant✅❌
View team members✅✅
Add, change, and remove members✅❌

Ticket visibility

You see a ticket when you are an Agent or Supervisor of its department, or of that department's parent. Your organization role does not add tickets. The same rule applies to analytics and to the tickets the Assistant can read.

  • A parent department's role reaches its sub-departments. A Supervisor or Agent of IT sees the tickets of IT / Networking too, with the same role.
  • A sub-department's role does not reach the parent. A member of only IT / Networking sees that queue's tickets. They can open IT's settings pages to see what the sub-department inherits, such as the agent channel, but cannot save changes there. See Sub-departments.
  • Department roles apply only where assigned. A Supervisor in IT is not a Supervisor in People.
  • Moving a ticket needs the right to update it in its current department. An Agent or Supervisor can then move it to any department, including one they don't belong to. After the move, they see it only if they belong to the new department.

To keep a department's tickets private, give the people who must not see them the Manager or Member organization role. An Org Admin can add themselves to any department. See Ensuring users can't see sensitive tickets.

How specific features apply roles

  • Vault credentials can belong to a department. A Credential Vault credential is org-wide or belongs to one top-level department, and a department credential can be used only by that department's tools. Org Admins and Managers manage every credential. A Supervisor manages the credentials of their own departments, but cannot change a credential's department or allowed hosts. A Supervisor can create a credential in any top-level department or org-wide, with at least one allowed host.
  • Tools are created at the organization level. Only Org Admins and Managers create tools, script tools, and tool connectors. A Supervisor can add a tool to a runbook only when the tool belongs to a department that they supervise. A new tool is org-wide by default, and only Org Admins and Managers can add an org-wide tool to a runbook. A Supervisor who tries gets "<tool> is managed by the org admins. Only they can add it to a runbook." Only Org Admins and Managers can set the approval policy of a runbook or of a tool reference in a runbook. To control who can run a tool, attach an approval policy to it.
  • Automations are for Org Admins only. An automation can read tickets in every department, so only Org Admins can see, create, edit, run, or approve automations.
  • The Assistant is for Org Admins, Managers, and department Supervisors. A Supervisor can open the Assistant and Team chat on the tickets of their departments. An Agent, or a Member with no department role, cannot. The Assistant sees tickets only from the departments that you belong to, also when you are an Org Admin. Only Org Admins see the Sessions page. See The Assistant for department Supervisors.
  • Runbooks follow department membership. A Supervisor or Agent sees the runbooks of their own departments plus the org-wide runbooks. A Supervisor can create, edit, duplicate, test, and delete runbooks in their own departments. Org-wide runbooks and other departments' runbooks are read-only for them; the editor shows "This runbook belongs to another department, or applies org-wide. Ask an org admin to change it." A Member with no department role sees no runbooks.
  • Articles: everyone reads, Supervisors write their own departments' articles. Every org member can read every knowledge base article. A Supervisor can create, edit, and delete the articles of the departments that they supervise, and a Supervisor of a sub-department can also write the parent department's articles. Only Org Admins and Managers can create an org-wide article or change an article to org-wide. A Supervisor can move an article only between departments that they supervise.
  • Campaigns follow the organization role only. Department roles do not change campaign access. See Campaigns.
  • MCP scopes follow the organization role. Org Admins and Managers can grant every MCP scope. A Member can grant only the read and ticket scopes listed in Scopes and organization roles, and acts only as themselves. When a user's role changes, their MCP tokens get the new role's scopes within 5 minutes.
  • The ✍️ emoji command does not check the organization role. In Slack, anyone whose Slack email matches a Risotto dashboard user can react with ✍️ to create an org-wide article from a thread. When the last ✍️ reaction is removed from the thread, Risotto deletes that article. See Slack Emoji Cheat Sheet.

Setting up a new user

  1. Choose an organization role

    Choose Member for most people, and Manager or Admin for people who set up Risotto. See Invite users.

  2. Add them to their departments

    Add them to each department whose tickets they work as an Agent or a Supervisor. Do this for Admins and Managers too, or they see no tickets. See Members.

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