> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/platform/platform-services/partner-management/disabling-a-partner.md).

# Disabling and Enabling a Partner

Step by step in the Partner Management staff portal: disable a partner so that every service refuses it, re-enable it, and what happens in between.

How a partner manager stops a partner from using any service, and lets it back in, in the Partner Management staff portal (`https://partner-management.<base domain>`, role `partner_manager`). The partner statuses: [Partner status](https://docs.openg2p.org/platform/platform-services/partner-management/functional-specifications.md#partner-status).

## Disable

1. **Partners**, open the partner.
2. Click **Disable**.

The partner's status becomes `disabled`. Nothing is deleted: its keys, policies and history stay, and the change is recorded in its **History** (`partner.disabled`). It stays in the **Partners** list, marked disabled: Partner Management never deletes a partner, so that its history and the decisions made with it can still be traced.

## What happens

Partner Management stops serving the partner's keys and policies: its key and policy APIs answer "not found", exactly as for an unknown partner. Every service that relies on them then refuses the partner:

* its signed requests no longer verify;
* every policy check fails, so no consent is accepted and no data is released for it.

Services cache keys and policies, so the refusal applies once their caches expire: within about a minute for policies and five minutes for keys, or up to the hard TTL (six hours by default) while Partner Management itself is unreachable ([Integration](https://docs.openg2p.org/platform/platform-services/partner-management/integration.md#6-consuming-access-policies)).

To stop one use case or one registry only, revoke that policy instead ([Creating and Changing Policies](https://docs.openg2p.org/platform/platform-services/partner-management/creating-and-changing-policies.md#an-existing-partner-add-edit-or-revoke)).

## Enable again

1. **Partners**, open the partner.
2. Click **Enable**.

The partner is `active` again with the keys and policies it had; services accept it once their caches refresh. Recorded as `partner.enabled`.

## By API

`POST /partners/{partner_id}/disable` and `POST /partners/{partner_id}/enable` on the staff API (a token with the `partner_manager` role): [API Reference](https://docs.openg2p.org/platform/platform-services/partner-management/api-reference.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/platform/platform-services/partner-management/disabling-a-partner.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.
