OpsDesk
A multi-tenant support and incident platform with real authorization, SLA logic, and operational workflows.
Quick read
The project in a few seconds.
Multi-tenant
Workspace-isolated application data.
4 roles
Owner · Admin · Agent · Viewer
Ticket → Incident
Escalation, ownership, and history.
Persisted SLAs
First-response and resolution targets.
How it works
The project from input to outcome.
Workspace
Tenant boundary
Services
Operational ownership
Tickets
Assignment + priority
Incidents
Escalated issues
SLA + History
Deadlines + activity
My contribution
The pieces I directly worked on.
Built multi-tenant workspaces with Owner, Admin, Agent, and Viewer roles.
Enforced permissions and workspace boundaries on the server instead of relying on hidden UI controls.
Built ticket creation, assignment, status, priority, and activity-history workflows.
Added ticket-to-incident escalation and incident lifecycle tracking.
Implemented priority-based first-response and resolution SLAs.
Added automated tests for important authorization and business rules.
Engineering proof
A few decisions that show what was happening under the surface.
Decision 01
Used the workspace as the tenant boundary so workspace-owned data can be isolated consistently.
Decision 02
Separated authentication from authorization: Clerk identifies the user, while OpsDesk determines what that user can do.
Decision 03
Scoped database queries by workspace instead of trusting a ticket or incident ID by itself.
Results
The proof that the build came together.
Built a working multi-tenant operations platform with authenticated workspaces.
Implemented server-enforced role-based permissions.
Created a complete service-to-ticket-to-incident workflow.
Added persisted first-response and resolution SLA tracking.
Product
See the work instead of only reading about it.
Workspace overview showing the operations dashboard and current support workload.
Ticket view showing priority-based first-response and resolution SLA tracking.
Incident workflow used to manage escalated issues and ownership.
Deep dive
Optional technical detail if you want to go deeper.