Service Desk started as email. Now your customers have a home of their own: a branded, self-service Customer Support Portal at your company's own web address. It's a fast, mobile-friendly page that lives separately from your team's DevStride workspace — your customers sign in there, and only there, and can never reach your boards, your data, or anyone else's company.
This first release delivers the portal itself and how customers get in: branded sign-in, passwordless login, and per-company access controls. The in-portal experience where customers browse and manage their requests is coming next (see What's next below).
No passwords, ever. Getting into the portal takes seconds:
Security is built in quietly. The response after entering an email is identical whether or not that address can access your portal, so the portal can never be used to fish for who your customers are. Login links and codes expire after 15 minutes, and a code is retired after a handful of wrong guesses.
Each company you support gets its own portal look, set right on the Company record under Service Desk → Companies:
Set nothing and the portal falls back to a clean, neutral DevStride shell — so it always looks finished. Every portal carries a discreet "Powered by DevStride" in the footer.
Also on the Company record, choose an access mode that fits how open you want the portal to be:
Access is re-checked on every visit, so it's always current. The moment you block a requester, erase them, move them to a different company, or turn Service Desk off, their access to the portal ends immediately — no waiting for a session to time out.
The portal auto-detects each visitor's language from their browser, and you can set a Default language on the company record as a fallback. English is available today, with the groundwork in place to add more languages down the road.
Erasing a requester ("right to be forgotten") is now thorough and final. When you erase someone, DevStride removes their personal information everywhere it was kept — their name, email, and phone; the original message that started their ticket; their personal details inside notifications and the activity log; and anything tied to their portal sign-in.
An erased requester cannot be quietly brought back — a later email from that person won't silently re-create or re-identify them. Tickets your team worked on are kept, but stripped of who they belonged to, so your history stays intact without the personal data.
⚠️ Erasure is permanent. Erasing a requester cannot be undone or reversed. Once it's done, the personal data is gone for good. Reach for Merge instead when you're consolidating duplicates you want to keep.
We also tightened protection on the public-facing parts of Service Desk — the request form and portal sign-in — so bursts of automated or abusive traffic are throttled before they reach your team. There's nothing to configure; it just runs.
The company dialog under Service Desk → Companies — where all of the portal settings above live — picked up three improvements of its own:
Acme.COM and acme.com can't sneak in as two entries.Whatever primary color a company's portal is given, the portal now keeps it readable: brand colors are automatically adjusted to accessibility-contrast-safe (WCAG) variants wherever they back text and controls. Pick a very light brand color and the portal quietly renders a readable derivative of it — your brand still shows through, and nobody squints at an unreadable button.
One fix in the same area: signing in to one company's portal no longer carries over to a different company's portal in the same browser. Each portal keeps its own sign-in state, cleanly separated.
📚 Full guide: the new Customer Support Portal page in the Service Desk docs.
Email and Slack notifications now travel through a durable delivery pipeline: if the email or Slack provider stumbles, DevStride retries automatically until the notification lands — without ever sending it twice. There's nothing to configure; deliveries are simply more dependable.
💡 What's next: This release opens the door — sign-in and branding. Coming next is the experience inside the portal: a My Requests list, a full conversation view so customers can follow and reply to their tickets, self-service request submission, and a knowledge base. Further out on the roadmap: service-level (SLA) timers and more channels beyond email, like Slack and Microsoft Teams.
2026-07-12
A maintenance release: statuses with an emptied work-type restriction behave correctly again (un-blocking Service Desk auto-close for affected desks), status deletion gets a safety cap, cycle filters stop over-returning, and the Support Request form keeps its template.
2026-07-17
For API and MCP users: 'lane' is now 'status' across requests, responses, and MCP tools. Existing integrations keep working — legacy names are accepted through a deprecation window. Nothing changes in the app itself.