Service Desk is an opt-in module. Until an administrator enables it, the Service Desk nav item stays hidden and its settings don't apply. Turning it on is a single, reversible switch.
Enablement is instant; nobody needs to sign out. You can also enable it from the module itself: clicking Service Desk in the sidebar before it's on shows a "Service Desk isn't enabled" page with an Enable Service Desk button for administrators. Members without the permission see a note asking them to contact an administrator.

| You get | Where |
|---|---|
| The Service Desk module with its Inbox, Held for review, SLA at risk, Rejected mail, Requesters, Companies, and Reports tabs (some tabs depend on your permissions) | Left sidebar |
| Request Forms, Schedules, SLA Policies, and the Default business schedule | Settings → Service Desk |
| Inbound addresses and Sending domains | Settings → Email |
| Ticket fields on work items: a Requester, a separate Customer description, and the Reply to customer / Internal note choice on comments | Any ticket |
| Two saved Inbox views: All open requests and Unassigned | Service Desk → Inbox |
| One automation, Auto-close solved tickets after 4 days, which emails the requester when it closes their ticket | Automate Workflows |
The seeded automation is an ordinary automation: edit the threshold, add conditions, pause it, or delete it. It runs immediately for a brand-new desk. If you re-enable a desk that already has tickets, it arrives paused so you can review it before it touches your backlog. See Time-Based Ticket Automations.
Nothing receives email yet. That starts when you create a channel address and forward your inbox to it: Email Channels & Setup.
The same Settings → Service Desk panel holds the Default business schedule. Pick one of your schedules here and every ticket whose team has no schedule of its own is measured against it by business-hours automations. Leave it empty and business-hours conditions count calendar time, nights and weekends included. If your organization has exactly one schedule, it is adopted as the default automatically.
The same panel's Customer communication group holds these switches:
| Switch | Default | Off / on means |
|---|---|---|
| Headless mode | Off | On: DevStride sends nothing to your customers; each message goes to your webhook endpoint for your own tool to send. |
| Email customers on status change | On | Off: customers are not told when their request changes status. |
| Show the replying staff member's name in emails | On | On: reply emails come from the staff member who replied, for example Jane Doe (Acme Support), and say who replied. Off: they come from your desk name only. |
| Send roadmap release updates automatically | Off | Off: the plan's owner approves the wording of each release update to a linked ticket before it is sent. On: updates go out as soon as the release is live, without approval; DevStride asks you to confirm before turning it on. |
| Share new ticket files with the customer | Off | Off: every file added to a ticket starts private until someone shares it. On: a file or link your team adds to a ticket starts shared and shows on the customer's portal ticket straight away; DevStride asks you to confirm before turning it on. |
| Customer portal | On | Off: the customer portal closes and portal links disappear. |
| Only signed-in customers can submit requests | Off | On: customers must sign in to the portal before they can submit; forms marked public keep their open link. |
| Help centre | On | Off: the portal's knowledge base closes. |
See Headless Mode and Customer Switches for what each one closes.
On Settings → Service Desk, click Disable Service Desk and confirm. Disabling is reversible: tickets, requesters, companies, conversations, and each company's portal settings are kept, and re-enabling restores everything. While it's off:
Overview
Service Desk turns customer email and form submissions into DevStride work items your team can triage, answer, and track. What it is, the five ideas behind it, and where to start.
Email Channels & Setup
Create a channel address, forward your support inbox to it, and choose where tickets land. How inbound mail becomes a ticket, who a customer's email copies onto it, how replies thread, who a forwarded message is credited to, and what removing an address does.