> 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/modules-and-features/settings/buyers/enable-or-disable-buyers.md).
# Enable or disable buyers
Manage your existing buyers.
If you no longer wish to use a buyer, you can temporarily disable them and re-enable them when required.
When you disable a buyer, the licensees associated with that buyer also become unavailable. This means you'll no longer be able to select those licensees when creating a new agreement.
### Enable or disable a buyer
To enable or disable a buyer:
1. Go to **Settings** > **Buyers**.
2. Find the buyer you want to manage.
Use the Buyers page to manage buyers.
3. Select the actions icon (**•••**) for the buyer and choose **Enable** or **Disable**. Note that only one of these options is shown depending on the current state of the buyer. For example, the **Enable** option is shown only if the buyer has been disabled.
4. In the confirmation dialog, confirm the action.
A message is displayed stating that the buyer was updated. You can view the updated buyer status on the **Buyers** page.
---
# 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/modules-and-features/settings/buyers/enable-or-disable-buyers.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.
