> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/getting-started/switch-projects.md).

# Switch projects and companies

Move between the companies and projects you're on with the company and project boxes in the header, or in the menu on a phone.

Use the project menu to move between the companies and productions you're on; anyone can switch. On a computer, it's the company and project boxes in the header, to the right of **Search pages…**; on a phone, it's the **Company** and **Project** fields near the top of the menu.

The lists show only the companies and projects you've been added to. To join another project, ask someone who manages its team to add you on **Project > Team** (see [Manage your team](/project/team.md)).

## Switch project

1. Select the project box in the header, which shows the name of the project you're on. On a phone, select the menu button (three lines) in the header, then select the **Project** field.
2. Select a project, or type part of its name and select it from the results.

The project you're on is listed first, then your other projects, newest first. A long list shows the first 50 entries; select **...and&#x20;*****N*****&#x20;more** at the bottom to see the rest.

## Show wrapped projects

Wrapped projects are hidden from the list at first.

1. Open the project list.
2. Select **Show wrapped projects** at the bottom of the list. It appears only when one of your other projects is wrapped.

Wrapped projects then appear after the others, in grey italics with **(wrapped)** after the name. They're hidden again the next time you open the list.

When you type to search, matching wrapped projects appear without selecting **Show wrapped projects**, after the projects that aren't wrapped.

## Switch company

1. Select the company box in the header, which shows your company's name. On a phone, open the menu and select the **Company** field.
2. Select a company, or type part of its name and select it from the results.

RollCredits opens the newest project you're on in that company.

Your companies are listed newest first. On a browser where you haven't chosen a company yet, RollCredits opens the newest one.

## What happens when you switch

* You stay on the same page, now showing the project you chose.
* Any transaction you had open closes.
* RollCredits remembers your choice on that browser and opens it again next time.
* If you open a link to a transaction or timecard on another project, such as one in an email, RollCredits switches company and project for you.

{% hint style="info" %}
While you're setting up a new company, the setup page also has a company box in its header if you already have another company that's set up. See [Set up your account and company](/getting-started/set-up-your-account.md).
{% endhint %}

## Add a new project

Owners, and Super Admins on the project you're on, also see **Add new project** at the top of the project list. Selecting it opens the **Add Project** page. For the steps, see [Add a project](/getting-started/add-project.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://knowledge.rollcredits.io/getting-started/switch-projects.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.
