> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/secure-and-govern-agent-access/hand-over-or-remove-an-agent-connection-safely.md).

# Hand over or remove an agent connection safely

Transfer operational ownership or remove a Podigee agent connection without losing work context.

Inventory active work before you revoke the current connection.

## Before you start

* Identify the current client, user, selected account, scopes, and credential owner.
* List active operation IDs and their target resources.
* Identify the person or team that will own the replacement connection.

## Hand over the connection

1. Record non-secret operation IDs, idempotency keys, target IDs, and current states.
2. Let the new owner create a separate connection to the same Podigee account.
3. Grant only the scopes required for the continuing work.
4. Verify the new connected identity and tenant.
5. Finish, cancel, or hand back active operations before the handover when the new owner is a different Podigee user. An operation stays bound to the Podigee user, account, and tenant that started it, and another user cannot inspect or resume it.
6. When the same Podigee user reconnects, inspect existing operations under the new authorization and obtain a fresh preview before any resume or consequential action.
7. Verify that the new owner can complete the intended workflow.
8. Revoke the old connector access or remove the old personal access token.
9. Confirm that the old client can no longer access Podigee.

Do not transfer passwords, bearer tokens, refresh tokens, private feed URLs, or signed upload URLs.

## Remove without replacement

1. Inspect active operations and cancel eligible work when required.
2. Preserve audit-safe identifiers for Support or compliance needs.
3. Revoke the grant or token in Podigee settings.
4. Remove local pdg credentials or client configuration.
5. Verify revocation from the old client.

## Expected result

The intended work has a clear owner, the replacement authority is verified when needed, and the old credential is unusable.

## If an operation needs recovery later

Reconnect the same user and account with the required scopes. Inspect the existing operation and use a fresh resume preview. Do not repeat the original request as new work.

## Next step

[Review and revoke connected clients](/documentation/start-here/ai-agents/connect-and-authorize/review-and-revoke-connected-clients.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/secure-and-govern-agent-access/hand-over-or-remove-an-agent-connection-safely.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.