TDesk

TDesk technical documentation

Admin workspace

Trace each screen to its assets and replace the local demo state one workflow at a time.

Find the right files

AreaLocationResponsibility
Shellassets/css/admin.css + assets/js/admin.jsSidebar, header, page search, dialogs, validation, storage, and feedback.
Tickets, inbox, knowledgehelpdesk.css + helpdesk.jsTicket list, thread, drafts, replies, knowledge base, article editor, and canned replies.
People and settingsworkspace.css + workspace.jsCustomers, agents, roles, policies, activity, and workspace preferences.
Library and authenticationkit.css + kit.jsForms, UI examples, tables, icons, and sign-in flow previews.
Reportsoverview.js and analytics.htmlDashboard queue and illustrative reporting periods.

Change navigation and layout

  1. Update the sidebar links and matching page search links in each page, or extract the shared shell into one partial or component in your app.
  2. Keep the active item marked with aria-current; give icon-only controls accessible names.
  3. Keep id="application-nav", id="menu-toggle", and dialog IDs in sync if you keep admin.js.
  4. Use assets/css/design-system.css for token overrides and keep page styles after shared styles.

Identify the demo state

Each help desk page has an embedded #helpdesk-seed JSON block. The script reads it and overlays browser-local records under sami.admin.v1.. The queue and detail route use ticket-detail.html?id=1042. The front and admin fixtures are independent; use one shared ticket API to connect them.

Queue URLs can carry status, priority, or agent. Customer detail has an id parameter. Keep a stable public ID and update both list links and detail routes together.

Forms with data-validate emit sami:valid after local validation. To connect a form, replace its demo listener with your own submit flow. The shared script cancels native submit; for regular server POST forms, remove that interception for the forms you migrate and enable their submit buttons through the actual implementation.

Passwords are not saved and the demo account screens do not grant access. Do not use local storage or the demo role matrix as an authorization boundary.

All 33 admin pages

PagePurpose
index.htmlOverview
activity-log.htmlActivity log
analytics.htmlAnalytics
article-editor.htmlArticle editor
automations.htmlAutomations
canned-responses.htmlSaved replies
customer-detail.htmlCustomer profile
customers.htmlCustomers
documentation.htmlDocumentation
error-403.html403 — Access denied
error-404.html404 — Page not found
error-500.html500 — Server error
forgot-password.htmlForgot password
form-validation.htmlForm validation
forms.htmlForm elements
icons.htmlIcon library
inbox.htmlInbox
knowledge-base.htmlKnowledge base
lock-screen.htmlLock screen
login.htmlSign in
maintenance.htmlMaintenance
reset-password.htmlReset password
roles.htmlRoles & permissions
settings.htmlSettings
signup.htmlSign up
sla.htmlSLA policies
tables.htmlData tables
team.htmlTeam members
ticket-create.htmlCreate ticket
ticket-detail.htmlTicket conversation
tickets.htmlAll tickets
ui-components.htmlUI components
verify-email.htmlVerify email