ⓘ Demo mode: read-only demonstration. Changes are disabled — request full access.
DEMO MODE
Changes are disabled in the demo.
You are viewing a read-only demonstration. Browse everything freely — adding, editing and deleting are switched off so the demo stays tidy for everyone.
For each screen we answer the same questions — what it is, why it exists, how to use it, who it is for, and what business problem it solves.
Users & Staff
Every account that can log in — administrators, support staff and customers — and exactly what each of them may do.
What is it?
The central register of accounts. Each carries a name, email, role, department membership, permission set, status and two-factor state. From here you create staff, promote or demote, suspend an account, or reset access.
Why does it exist?
Access is the foundation of accountability. If everyone can do everything, nothing can be traced; if nobody can do anything, work stops. This screen is where that balance is set — and where a departing employee is switched off in one action.
How does it work?
1Create the account with a name, email address and role (admin, staff or client).
2Assign the departments the person works in — this decides which tickets they see.
3Grant or withhold individual permissions such as deleting tickets or viewing reports.
4Require two-factor authentication for administrators and anyone handling sensitive data.
5Deactivate rather than delete when someone leaves — their ticket history stays intact.
WHO USES IT
Administrator
WHAT MANAGEMENT ACHIEVES
Onboarding and offboarding become one screen and one minute, with no orphaned tickets and no shared passwords.
In practice
A support executive resigns on Tuesday. The administrator deactivates the account, reassigns eleven open tickets to the team lead, and every past conversation stays readable in the customer records.