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

# Workspaces

Create and manage workspaces, copy content between them

Workspaces are shared environments for teams or projects. Each account can have multiple workspaces. For sharing content across all workspaces, see the [Account Library](https://helpdesk.smaply.app/account-and-team/how-to-use-the-account-library.md).

#### Why use workspaces

* Give each team or project its own environment for journey maps, personas, and templates
* Keep work separated by context while reusing assets through copy or the Account Library

#### In this section

* [**Create a workspace**](https://helpdesk.smaply.app/account-and-team/workspaces/how-to-create-a-workspace.md) - Create additional workspaces within an account.
* [**Manage workspaces**](https://helpdesk.smaply.app/account-and-team/workspaces/how-to-manage-workspaces.md) - Rename and delete workspaces.
* [**Copy assets across workspaces**](https://helpdesk.smaply.app/account-and-team/workspaces/how-to-copy-assets-across-workspaces.md) - Copy journey maps and templates to another workspace, and share personas through the Account Library.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdesk.smaply.app/account-and-team/workspaces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
