Documentation
Reference for env vars, roles, operations, and troubleshooting at v0.10.0.
- Environment Variables
Required and optional env vars for Postgres, sessions, and OAuth credentials.
- User Roles
Admin / Manager / Tech / Submitter / Viewer — what each can do, plus per-project overrides.
- Custom forms + computed fields
Project-scoped category → form → field model with per-form required, agent-only and sensitive flags, multiselect, deep-linkable new-ticket URLs, {field.slug} tags, and formula-driven computed fields.
- Ticket schedules + personal tasks
Recurring ticket templates fired on a cron schedule with an audit ledger, and owner-scoped personal tasks with one-off or recurring due dates.
- Comments and Notes
Edit, lock, and (edited) indicator semantics for comments + notes.
- Runbooks
Checklist articles authored in Trove KB (kind runbook), run from the ticket Runbook tab with per-ticket step state and canned-response pills.
- Operations
Common ops — updates, logs, password reset, wipe-and-restart.
- Inbound Email Routing
Routing precedence, agent-forward attribution, and the default landing project for multi-scope inboxes.
- Asset tags, custody log, label printing
Operator-facing asset tags, custody check-out / check-in trail, Zebra label printer with QR deep-links.
- Consumables
Supply inventory with append-only ledger — toner, drums, batteries, anything that's interchangeable.
- Troubleshooting
Cookie / redirect loops, Entra AADSTS50011, 413 Request Entity Too Large.
- Alerts
Deduped state-machined alerts page distinct from the per-event audit log. Alert rules per source decide what auto-promotes to a ticket. Dashboard widget surfaces top firing alerts.
- Inventory
Managed asset list aggregated from RMM integrations + manual entry. Asset types, custom fields, ticket linking, security posture, software list, attribute mapping.
- Knowledge Base + Trove KB
The built-in per-project KB, plus the optional Trove KB integration: collections, categories, runbooks, favorites, ticket links, suggestions, resolution drafts, knowledge briefs, signed webhooks, and an optional migration off the local KB.
- SLA — warnings, business hours, escalations
Per-priority SLA targets with pre-breach warnings + business-hours clocks. Escalation chains on warning + breach. Auto-assignment by priority with three strategies. Vendor-vs-internal pause split + time-in-status reporting.