Skip to content

Workspace

Run the workspace itself, with a clear owner for every part of it.

Who has which role, what's waiting for approval, the full audit trail, reports, support cases, reusable templates and settings — each with its own permission and its own page. Billing shows your usage, never a price no one has set.

What Workspace is

Workspace is where the workspace runs itself: roles and access, approvals, audit, reports, support, templates and settings, each with its own read and write permission.

Every action a person takes is written to one audit log, filtered only by closed vocabularies a query can be checked against — never a freeform search.

Approvals cross three families — marketing, studio and workbench — from one open queue. A requester can withdraw their own request; only a person holding that family's approve permission can decide someone else's.

Work it supports today

Each of these starts on a real page in the product. Nothing here is planned or promised.

  • Grant a role and see what it can do

    A member with a role, and a clear answer to what that role can read and write.

    1. Open Roles & access.
    2. Choose a member and grant a role.
    3. Confirm what that role can read and write.
  • Decide something waiting on you

    An open approval decided, or withdrawn if it was your own request.

    1. Open Approvals.
    2. Find a request you can decide.
    3. Approve or reject it, or withdraw your own request.
  • Open a support case and track it to done

    A case with a priority and an SLA target, visible until it's resolved.

    1. Open Support and choose New case.
    2. Set a subject, body and priority.
    3. Watch its SLA target; it counts as overdue if it slips.
  • Save a template you'll reuse

    A named template of the right kind, ready to use wherever that kind is written.

    1. Open Templates.
    2. Choose a kind.
    3. Create one with the variables it supports.

By hand: open a support case and track it

Priya Anand, a workspace admin at Halden Rowe Joinery, needs to track a billing question a member raised.

  1. Priya opens Workspace, then Support.
  2. She chooses New case and sets a subject, body and priority.
  3. The case appears with a state of new and its own SLA target.
  4. She watches it move toward done; it counts toward overdue if it slips past its target.

Fictional names. Start here: /workspace/support

Or let Noc do it

Noc plans the steps, previews every effect, asks before anything irreversible, and hands back one receipt. Autopilot is off by default.

“Noc, this support case has been answered — assign it to the person handling it, and move it to pending.”

  1. Read the support case's current state and assignee. Nothing is written.
  2. Assign the case to the member you name. Undo assigns the previous owner back.
  3. Move the case from open to pending. This can be undone, but Noc still previews the move and asks first.
Before anything irreversible
Before it changes the case, Noc previews the exact move — the new assignee, the new state — and asks for your confirmation first.
What you get back
One receipt for each step that ran, and one for the whole request, so you can see exactly what changed and who asked for it.

Capabilities this plan can use: 3. Each is registered, permission-bound and previewed.

What stays in your hands

  • Your permissions decide, every time

    Reading the audit log needs audit.read; reports need reporting.read; support needs support.read or support.write; templates need templates.read or templates.write; administering the tenant needs project.admin or tenant.admin.

  • An approval crosses a boundary you can't cross yourself

    You can always withdraw your own request; deciding someone else's needs that family's own approve permission, never just membership.

  • A virtual role carries no authority

    A virtual-role proposal may not publish, deploy, change pricing, contact customers, expand permissions or activate work — the database itself refuses any state but inactive.

The honest states

What the product really shows when there is nothing yet, when it refuses, and where this build stops.

  • What you see first

    A new workspace's Support queue is empty

    There's nothing to see until a case is opened; the first case is the one someone raises.

  • When something is refused

    A refusal names the exact permission you're missing

    Billing needs the reporting-read permission — and says so plainly, rather than showing a broken page.

  • Not decided yet

    Billing shows usage, not a price

    Billing shows your plan, a trial and your own usage; there is no price because none is set, and any change you request is recorded, never carried out automatically.

  • Not decided yet

    Virtual roles are proposed, not offered

    Three virtual-role proposals are shown for reference; none may be activated in this build until a separate, human-approved role model exists.

  • Not available in this build

    Help does not answer questions with a model

    Help is a closed, searchable article index; nothing here is answered by AI or model-backed search.

Next

To see Workspace you need a membership in a workspace. Acting needs the permissions your administrator grants.