> 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/create-and-publish/publishing-and-distribution/set-up-spotify-open-access.md).

# Set up Spotify Open Access

Enter your Spotify Open Access partner ID and assign entitlements for a restricted podcast.

Use this task to connect a restricted podcast to the Spotify Open Access program. Spotify Open Access lets your paying members listen to member-only episodes in Spotify. Podigee adds your partner ID and the episode entitlements to the feed. Spotify checks the membership.

## Before you start

* You need the owner, admin, or editor role for the podcast, with permission to edit the podcast.
* Spotify Open Access is available on plans that include private podcasts (Scale and above), or an older plan that includes it.
* The podcast must be restricted to invited listeners. See [Restrict a podcast to invited listeners](/documentation/create-and-publish/publishing-and-distribution/restrict-a-podcast-to-invited-listeners.md).
* You need a partner ID from the Spotify Open Access program. Podigee does not issue it.

{% tabs %}
{% tab title="Classic view" %}

### Enter the partner details

1. Open the podcast and select the **Feeds** tab.
2. Open the section **Spotify Open Access**, titled **Setup Spotify's Open Access feature**.
3. Enter the partner ID in **Open Access Partner ID**.
4. While you test with the Spotify sandbox, enable **Enable Test Mode**. Disable it for live members.
5. Enter the entitlement names that your program uses in **Entitlements**.
6. Save the section.

### Assign entitlements to episodes

The section reminds you: **No Entitlements are assigned to the episodes by default. Make sure you assign them to the individual episodes manually.**

1. Open an episode and select the **Custom feeds** tab.
2. In the Spotify Open Access section, select the **Entitlements** for the episode. Podigee accepts only names from the podcast list.
3. Save the episode.

Repeat these steps for each member-only episode.

### Expected result

The feed contains the Spotify Open Access partner data and the entitlement of each assigned episode. Spotify shows the episodes to members that hold the entitlement.

### If you cannot complete the task

* The section is missing on the **Feeds** tab: the podcast is not restricted, or the plan of the podcast owner does not include Spotify Open Access.
* Podigee rejects an entitlement on the episode: add the entitlement to the podcast list first.
* You cannot change the podcast owner: Podigee blocks an owner change while Spotify Open Access is enabled.
  {% endtab %}

{% tab title="Podigee workspace" %}
The Podigee workspace does not include Spotify Open Access settings yet. Switch to the classic view to enter the partner ID and assign entitlements.
{% endtab %}
{% endtabs %}

## Next step

[Understand your RSS feed](/documentation/create-and-publish/publishing-and-distribution/understand-your-rss-feed.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/create-and-publish/publishing-and-distribution/set-up-spotify-open-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.