> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/marketplace-platform/getting-started/switch-account.md).

# Switch accounts

Switch between your accounts without signing out.

If you belong to multiple accounts, you can switch between them without signing out of the platform. 

### Switch accounts

To switch between your Marketplace accounts:

1. Sign in to your account.
2. Select your profile menu. 

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FbUIbR9Rw6RowXNULl0G2%2Fimage.png?alt=media&amp;token=feaad3c3-8b2c-4b41-a5cd-6381c89e3099" alt=""><figcaption><p>Switch between your accounts.</p></figcaption></figure></div>

3. If required, search for the account using its name or identifier.
   * If the account is added to your favorites, use the **Favorites** tab to access it.
   * If you accessed the account recently, use the **Recents** tab to open it again.
4. Select the account name.&#x20;

Your account is switched, and you can access the modules and settings linked to your profile.


---

# 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.platform.softwareone.com/marketplace-platform/getting-started/switch-account.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.