> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-licensing-guide/v19/manage-accounts/switching-between-accounts.md).
# Switching between accounts
When you log in to Parallels My Account, you use your personal credentials. Once logged in, you can switch to your organization's accounts by clicking the drop-down menu in the upper left hand corner and choosing an account.
When you select an account, the **Dashboard** is automatically populated with Parallels product(s) registered with the account.
When you select a business account, the **Business Profile** item is added to the navigation area of the page.
Clicking the **Business Profile** item opens the page where you can view and manage your organization's business account.
Clicking on the  icon in the page header opens a menu where you can view and select the following items:
* Your name and email address.
* **Personal Profile**. Opens a page where you can view and modify your personal information.
* **Security Settings**. Opens a page where you can view your account security settings.
* **Logout**. Logs you out of Parallels My Account.
---
# 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.parallels.com/landing/ras-licensing-guide/v19/manage-accounts/switching-between-accounts.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.
