Skip to content

Workspaces

A workspace is one installation of a persona revision. It supplies member roles, connector bindings, models, and grants. It also keeps run state, approvals, outputs, and shared records.

The adopted persona revision supplies teams, playbooks, schemas, and logical requirements. The workspace stores local member roles, bindings, records, approvals, schedules, and history. Bindings can differ even when two workspaces adopt the same definition.

Meeting desk at the same published revision
├── Finance workspace
│ ├── calendar: Finance account
│ └── output: Finance meeting list
└── Operations workspace
├── calendar: Operations account
└── output: Operations meeting list

The logical calendar requirement is identical in both installations. Each team sees the data permitted by its own grants and the acting member’s account.

Review the pinned persona and linked definitions. Set up required connectors, model capabilities, output targets, and reviewers before running a team goal. Treat a package requiring missing compute or unbound connectors as setup work.

Compare the accepted source revision and the workspace’s current definitions. Verify new pins, preserve workspace-owned history and compatible bindings, and review changed requirements before execution. For Studio package updates, the preview identifies any local edits or permission changes that need review.

See personas and workspaces and what lives outside the persona folder.