Organizations and Workspaces

An organization is your company; a workspace is a team-sized scope inside it. Agents, assignments, sessions, and work surfaces live in workspaces; skills, integrations, guardrails, and governance can be set org-wide.

The two-level shape matters because it decides what is shared and what is governed. A workspace is the sharing boundary: its members see the same agents, boards, and data tables, and its agents reach the same connections. The organization is the governance boundary: it holds membership, org-wide skills and integrations, the guardrail floor every workspace inherits, usage reporting, and the audit log. A useful default is one workspace per team, because teams are what actually share systems and conventions:

Workspace	What typically lives there
Revenue	CRM connection, a pipeline-report agent, a lead-enrichment webhook assignment
Product	Competitor-tracker data table, release-notes assignments, analytics connections
People	Recruiting-pipeline tracker, a screening-notes agent, HR system connection

You can use Workprentice without an organization. Create one when you want teammates: “Organizations let you collaborate with your team on shared workspaces.” Nothing is lost by starting solo — the organization is the step you take when a second person needs to see the same work.

Organization settings

Organization settings cover General, Members, Workspaces, Organization Skills, Organization Integrations, Guardrails, Usage, and Audit Log.

Members and roles

Members are Admins or Members; the founding owner holds a protected role above both. Owners and admins manage invites, roles, member removal, and workspaces. A billing admin role grants usage visibility without management rights — the right fit for a finance partner who needs to see token spend but should not be able to change membership or settings.

Keep the admin set small. Most people only need to be members: they get the workspaces they belong to and everything shared inside them, while the handful of admins handle invites, workspace creation, and org-wide configuration.

Inviting your team

Two paths:

Email invites — comma-separated addresses, a role, and optionally extra workspaces beyond the default one. Pending invites can be revoked.
Domain auto-join — claim your company’s email domains so new users who sign up with a matching address are automatically added to the organization. Owners can additionally enable managed accounts, making the organization workspace the default landing experience.

Email invites suit the early days, when you are adding specific people and choosing their workspaces one by one. Domain auto-join is for the rollout moment: once the domain is claimed, anyone who signs up with a company address lands in the organization without an admin in the loop, so new hires stop arriving as orphaned solo accounts.

Workspaces

Owners and admins create workspaces (name plus a URL slug) and choose the default workspace new members join. Deleting a workspace permanently removes it and its members from it; the last workspace in an organization cannot be deleted.

Workspace settings

Workspace settings cover API Keys (webhook authentication — see API keys and webhooks), Guardrails, Usage, and a Danger Zone for deletion. Skills and integrations are managed in Customize, where the scope pills switch between workspace and organization.

The split is deliberate: settings that govern the workspace live in Settings, while the abilities agents work with — skills and connections — live in Customize, next to where you use them. The scope pills mean you are always one click from seeing what the workspace owns versus what it inherits from the organization.

Usage and the audit log

Usage reports input and output tokens, sessions, and cache hit rate — by model, by agent, and drillable from workspaces down to individual sessions, with CSV export. The Audit Log is a read-only record of administrative and agent activity across the organization, filterable by event type, actor, and time, and exportable to CSV or JSONL for compliance review.

These two surfaces answer the questions that arrive once agents do real work. Usage answers “where is the spend going?” — drill from the organization to a workspace to the one agent whose assignment is heavier than expected, then to the individual sessions behind the number. The audit log answers “who did what, and when?” — and because it is exportable, the answer can leave the product and enter your compliance process.

Patterns that work

Start solo, organize later — use Workprentice alone, then create the organization the day a teammate needs in. Your work comes with you.
One workspace per team — Revenue, Product, People. Teams share systems and conventions; workspaces are built to hold exactly that.
Shared things at org scope, team things at workspace scope — the company style skill and the company chat connection org-wide; the CRM in the workspace whose team owns it.
Set the guardrail floor once — restrictions at the organization apply everywhere and cannot be loosened below; workspaces and agents only tighten from there. See Guardrails.
Give finance the billing admin role — usage visibility for the people who watch spend, without handing them member management.