> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/account-setup-and-administration/creating-workspaces.md). # Creating Workspaces Workspace is where you create and manage your document templates, deliveries, eSignatures and team members. Each workspace operates independently, allowing teams to work autonomously within the same organization. For example, you can create a workspace for different departments like *HR*, *Marketing*, and *Support*. ## **Create Your Workspace**: * From the left-side menu, go to the **Home** page. * Click **Create Workspace**, provide a Workspace Name, and click on **Create Worksapce** to create it.

* To create more workspaces, return to the **Home** page, and repeat above steps. ## **Accessing your workspace** All workspaces in your organization can be viewed from the **Home** page. To access a workspace, select the desired workspace. ## **Managing a Workspace** Inside your workspace navigate to **Settings > Workspace**

For more details on configuration and customization, refer to the [**Workspace Settings**](/settings/workspace.md) help page. --- # 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://help.docupilot.app/account-setup-and-administration/creating-workspaces.md?ask=&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.