Skip to content
ThinkWork ThinkWork

Admin - Spaces

Admin Spaces is where operators create and configure contextual workrooms for the tenant platform agent. A Space can represent a team, customer, project, workflow, inbox, or channel-bound room with its own workspace context, knowledge, triggers, access, and local policy.

Spaces also own the reusable templates for Goal-driven workflows. A Goal template is a folder of markdown files in the Space workspace that explains a repeatable outcome, progress model, completion rule, review policy, decisions, artifacts, and handoffs.

For a practical walkthrough of how to design one, see Build a Space. This page stays focused on the Admin UI surfaces.

The Admin UI has two levels:

  • Spaces list: /spaces
  • Space Studio: /spaces/:spaceId, which redirects to /spaces/:spaceId/workspace

Space Studio tabs appear in this order: Workspace, KBs, Triggers, Settings, and Members. The Members tab appears only for Private Spaces.

Read this section

Section titled “Read this section”

Start with Spaces list if you are creating or finding a Space. Then open the page for the tab you are configuring.

Spaces list The `/spaces` table, creating a Space, and opening Space Studio.
Workspace Space-local files for procedures, customer context, project notes, and workroom instructions.
KBs Knowledge-base selection for the Space.
Triggers Schedule, Webhook, and Email triggers that create or wake work in the Space.
Settings Space name, access mode, and description.
Members Private Space membership and access control.

What belongs here

Section titled “What belongs here”

Use Admin Spaces when the operator decision is local to a workroom:

  • local workspace files;
  • Space-owned Goal templates for repeatable workflows;
  • selected knowledge bases;
  • schedules, webhooks, or Space email triggers;
  • Public or Private access;
  • Private Space membership.

Use Tenant Agent for tenant-wide platform-agent defaults and baseline workspace behavior. Use tenant MCP and built-in tool pages for registration of capabilities that Spaces can make available.

Authoring Goal templates

Section titled “Authoring Goal templates”

Use the Space workspace when a workflow belongs to that Space’s operating pattern. Customer Onboarding is the reference example: the Space source contains a goals/customer-onboarding/ folder with:

GOAL.md
PROGRESS.md
DECISIONS.md
ARTIFACTS.md
HANDOFFS.md
stages/

The template should say:

  • the outcome in plain language;
  • whether the default mode is Delegate or Collaborate;
  • which structured progress model the workflow uses;
  • what must be true before completion;
  • who should review high-risk work;
  • what decisions, artifacts, and handoffs should be captured for Company Brain;
  • what a local agent can still understand if the folder is exported or opened outside ThinkWork.

Keep task status, owners, permissions, and final review in ThinkWork’s structured workflow surfaces. Keep rationale, examples, source notes, and handoff guidance in markdown.

Operator placement rules

Section titled “Operator placement rules”
ConfigureUse it for
Tenant AgentTenant-wide model, budget, sandbox, root behavior, routing, and folder specialists
SpaceCustomer, project, team, workflow, inbox, channel, access, triggers, tools, and local policy
Goal templateA repeatable outcome contract inside a Space
Goal instanceOne promoted Thread executing that outcome
Company BrainReviewed learning distilled from completed Goals and other curated sources
Section titled “Related pages”