Permissions
Which permissions gate the Service Desk module, replying to customers, managing requesters and the portal, configuring the desk, and reading reports. Plus why the module or a button can disappear.
On this page
Service Desk uses the same role system as the rest of DevStride. A member's role decides what they can do with the desk, organization-wide.
The Service Desk permissions#
| Permission | Grants | Typical for |
|---|---|---|
| Access Service Desk | See the Service Desk module and its Inbox, Requesters, and Companies tabs. | Anyone who handles tickets. |
| Send Public Replies | Send Reply to customer messages, choose a Unified ticket description, share a ticket's file with the customer, post public comments on knowledge-base articles, and include a message to the client when opening a ticket for them. Without it, a member adds internal notes only. Requires Create Comment. | Front-line agents. |
| Manage Requesters | Create, edit, block, merge, and anonymize requesters, including correcting a requester's email and resending its confirmation; create and edit companies and their portal settings; open a ticket for a client with New ticket in the Inbox, by email, or by forwarding the client's email to the desk (each with Create Items and Workstreams); convert items to tickets; change a ticket's requester; copy people on a ticket, or stop copying them (with edit access to the ticket); merge tickets; and see the Held for review, SLA at risk, and Rejected mail tabs. | Support leads. |
| Send Items For Client Review | Send a work item to a client company for review in its portal, and withdraw a review that is still waiting. The Owner and Admin roles hold it; any other role gets it only when an administrator adds it. | Account managers and project leads. |
| Manage Service Desk Settings | Enable or disable Service Desk; manage inbound addresses, your team's own mailboxes and sending domains (Settings → Email), request forms, schedules, SLA policies, and the default business schedule; and switch headless mode, status-change emails, the customer portal and the help centre. Requires Access Settings. | Administrators. |
| Manage Portal SSO | Add, edit, test, enable, disable and remove the identity-provider connections under Settings → Service Desk → Single sign-on, and choose which companies' portals offer company sign-in. Requires Access Settings. The Owner and the Admin role hold it; any other role gets it only when an administrator adds it. | Administrators who manage customer identity. |
Two permissions from elsewhere also matter:
| Permission | Grants |
|---|---|
| Read report throughput (Reports) | The Service Desk Reports tab. Access Reports is additionally needed to export a report to CSV. |
| Manage Work Types (Data model) | The Customer visibility setting that decides which custom fields customers can see or edit in the portal. |
Mix them to fit the job
Give an investigating engineer Access Service Desk without Send Public Replies: they can read tickets and add internal notes but can't email a customer by accident. Front-line agents add Send Public Replies; leads add Manage Requesters; administrators add Manage Service Desk Settings.
The Service desk agent role template#
The built-in Service desk agent template bundles the Service Desk permissions, including Send Items For Client Review, plus Read report throughput and the comment, item, and settings permissions they depend on. Apply it when creating a role for your support team and remove what you don't want (most often Manage Service Desk Settings). Or build a custom role from scratch; see Roles & Permissions.
The built-in Owner and Admin roles already hold every Service Desk permission.
Why the whole module disappeared#
Two independent gates must both pass for Service Desk to appear in the left navigation:
- An administrator has enabled Service Desk for the organization (Enabling Service Desk).
- Your role includes Access Service Desk.
If a teammate can see it and you can't, it's your role. If nobody can, the module was disabled.
Why a button disappeared#
DevStride hides actions you lack permission for rather than greying them out. A missing button after a role change is not a bug.
| If this is missing… | You're missing |
|---|---|
| Reply to customer (Internal note still available) | Send Public Replies |
| Share with customer on a ticket's file | Send Public Replies |
| Held for review, SLA at risk, or Rejected mail tab; Block / Merge / Anonymize, Edit email…, or Resend confirmation on a requester; Change requester…, Convert to ticket, Merge tickets | Manage Requesters |
| New ticket in the Inbox | Manage Requesters and Create Items and Workstreams |
| Add person by name or email, or the x beside a name, in a ticket's Copied list | Manage Requesters |
| Send for client review, Withdraw on a client review | Send Items For Client Review |
| Reports tab | Read report throughput |
| Export CSV on Reports | Access Reports |
| Enable / Disable Service Desk; Inbound addresses and Sending domains (Settings → Email), Request Forms, Schedules, SLA Policies | Manage Service Desk Settings |
| Single sign-on settings; the Portal sign-in section on a company | Manage Portal SSO (the company section also needs Manage Requesters) |
| The whole Service Desk nav entry | Access Service Desk, or the module is disabled |
Permission changes take effect the next time you reload DevStride.
Some actions refuse even when you hold the permission
Manage Requesters lets you merge and anonymize requesters, but DevStride refuses either on a requester whose email belongs to an active member of your organization, because that address appears on other people's tickets. Removing the member lifts the refusal without making the action safe; contact support instead. See Requesters & Companies.
A note on requesters#
Requesters are not governed by these permissions. They hold no role and can't sign in to your workspace, only to your customer portal, a separate portal-only login that never reaches your workspace. These permissions are entirely about what your team can do.