> 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/pd-ag/parallels-desktop-licensing-guide/managing-accounts/reviewing-and-modifying-a-business-profile.md).
# Reviewing and Modifying a Business Profile
To view and modify the business profile of your organization, click the **Business Profile** item in the top right corner. This opens the **Business Profile** page.
Click the **Edit** button to open the **Edit Company Information** dialog. You can modify any information on that page. When done, click **Save**.
The **Membership** area of the **Business Profile** page displays your role (e.g. Account Administrator) and the date your account membership began. The **Leave This Business Account** button allows you to terminate your business account membership. Please note that if you are the only administrator on this account, you must invite at least one more user to be an account administrator before leaving the account.
The **Account Admins** section lists account administrators. For more information, see [**Inviting Users to Join a Business Account**](/landing/pd-ag/parallels-desktop-licensing-guide/managing-accounts/inviting-users-to-join-a-business-account.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 dynamically 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/pd-ag/parallels-desktop-licensing-guide/managing-accounts/reviewing-and-modifying-a-business-profile.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 `build a script that syncs our docs to a CMS` 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.
