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

# Workspaces overview

> Workspaces (organizations) own agents, conversations, and members.

A **workspace** (called an *organization* in the database) is the multi-tenant boundary in Zeptar. Every agent, conversation, member, and invitation belongs to exactly one workspace.

## Active workspace

Each session has an **active workspace** — set by the web UI's workspace switcher. Endpoints that don't take an explicit `orgId` in the path read the active workspace from the session.

Endpoints that take `orgId` in the path:

* `POST /v1/organizations/{orgId}/members`
* `DELETE /v1/organizations/{orgId}/members/{memberId}`

…use the path parameter as the authoritative scope. The active-workspace fallback does not apply.

## Membership gate

`GET /v1/organizations/by-slug/{slug}` returns `404 organization_not_found` if the requester is not a member of the workspace, even if the slug exists. This prevents slug enumeration.

## Roles

Three roles are supported:

| Role     | Can edit agents | Can manage members | Can delete workspace |
| -------- | --------------- | ------------------ | -------------------- |
| `member` | ✓               | ✗                  | ✗                    |
| `admin`  | ✓               | ✓                  | ✗                    |
| `owner`  | ✓               | ✓                  | ✓                    |

`DELETE /v1/organizations/{orgId}/members/{memberId}` requires `member.delete` permission, granted to both `admin` and `owner`.

## Related guides

* [Workspace invitations](/api-reference/workspace-invitations/overview) — pending invites for the current user.
* [Me](/api-reference/me/overview) — read the active workspace id.