> 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/help-center/ai-agents/podigee-connected-to-the-wrong-account.md).

# Podigee connected to the wrong account

Revoke a connection and authorize it for the intended Podigee account.

One connector grant or MCP personal access token belongs to one Podigee account. Revoke the wrong grant, then create a separate grant for the intended account.

## Check the connected account

Ask the client to run `get_me`. If you use `pdg`, run:

```sh
pdg me --json
```

Compare the returned account identity with the account that owns the target podcast.

## Reconnect safely

1. Open **My account** in Podigee.
2. Select **API**.
3. Find the wrong client and account under **Connector access**, or the token under **Personal access tokens**.
4. Select **Revoke** for the connector, or **Remove** for the token.
5. Remove the connection from the AI client if it still appears there.
6. Start a new connection.
7. If Podigee shows more than one account, select the intended Podigee account during authorization.
8. Run `get_me` again before any write operation.

Revoking a grant or removing a token stops that credential. It does not delete podcasts or episodes.

## Expected result

The new connection returns the intended account. Podcast searches show only resources available to that account and user.

## If the intended account is missing

Confirm that your Podigee user has access to the account. Ask an account administrator to add the required access before you reconnect.


---

# 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/help-center/ai-agents/podigee-connected-to-the-wrong-account.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.