Preferences, workspace configuration, and data management
Per-browser settings — no account system exists in this app, so these live only on this device
Table density
Applies to every list's table, everywhere in the app.
Reset browser data
Favorites, recently-viewed history, saved list filters, and your remembered comment name are all stored only in this browser — nothing here touches the underlying records.
Project 77 — Virtual Assistance
Boston small-multifamily back-office & support operations
Boston, MA · single-workspace deployment
Stage definitions — stage-gated fields are enforced on every write path; backward moves stay free
Guardrails enforced on save: a workflow can't reach Workflow mapping without an SOP attached, Pilot without a pilot start date, or QBR without a last-QBR date — the pipeline board, inline selects, bulk actions, and edit forms all run the same checks. A ticket moved to Resolved or Closed gets its resolved time stamped (never clobbering an existing one); reopening clears it.
Resolution windows per category and priority — the derived SLA state everywhere comes from these
7 policies configured. Manage SLA metrics →
A ticket matches the policy for its exact category + priority at create/edit time; creating a new policy backfills matching tickets that had none. Tickets turn at risk past 75% of their window and breachedpast it. Deleting a policy detaches its tickets (they show "No SLA", never an error).
How this workspace records data
This is a seeded demonstration workspace
Clients
5
Workflows
9
SOPs
6
Tickets
13
SLA policies
7
21h/week under management across 3 managed workflows. Records created in this demo persist for the life of the current server instance; the workspace resets to its seed data on the next cold start or redeploy.