> 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/guides-and-tutorials/marketplace-for-partners/how-to-verify-if-your-account-has-partner-capabilities.md).

# How to verify if your account has partner capabilities

Verify if your Marketplace account is enabled for partner use.

There are three ways to verify whether your account is configured as a partner account in the Marketplace Platform.&#x20;

You can check this through the following pages, available under **Settings** in the main navigation menu:

1. **Accounts** – The [Accounts](/modules-and-features/settings/account.md) page displays general information about your account. If you are set up as a SoftwareOne partner, you'll see a field labeled **Partner program** with the value **Yes** in the **Additional Data** section on the **General** tab. This field does not appear for client accounts.
2. **Buyers** – The [Buyers ](/modules-and-features/settings/buyers.md)page lists all entities or organizations that have been configured for your Marketplace account. For partner accounts, this page displays all organizations that receive invoices from SoftwareOne.
3. **Licensees** – On the [Licensees](/modules-and-features/settings/licensees.md) page, partners can view their own organizations as well as third-party organizations. The **Resale** column indicates whether a licensee is procuring for self-consumption or reselling. If the value in the **Resale** column is **Yes**, it means the licensee is ordering products and services for resale purposes.


---

# 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/guides-and-tutorials/marketplace-for-partners/how-to-verify-if-your-account-has-partner-capabilities.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.
