> 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/owners-playbook/build-your-club/build-a-location/membership-tab-of-venue.md).

# Membership tab of Venue

### Overview

Configure default membership subscription settings at the venue (area) level. These defaults automatically apply when creating new memberships for that venue, saving time and ensuring consistency. If a venue doesn't have area-level defaults set, the system uses tenant-level defaults instead.

Use this feature when different venues have different membership policies, or when you want to streamline membership creation by pre-setting common values.

## Set Subscription Defaults for a Venue

* Navigate to the **Overview** page from the Dashboard
* Click on the venue (area) you want to configure
* Click the **Edit** button to open the venue settings drawer
* Click on the **Memberships** tab
* Expand the **Subscription Defaults** panel

\[SCREENSHOT NEEDED: Area drawer open with Memberships tab selected, showing Subscription Defaults panel expanded]

* Enter values for any of the following fields:
  * **Default Min. Commitment (days)**: Minimum number of days a member must be subscribed before they can cancel
  * **Default Min. Notice - Monthly (days)**: Minimum advance notice required for cancelling monthly subscriptions
  * **Default Min. Notice - Yearly (days)**: Minimum advance notice required for cancelling yearly subscriptions
* Leave any field blank to inherit the tenant-level default for that setting
* Click **Save** to apply your changes

\[SCREENSHOT NEEDED: Subscription Defaults panel with fields filled in, showing placeholder text "Inherit from tenant"]

When you create a new membership for this venue, these area-level defaults automatically populate the membership's commitment and cancellation notice settings. You can still override these defaults for individual memberships if needed.

## How Defaults Are Applied

The system uses a hierarchy when setting membership defaults:

1. **Area-level defaults** (if set) - These are the values you configure in the Subscription Defaults panel
2. **Tenant-level defaults** (if area defaults are not set) - System-wide defaults configured at the tenant level
3. **Zero** (if neither area nor tenant defaults are set)

**Example**: If you set "Default Min. Commitment (days)" to 30 for a venue, all new memberships created for that venue will automatically have a 30-day minimum commitment. If you leave it blank, the system uses the tenant-level default instead.

## Tips

* Set area-level defaults when venues have different policies (e.g., one venue requires 30-day notice, another requires 60-day notice)
* Leave fields blank if you want all venues to use the same tenant-level defaults
* You can still customize these values for individual memberships after creation
* Changes to area defaults only affect new memberships - existing memberships keep their current settings

You can set these defaults in the Company Settings page if you have the Owner role.

<figure><img src="/files/BySfNsxyZ6MMCiHNYhvV" alt=""><figcaption></figcaption></figure>


---

# 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/owners-playbook/build-your-club/build-a-location/membership-tab-of-venue.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.