> For the complete documentation index, see [llms.txt](https://help.roolz.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.roolz.net/en/switching-company-spaces.md).

# Switching company spaces

### If you have multiple companies and don't know how to switch between them:

{% tabs %}
{% tab title="PC version" %}

* In the upper right corner, next to your profile picture, you will see your active space (a colored circle with 2 letters if you don't have photo).
* If you see "Create company", you are in your personal space and are not a member of any company. You can create a company and invite your colleagues to join you for more productive work.
* If you are a member of the company, click on the down arrow icon. When the list of your spaces expands, click on the company, which space you want to enter.
* In addition to company spaces, there is also a personal space where the user acts as an individual. To act as an individual, select "Personal space".

<div align="left"><figure><img src="https://2469999162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4Tidb9efyw3qYBxHOhk%2Fuploads%2FiZ0CTqktcjVJw9Al3Gdx%2FChange_company3_comp.png?alt=media&amp;token=5d7ce377-eca3-4b70-a638-0fe9cb114bbb" alt="" width="375"><figcaption></figcaption></figure></div>
{% endtab %}

{% tab title="Mobile version" %}

* Click on the menu button in the top left corner. At the top of the page, your active workspace will be displayed. If you see "Create company" button, you are in your personal space and are not in the company. You can create a company and invite people to join you to be more productive.

<div align="left"><figure><img src="https://2469999162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4Tidb9efyw3qYBxHOhk%2Fuploads%2FPm20Af0k90e5P53u94aW%2FChange_comp1_phone.png?alt=media&amp;token=f67ac9e6-0260-46e8-8b48-faee6da86e05" alt="" width="375"><figcaption></figcaption></figure></div>

* If you are a company member, click on the down arrow icon.

<div align="left"><figure><img src="https://2469999162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4Tidb9efyw3qYBxHOhk%2Fuploads%2FfvMjVwVa8oMTGPriOsIU%2FChange_comp2_phone.png?alt=media&amp;token=d8798bae-b7d0-4ffb-9e1a-ae9f6a865e2a" alt="" width="375"><figcaption></figcaption></figure></div>

* When the list of your spaces expands, click on the company, which space you want to enter.

<div align="left"><figure><img src="https://2469999162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4Tidb9efyw3qYBxHOhk%2Fuploads%2FJZqyBzmGjsDM9EwXcAO9%2FChange_comp3_phone.png?alt=media&amp;token=c6af3712-30d7-4680-88e1-90b1c7f632ae" alt="" width="375"><figcaption></figcaption></figure></div>
{% endtab %}
{% endtabs %}


---

# 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.roolz.net/en/switching-company-spaces.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.
