> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/memberships/types-of-memberships/hidden-memberships.md).
# Hidden Memberships
### Overview
A Hidden Membership does not appear in the App for Customers to purchase.
Changing a Membership from `Listed` to `Unlisted` is done on the Membership page of the Dashboard. Anyone with the Owner role can change a Membership from `Listed` or `Unlisted` and back again.
Clubs can use Hidden Memberships for a single organization, an employer, a partner group, or an invited founding group, so those rates never become visible to every Customer. Two approaches exist, and the right one depends on whether the Customers buy it themselves or an Admin assigns it.
### Option 1: Share a direct Membership link
By leveraging the Slug of the Membership, a Hidden Membership can be shared with any Customer through a direct link. For example:
`https://club_name.podplay.app/memberships/founding`
Sharing this link with a specific Customer or a group of Customers allows those Customers to
* Click the link
* Land on the Membership page of the App
* See the Hidden Membership
* Buy the Hidden Membership
The Membership stays invisible to every other Customer in the App.
{% hint style="warning" %}
**The link is the only access control.** Anyone holding the link can purchase. Share it through the organization or the invited list rather than a public channel.
{% endhint %}
#### Offering more than one price tier
PodPlay builds one Hidden Membership per price tier, and each tier gets its own link. A Club offering an Individual tier and a Couple tier receives two links, and the slug names the tier:
```
https://club_name.podplay.app/memberships/founding-individual
https://club_name.podplay.app/memberships/founding-premier
```
Send both tier names and both prices in the same request so the Memberships and the links are created together.
### Option 2: Assign the Membership to Profiles manually
Use this when the Club wants control over who receives the Membership rather than distributing a link.
1. Have the Customers create a Profile in the App, or create the Profiles manually in the Dashboard.
2. Assign the Hidden Membership to those specific Profiles. A Club Admin or PodPlay can do this.
This is the approach behind a Corporate Membership or another Group Membership, where an Admin assigns one Membership across several Profiles at once.
### Using a Hidden Membership as a founding offer
A Hidden Membership is the usual vehicle for a founding or invite-only offer sold before a Club opens. The Club sends the link to an invited list, and the Membership never appears to the general Customer base.
The offer combines with two other settings:
* Payment choice at checkout, where the Club can apply the 3% processing fee to card payments and leave ACH without it. See Paying for a Membership with a card or bank account.
* A term longer than one year, held by the presale end date. See Selling multi-year and prepaid Memberships.
For the wider presale process around the offer, see Running a Membership presale.
### Verify the offer before sharing the links
1. Open each link in a browser while signed out.
2. Confirm the Membership name, tier, and price are correct.
3. Confirm the payment methods the Club expects appear at the payment step.
4. Confirm the Membership does not appear in the App's Membership list for a Customer without the link.
### Common issues
* **A Customer says the Membership is not in the App:** That is expected. A Hidden Membership is reachable only by direct link or Admin assignment.
* **A Customer cannot switch into the Membership:** A Membership currently in a presale period rejects a switch. See Upgrading and downgrading a Membership.
---
# 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.podplay.app/memberships/types-of-memberships/hidden-memberships.md?ask=&goal=
```
`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.
