> For the complete documentation index, see [llms.txt](https://docs.mosofin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosofin.com/account/workspaces-and-organization.md).

# Workspaces and organization

A workspace represents one client or company. It separates the connected financial source, agents, skills, API tool policies, and audit trail from every other workspace.

## Switch workspaces

Open the workspace switcher at the top of the sidebar and choose a workspace. The active workspace is marked in the list. Always verify the selection before asking Claude a question or changing permissions.

## Create a workspace

Select **New workspace** from the switcher or **Account settings > All workspaces**. If the action is unavailable, review your plan in Billing or ask the account owner.

Use a naming convention that makes the client or entity unmistakable. Avoid placing confidential account numbers in the workspace name because names can appear in navigation and screenshots.

## All workspaces

The account-wide view lists every workspace you belong to. From there you can open a workspace or access its settings. An expired plan can temporarily disable workspace actions until the owner restores the subscription.

## Roles and ownership

Workspace roles determine which settings a person can manage. Billing and some governance actions are owner-only. If you can view a feature but cannot change it, confirm your role with the workspace owner.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mosofin.com/account/workspaces-and-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.