> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c150/c152/q439.md).

# How do I create, manage, and rename workspaces (spaces) in the app?

## Report and Run: Cloud and Integrate

In the cloud version of the app, you create a single space when you start your subscription. You can manage and customize your workspace in a few ways:

* change the [name](/manual/report-and-run-integrate/branding/set-a-company-name.md) and [logo](/manual/report-and-run-integrate/branding/set-a-company-logo.md) associated with your workspace
* use folders to [set up different logos](/manual/readme/branding/set-multiple-logos.md) and branding within your workspace
  * adjust [folder properties](/manual/report-and-run-integrate/content/folders/set-folder-properties.md) so reports show different names, logos, and contact details
  * [invite collaborators](/manual/report-and-run-integrate/collaboration/invite-a-user-into-a-folder.md) to edit or view only specific folders

## Report and Run: Offline

In the offline version of the app, you can [create multiple spaces](/manual/report-and-run/content/spaces/create-new-space.md) and edit the [name](/manual/report-and-run/branding/set-a-company-logo.md) and [logos](/manual/report-and-run/branding/set-multiple-logos.md) in each space. 

## Related

* [Article: How to create a Report and Run: Cloud account](/manual/readme/quick-start-guide/create-an-account.md)
* [Article: How to switch spaces in Report and Run: Offline](/manual/report-and-run/content/spaces/switch-spaces.md)
* [FAQ: How do I delete a workspace (space) on the mobile app?](/manual/faq/c150/c152/q443.md)
* [FAQ: How do I create separate workspaces with unique text templates?](/manual/faq/c150/c155/q493.md)


---

# 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://docs.reportandrun.com/manual/faq/c150/c152/q439.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.