A workspace groups workflows and the resources they use, including tables, files, knowledge bases, integrations, and secrets. Workspace roles control access, with additional permissions for resources such as credentials. Deployments and explicit sharing can expose selected resources outside the workspace.
What a workspace contains
The app labels a workspace a team space: the workspace switcher, the Team spaces rail entry, and the Team space settings group all refer to it. The left rail and the Team spaces tabs are the map of a workspace — see The workspace for a tour. Each area holds one kind of resource:
Relays
A Relay is an AI coworker that works on tasks for the person who delegated them, inside the limits you set. See Relays.
Workflows
A workflow is a saved, repeatable procedure made of blocks: the primary resource in a workspace. You edit it, deploy it to surfaces like an API or a chat, and version it. See Workflows for the full model.
Tables
A table is structured data in the workspace, used as a source or an output inside workflows.
Library
The Library holds the workspace's files: documents and binaries readable by workflows, Chat, and Relays, organized into folders. See Library.
Data sources, dashboards, and governed data
Data sources connect warehouses, databases, apps, and spreadsheets. Dashboards turn that data into charts and reports, and metrics, the semantic model, rules, and monitors define and watch your numbers. Workbooks query data sources in SQL or plain English. See Data, Workbooks, and Dashboards.
Knowledge bases
A knowledge base is a collection of documents or structured data that workflows search to give a model context at run time.
Integrations
An integration is a connected account for a third-party service (Gmail, Slack, GitHub, and so on). Each carries its own access control, so a team shares one connection. See Integrations.
Secrets
A secret is an API key or environment variable stored securely in the workspace. Secrets come in two scopes: Workspace secrets are shared with the workspace, and Personal secrets are private to you. See Secrets.
Run history
Run history (the Logs page), linked at the top of the Workflows pane, lists every workflow run. A log is the execution trace of one workflow run: the trigger, the blocks that ran, and each block's input, output, and error. Logs are how you verify what happened.
Deployments are not a section of their own. A deployment is a versioned snapshot of one workflow, published for outside use through an API, chat, or MCP server. Editing a workflow does not change a live deployment until you promote the new version, and rollback means promoting an earlier one. See Deployments.
Access and isolation
Everything is scoped to the workspace, so access, settings, and isolation work the same way:
- Access. Workspace roles determine what members can do. Credential grants and permission groups can restrict particular resources or features.
- Settings. Each workspace has its own configuration: integrations, secrets, access control, API keys, and more. The Settings page lists the full menu.
- Ownership. Workflows, tables, files, and knowledge bases belong to a workspace. To edit a workflow in another workspace, move or copy it there; deployments and sharing determine how others can use it.
Members join with one of three permission levels: Read, Write, or Admin (the creator is Owner). Read can view, Write can build and run, Admin can also manage members and settings. See Roles and permissions for the full breakdown.
Personal and organization workspaces
Most workspaces are one of two kinds.
A personal workspace lives under your own account. Use it for experimentation and individual work. Your plan sets how many you can create. When you join an organization as an internal member, personal workspaces you own move into it — the accept screen names them before you accept.
An organization workspace (also called a shared workspace) lives under an organization, available on Team and Enterprise plans. You invite people to one or more workspaces at a time, each with a permission level, and choose whether they join as members or as external collaborators. Internal members join the organization, count toward its seat total, and bring their own workspaces with them. External members stay outside the organization — no seat, and everything they own stays theirs — that's how partners and clients get access, and it requires them to already be on a paid Agent Serve plan. For agencies and enterprises, this is the workspace you hand to the customer: the app they use, own, and maintain.
Plan limits, seat counts, and the internal-versus-external distinction live in Roles and permissions. This page covers what a workspace is, not how billing works.