Feature documentation
Client Portal & Client Logins
Your clients get a portal. Your data model knows they are clients.
Client users sign in through the same identity provider as your staff but come out the other side with a genuinely different product: their company’s tickets only, the public conversation only, and exactly the actions a client should have — raise a ticket, reply, attach a file. Not a staff dashboard with buttons that error; a client experience with no staff tooling to trip over.
Scoped by company, enforced by the server
A client user belongs to one client company. Company administrators see all of that company’s tickets; regular users see their own. The scoping is applied in every query on the server — there is no client-side filter to bypass, and a ticket outside the caller’s company is indistinguishable from one that does not exist.
Least privilege by construction
A client login carries exactly the permissions client-reachable endpoints need — create a ticket, add a public note — and nothing else. Staff-only controls (status changes, assignment, time tracking, internal notes) are absent from the client’s pages and refused by the API if requested anyway.
Provisioning clients
Invite client users by email — the account binds to their identity on first verified sign-in — or import your PSA’s existing contacts for a company in one action, matched on the PSA contact id so re-imports update rather than duplicate.
Keep your PSA. Upgrade your client experience.
Desk Portal gives your clients a modern support experience while your team continues working in the PSA they already know.