> 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/manage-private-feed-access/understand-private-feed-protection-and-listener-access.md).

# Understand private feed protection and listener access

Understand how protected podcasts, listener records, and credential-bearing feed URLs work.

Feed protection controls whether a podcast requires listener-specific access. Listener records control who can use that protected feed.

## Protection and listeners

* A protected podcast requires a plan that includes protected podcasts.
* A listener belongs to one podcast and has an email or username.
* Listener status can be pending, active, inactive, or resent.
* An optional expiry time can end access automatically.
* Deactivation is the reversible way to stop one listener's access.
* Deletion removes the listener record permanently.

## Feed URLs

The podcast's normal feed URL identifies the show. A listener's private feed URL adds an access credential. Treat the complete private URL like a password.

The public MCP listener record deliberately does not return access tokens or private feed URLs. Use Podigee's invitation and listener-facing access flow to deliver access without exposing the secret in a conversation.

## Public-feed effect

Enabling protection changes access to the podcast feed. Disabling protection makes the normal feed available without listener credentials. Review the listener effect before either change.

## Related tasks

* [Enable or disable feed protection](/documentation/start-here/ai-agents/manage-private-feed-access/enable-or-disable-feed-protection.md)
* [Add a private-feed listener](/documentation/start-here/ai-agents/manage-private-feed-access/add-a-private-feed-listener.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/manage-private-feed-access/understand-private-feed-protection-and-listener-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.