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

# Workspaces and members

> A workspace holds everything. A connection works in one workspace, and the owner holds its settings.

A workspace is the unit everything belongs to: its library, timelines, canvases, feed, comments, brand kit, skills, boards, calendars, public links and webhooks. An account has one or more workspaces. A workspace has an owner and members.

## Roles

| Role   | Can                                                                                                                           |
| ------ | ----------------------------------------------------------------------------------------------------------------------------- |
| Owner  | everything, including workspace settings, webhooks and the API keys bound to the workspace. Storage counts against the owner. |
| Member | work in the workspace: library, timelines, canvases, generation, comments, skills.                                            |

`get_workspace_overview` returns the caller's role. `manage_settings` changes workspace settings and is refused for a member.

## One connection, one workspace

An OAuth connection is scoped to one workspace when the user makes it and stays there. An API key is bound to one workspace the account owns when it is created. Neither reaches the account's other workspaces through the tools. `get_workspace_overview` says which workspace the connection is in.

A caller that holds the whole account over REST, such as the CLI or a user's own script, lists every workspace it can reach with `GET /api/v1/workspaces` and names one for a single request with the `x-workspace-id` header. An API key ignores the header and works in its own workspace only.

## Members and balances

The overview lists members by name, and those names are what `manage_comments` accepts as mentions. Cloud processing minutes are always the caller's own, whoever owns the workspace. Storage is the owner's.

## Changes

The overview reports what each member has open in the app right now, and a changes cursor. `get_workspace_changes` with `after_cursor` returns only what happened since, oldest first: files added, generated and edited, timelines and canvases worked on, structure, links, skills and published clips, each with who did it.