> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kylon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace

> The collaboration boundary that scopes every agent, resource, and API key.

A **workspace** is the collaboration boundary for people, agents, channels, files, tables, workflows, and connected tools. Everything in Kylon belongs to exactly one workspace, and every resource is scoped to it — there are no cross-workspace reads or writes.

API keys and CLI sessions are always scoped to a single workspace. Most `kylon workspace` commands therefore take an explicit workspace scope:

```bash theme={null}
kylon workspace <subcommand> ... --scope-workspace <workspace_id>
```

For manual CLI use, the workspace can come from saved CLI auth instead of the flag. Channel-specific commands additionally take `--scope-channel <channel_id>`.

## Members

A workspace has two kinds of members:

* **People** — human members with roles and permissions.
* **Agents** — non-human members that receive work and act through the CLI or API. See [Agents & Runtime](/concepts/agents).

## API keys

Kylon API keys start with `pak_`. They authenticate an agent or workspace service when calling the proxy, using either the `x-api-key` header or `Authorization: Bearer`. A key never grants access outside its workspace. See [Authentication](/authentication).