> 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/a-private-feed-listener-cannot-get-access.md).

# A private-feed listener cannot get access

Check feed protection, listener state, expiry, invitation, and password reset safely.

Check feed protection and the listener record before you resend access or create another listener.

## Check the listener

1. Confirm that feed protection is enabled for the podcast.
2. List listeners for the correct podcast.
3. Find the listener by the intended email address.
4. Check the listener `status` (`pending`, `active`, `inactive`, or `resent`) and its `expires_at` date.
5. Confirm that the email address is correct.
6. Activate the listener when the record is valid but inactive.
7. Send a password reset when the listener cannot authenticate.

Preview every listener change. Show the affected email address and action before confirmation. Prefer deactivation when the access removal might need to be reversed.

## Private URL boundary

MCP listener tools do not return the private feed URL or access token. Do not construct one from IDs. Do not paste a private URL into chat. Use Podigee's protected invitation and reset flow.

## Expected result

The active, unexpired listener receives the applicable Podigee message and can authenticate to the protected feed.

## If access still fails

Send Podigee Support the podcast and listener IDs, listener state, expiry, message time, and sanitized error. Do not send the listener password, private feed URL, or token.


---

# 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/a-private-feed-listener-cannot-get-access.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.