> For the complete documentation index, see [llms.txt](https://docs.zama.org/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/protocol/sdk/api-references/react/userevokepermits.md).

# useRevokePermits

Revoke FHE permits for specific contract addresses, or all permits at once.

Revoke FHE permits for the current signer. With a contract list, removes direct-decrypt permits on the current chain. Without arguments, removes every permit across all chains and delegators. The transport key pair survives — use [`useClearCredentials`](/protocol/sdk/api-references/react/useclearcredentials.md) to also wipe the transport key pair.

## Import

```ts
import { useRevokePermits } from "@zama-fhe/react-sdk";
```

## Usage

{% tabs %}
{% tab title="RevokeButton.tsx" %}

```tsx
import { useRevokePermits } from "@zama-fhe/react-sdk";

function RevokeButton({ contracts }: { contracts: `0x${string}`[] }) {
  const { mutate: revokePermits, isPending, isSuccess } = useRevokePermits();

  return (
    <button onClick={() => revokePermits(contracts)} disabled={isPending}>
      {isPending ? "Revoking..." : "Revoke permits"}
    </button>
  );
}
```

{% endtab %}

{% tab title="RevokeAll.tsx" %}

```tsx
import { useRevokePermits } from "@zama-fhe/react-sdk";

function RevokeAllButton() {
  const { mutate: revokePermits, isPending } = useRevokePermits();

  return (
    <button onClick={() => revokePermits()} disabled={isPending}>
      {isPending ? "Revoking all..." : "Revoke all permits"}
    </button>
  );
}
```

{% endtab %}
{% endtabs %}

## Parameters

`useRevokePermits` takes no constructor parameters.

## Mutation variables

### addresses

`Address[] | void`

Optional array of contract addresses. When provided, revokes permits on the current chain whose payload touches any listed address. When omitted, revokes all permits across all chains and delegators.

```ts
const { mutate: revokePermits } = useRevokePermits();

revokePermits(["0xContractA", "0xContractB"]); // current chain only
revokePermits(); // all permits, all chains
```

## Return Type

## Behavior

* Removes signed permits from the permission store.
* Auto-invalidates all [`useHasPermit`](/protocol/sdk/api-references/react/usehaspermit.md) queries on success.
* The transport key pair is not affected — only permits are removed.

## Related

* [`useClearCredentials`](/protocol/sdk/api-references/react/useclearcredentials.md) — wipe the transport key pair and all permits
* [`useGrantPermit`](/protocol/sdk/api-references/react/usegrantpermit.md) — sign permits for contracts
* [`useHasPermit`](/protocol/sdk/api-references/react/usehaspermit.md) — check whether stored permits cover contracts


---

# 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.zama.org/protocol/sdk/api-references/react/userevokepermits.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.