# Revoking Sessions Safely

Revocation is the primary control for retiring unused or high-risk sessions. The steps below explain the available pathways and safeguards.

## Revoke an individual session

1. Expand the session card (optional) to review scope and limits.
2. Select **Revoke session**.
3. Confirm the action in the prompt presented by PENGUARDS.
4. Approve the transaction within Abstract Global Wallet.
5. Monitor the status banner as it progresses from:
6. Awaiting wallet
7. Broadcasting
8. Confirmed The session is removed once the validator reports it closed.

If the transaction is cancelled inside AGW, the dashboard remains unchanged and the session stays available for future action.

![Per-session revoke confirmation](/files/DNTWTFKKZsr42lUCR5ew)

## Revoke multiple sessions at once

* Select **Revoke all** on the toolbar when a full reset is required.
* The extension queues each active session and processes them sequentially within the same task window.
* Progress counters (for example, "2 / 5 sessions revoked") provide continuous visibility.

![Bulk revoke workflow](/files/t7KgXad1B8cIusG9M2EM)

## About the revoke task window

* Opens automatically and remains visible while any revocation is pending.
* Persists even if browser focus shifts to another tab or to the wallet modal.
* Offers retry and close controls when a transaction fails or is cancelled.
* Closes itself once all queued revocations have completed—successfully or otherwise.

## Notifications & error recovery

* Toast notifications summarise each outcome (for example, "3 sessions revoked" or "Revoke failed: user rejected").
* If the wallet declines the transaction, the session remains on the dashboard and the revoke control resets for a future attempt.
* In rare instances where Chrome blocks creation of the task window, PENGUARDS reverts to an inline flow so the revocation can still be completed.

> Revocation is permanent. Re-establishing access requires returning to the originating application and issuing a new session key.


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://penguards.zer0luck.kr/revoking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.