# Create a client workspace

> Set up a Maven workspace for each client, with its own sources, reports, portal access and tracking, then add the context Maven uses when it builds reports.

Source: https://mavendata.ai/docs/getting-started

In Maven, every client gets their own **workspace**. A workspace holds that client's connected sources, reports, budgets and tracking, and it decides which of your team and which client users can see them. Each workspace is kept separate from every other client. Create one workspace per client, then connect their sources.

Only account admins can create workspaces.

## Create the workspace

1. Open the **New Workspace** page. If your account has no workspaces yet, Maven opens it for you when you sign in. You can also choose **Create a workspace** on the welcome checklist, or search for **Add New Workspace** in the command palette.
2. Enter a **Workspace Name**. This is the client-facing name, shown in the app, in reports and on the client portal.
3. Optionally enter the client's **Website**, for example `https://acme.com`.
4. Select **Create Workspace**.

If adding the workspace changes your subscription, the button shows the price instead, and Maven asks you to confirm before it creates the workspace. See [Plans and pricing](https://mavendata.ai/docs/account/plans).

When the workspace is created, Maven opens **Reports** for it. To switch between clients, use the workspace selector in the sidebar (**Search workspaces...**).

## Check the workspace settings

Open the user menu at the bottom of the sidebar and choose **Settings**. With a workspace selected, **Workspace** settings come first.

| Section | What it's for |
|---|---|
| **Workspace profile** | The workspace name and website. Select **Save changes** after editing. |
| **Default currency** | The currency used for labels and defaults. Reported spend always keeps each ad account's own currency. Enter a code such as `USD` and select **Save currency**, or select **Use automatic** to let Maven detect it. |
| **Agent context** | What Maven knows about this client. Maven uses it when it builds reports and answers questions. |

## Tell Maven about the client

Maven builds most of a workspace's context from connected data and conversations. You can add to it directly:

1. In **Agent context**, find **Tell the agent anything**.
2. Write the client's goals, definitions, caveats or preferences, for example "Leads means qualified form fills, not newsletter sign-ups". Maven keeps your words exactly.
3. Select **Save context**.

If Maven has open questions about the client, they appear under **A few things to clarify**. Short answers help it fill gaps it can't infer from the data.

Under **What the agent knows**, you'll see structured facts such as **Business type**, **Industry**, **Priority KPIs**, **Cadence**, **Primary platforms** and **Fiscal year starts**. These are read-only. Maven maintains them from your data and conversations, so correct them by telling the agent.

```prompt
Remember for the Acme workspace that "leads" means qualified form fills, not newsletter sign-ups.
```

## What happens next

1. [Connect the client's sources](https://mavendata.ai/docs/getting-started/connect-sources).
2. [Set budgets and alerts](https://mavendata.ai/docs/getting-started/targets-and-alerts).
3. [Set up the client portal](https://mavendata.ai/docs/client-portal) and invite the client.
4. [Connect your AI tools](https://mavendata.ai/docs/mcp/connect) to build reports for the workspace.

## FAQ

**Can one workspace cover several brands?** A workspace is one client. If you report on brands separately, give each its own workspace.

**Who on my team can see a workspace?** Admins have full access to the account. Other team members and client users need access to at least one workspace, which you choose when you invite them. See [Client logins and sharing](https://mavendata.ai/docs/client-portal/sharing-and-access).
