# Workspaces and members

Create workspaces, switch between them, invite members and choose what each person can do.

## Workspaces

A workspace holds envelopes, templates, folders, settings and members. Everyone in a workspace sees its envelopes. Your account starts with one workspace when you sign up.

### Create and switch

Open the workspace menu at the top of the sidebar. Select a workspace to switch to it, or select **Create workspace**, enter a **Workspace name** and select **Create workspace**.

Free and Starter include one workspace, so **Create workspace** only appears on Pro and Platform. See [Plans and billing](/docs/plans-and-billing).

Every workspace you own uses your plan, and its envelopes count toward your allowances. If you move to a plan with fewer workspaces, your oldest workspaces stay active and the others become read-only until you upgrade.

### Rename

Owners and admins can change the name in **Settings → General**.

## Members

**Settings → Members** lists everyone in the workspace and the plan's member limit.

The workspace's [Sandbox](/docs/sandbox) has the same members and roles. Invite, change and remove members in the live workspace.

### Invite a member

1. Open **Settings → Members**, or select **Invite** in the workspace menu.
2. Under **Invite member**, enter an **Email address** and choose a **Role**.
3. Select **Send invitation**.

The person gets an email with a link. They sign in or create an account with the invited email address, then select **Accept invitation**. Invitations expire after 7 days.

Pending invitations are listed under **Pending invitations**, where you can **Cancel** them. Pending invitations count toward the member limit.

### Member limits

| Plan | Members per workspace |
| --- | --- |
| Free | 1 (just you) |
| Solo | 1 (just you) |
| Starter | 3 |
| Pro | 10 |
| Platform | Unlimited |

The owner counts as a member. If you downgrade, existing members keep access, but you can't invite anyone until you're under the new limit.

### Change a role or remove a member

Owners and admins can pick a new role from the member's row or select **Remove**. A removed member loses access to the workspace right away. Their account isn't deleted.

## Roles

| Role | What they can do |
| --- | --- |
| Owner | Everything an admin can. The workspace uses the owner's plan. The owner can transfer ownership. Each workspace has one owner. |
| Admin | Send and manage envelopes and templates. Manage members, workspace settings, branding, notifications and the Developers area. |
| Member | Send and manage envelopes, templates and folders. View the member list and data settings. |
| Developer | Manage API keys, webhooks, events and logs in the Developers area. Can't open envelopes, documents or templates. |

Everyone can [connect an AI assistant](/docs/mcp#connect-your-ai-assistant) and create personal API keys, which act with their own role. A developer can only create workspace keys with key and webhook abilities; owners and admins with any ability. See [API quick start](/docs/api-authentication).

## Transfer ownership

The owner can hand the workspace to another member in **Settings → General → Danger zone**. Select **Transfer ownership**, choose the **New owner** and confirm.

- The new owner must already be a member with a verified email address.
- You become an admin.
- Envelopes and their history stay in the workspace.
- From then on, usage and limits follow the new owner's plan. Subscriptions don't move. If the new owner's plan has no room for another workspace, the workspace becomes read-only.

## Data and retention

**Settings → Data & retention** holds these settings. Owners and admins can change them; other members can view them.

- **Envelope Retention:** how long inactive drafts are kept, and whether completed envelopes are kept indefinitely (the default) or for a set number of years. Permanent deletion of expired completed envelopes is off until you turn it on.
- **Workspace data export:** request a ZIP of original and completed PDFs, signing evidence and templates.

### Export workspace data

Select **Request export ZIP**. You can leave the page while the ZIP is prepared; the owner and admins get an email when an export is requested. When it's ready, download it: a large workspace comes in parts of about 128 MiB, so select **Download part 1 of …** and each part after it. Each link works once.

- Up to 3 export requests per workspace a day, one at a time.
- The download link works once and expires after 15 minutes.
- If a request or download fails with "unavailable", export storage isn't set up, the ZIP can't be found, or the workspace has no verified owner or admin to notify. Retrying won't help: make sure an owner or admin has a verified email, then contact support. A failed download doesn't use up the link.

Store the ZIP securely. It contains every signed document in the workspace.

API keys with the `workspaces:export` ability can request exports too. See the [API reference](/docs/api).

## Delete a workspace or account

There's no option to delete a workspace in the app. Contact support if you need one removed.

To delete your account, see [Sign-in and security](/docs/account-security#delete-your-account). Workspaces you own that have other members must be transferred first.

## Settings through the API and MCP

`GET /api/v1/workspace` returns the key's own workspace: its `name`, its `settings` and its `notification_policy`. `settings` is the same object a platform reads on `GET /api/v1/workspaces/{workspace}`: `default_signing_window_days` (null for the 60-day default) and the resulting `signing_window_days`, the default `reminders`, `delivery_problems_enabled`, `require_esign_consent` (whether signers must agree to the [signing disclosure](/docs/envelopes#signing-disclosure)), the disclosure wording and the embedding origins.

`PATCH /api/v1/workspace` changes `settings.default_signing_window_days`, `settings.reminders`, `settings.delivery_problems_enabled`, `settings.require_esign_consent` and `notification_policy`. Only the fields you send change, and inside `reminders` and `notification_policy` only the keys you send (`null` clears a notification kind). Envelopes already sent keep their own settings. The disclosure wording has its own [endpoints](/docs/envelopes#signing-disclosure), and the embedding origins are set by the platform.

```json
{ "settings": { "default_signing_window_days": 14, "require_esign_consent": true } }
```

- Reading needs the `envelopes:read` ability, changing `envelopes:write`. A test key reads and changes the sandbox's own defaults. A platform key sends `Workspace-Id`.
- Changing `reminders` needs a plan with automatic reminders.
- `GET /api/v1/workspace/members` lists everyone in the workspace with their name, email and role. Inviting and changing roles stay in the app. A platform can remove people its login links added with `DELETE /api/v1/workspaces/{workspace}/members/{external_id}` (see [Platform sign-in](/docs/platform-sign-in#remove-a-person)).

AI agents use the MCP tools `get_workspace_settings`, `update_workspace_settings` (it asks the user to confirm first) and `list_workspace_members`.

## Other workspace settings

| Setting | Where it's covered |
| --- | --- |
| **Signing & reminders** | [Send and track](/docs/sending-for-signature) |
| **Signing disclosure** | The electronic signature disclosure signers see, and whether they must agree before signing |
| **Notifications** | [Notifications](/docs/notifications) |
| **Branding** | [Branding](/docs/branding) |
| **Embedding** | [Embedded signing](/docs/embed-integration) |
