# Managing your connections

> The self-service portal to link, review, and revoke the credentials an agent uses on your behalf.

Source: https://openap.org/docs/managing-connections

When an agent acts on your behalf, you decide what it can reach. OAP gives you a self-service place to
 **link, review, and revoke** the accounts an agent uses as you — no admin ticket required.

## Linking, on demand

The first time a `userPassthrough` agent needs an account you haven't connected, the session **pauses** and
sends you a link to connect it — a focused page that asks for just that credential, walking you through the
provider's own OAuth consent or a token entry. Once it's linked (and verified), the session resumes
automatically. You're never asked for more than the agent actually needs.

## The connections portal

There's also a standing portal — reachable from the agent's App Home *"Manage connections"* button — that lists
every account you've linked and every one an agent has asked for. From there you can:

- **Link** a new credential through the same guided flow.
- **See** which agents use which of your accounts.
- **Revoke** any connection — which deletes the stored credential and the identity entry immediately.

> **Security: Revocation reaches running sessions**
>
> Revoking a connection isn't just a database delete: the change propagates to in-flight sessions within tens of
> milliseconds, so an agent mid-task loses access the moment you pull it — it can't keep using a credential you
> just revoked. See [ASI03 — Identity & Privilege Abuse](https://openap.org/docs/owasp-top10#asi03).

## Before it's stored, it's verified

When you link a credential, OAP checks it's actually live before saving it. If the token is rejected, you're
shown a warning and asked whether to store it anyway — a bad credential is never silently kept, so an agent
doesn't fail later on something that was wrong at setup.
