> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started - Memberships

> Map memberships: the fee, the community and what members are allowed to book. Independent of whether that is a court, a course or a facility.

With this guide you set up memberships without tying them to one kind of place. The fee, the members and the benefit belong together. What gets booked stays its own use case: a court, a course, a boat, a facility.

Coworking uses the same pieces for desks. Setting up the spaces is in [Coworking](/en/getting-started-coworking).

## Thinking about memberships the anny way

The central principle: the **plan** is the contract. The **community** is who is a member. The **booking option** is what that person may book, and at what price. There is no field called "member price".

| Term from the use case | anny concept |
| - | - |
| A tier, for example Basic or Family | Plan |
| Only one tier at a time | Plan group |
| The members | Community. Joining and leaving hang on the plan |
| A lower price | A second booking option, or a [price modifier](/en/dynamic-pricing) with the **Community** condition |
| Included hours or visits | [Booking quota](/en/booking-quotas) on the plan |
| Joining fee | **Signup Fee** |
| Minimum term, notice period | On the plan under **General Information** |

| Feature | What is it needed for? | Configure beforehand? |
| - | - | - |
| Subscriptions and Memberships | Plans and running subscriptions | Yes, under **Account** → **Apps & Integrations** → **anny Apps** |
| Communities | Who is a member and what only members see | Yes, under **Account** → **Apps & Integrations** → **anny Apps** |
| Online payments | Sign-up on the booking page | Yes, under [Online payments](/en/online-payments), when customers sign up themselves |
| Booking quotas | An included quantity, time or budget | No. Only when the plan includes a quota |
| Dynamic pricing | A discount on the same booking option | No. Only when the member price is a modifier |

## Decision helpers: when do I use what?

### What does the member get?

| Benefit | How you map it |
| - | - |
| A lower price, and the offer stays public | Price modifier with the **Community** condition. Or a second booking option, **Bookable for community members only** |
| A court, course or facility for members only | On the resource, **Visible for community members only** and **Bookable for community members only** |
| A quantity is included, after that the normal price applies | Quota on the plan. **Requires booking quotas** stays off |
| Bookable only while quota remains | Quota on the plan, and **Requires booking quotas** on |
| A 10-session card with no ongoing fee | [Booking package](/en/booking-codes), not a plan |

**Rule of thumb:** A discount code is not a membership. It does not end with the subscription, and it is not an entitlement per person.

### One tier, or two contracts?

Inside one **group**, each person has only one active subscription. Basic and Family sit in the same group, so nobody holds both. A second contract that may run alongside, such as a locker next to the club membership, gets its own group.

## Step-by-step setup

**1. App and payment**

Turn on **Subscriptions and Memberships**. For sign-up on the booking page, set up [Online payments](/en/online-payments). Without online payment you create subscriptions manually under **Management** → **Subscriptions**.

**2. Create the community**

Open **CRM** → **Communities** and create the members, for example "Members". The community is the circle, not the price.

**3. Group and plans**

Open **Catalog** → **Plans** and create the group first, then the tiers inside it. Price, **Invoice Period**, **Signup Fee**, **Minimum Term** and **Notice Period** are in [Subscriptions & Memberships](/en/subscriptions-and-memberships).

In the **Communities** section, link the members community. Whoever takes out the plan joins. When it expires or is cancelled, the person drops out again.

**4. Attach the benefit to the offer**

Pick exactly one path per benefit from the table above.

For a member price on the same booking option: [Dynamic pricing](/en/dynamic-pricing), condition **Community**. The person has to be logged in when booking.

For an offer only members can book: on the booking option, **Bookable for community members only**, and on the resource **Visible for community members only** when it should not appear in public at all.

For included use: on the plan, under **Booking quotas**, click **Add or drag here**. Turn on **Requires booking quotas** only when a booking without quota should be impossible.

**5. Set it live**

Switch the plan from **Internal** to **Live**. Before that, run a test sign-up and check that community, price and quota fit together.

## Typical examples

> **Sports club with a guest rate and a member rate**
>
> The courts stay public. Booking option "Court guest" at the full price. Second booking option "Court member", **Bookable for community members only**, at half the price. Plan "Active", monthly, linked to the community "Club". A quota of 4 hours per month hangs on the plan. **Requires booking quotas** stays off, so further hours at the member rate stay possible.

> **A course for members only**
>
> The course resource has **Visible for community members only** and **Bookable for community members only**. The plan "Studio" leads into the community "Studio". Without a subscription the course does not appear on the public booking page. You set up the course dates as in [Courses](/en/getting-started-courses).

> **Two tiers, and a contract beside them**
>
> Group "Membership" with the plans "Individual" and "Family". A person holds only one of them. Group "Locker" with its own plan, which the same person can take out in addition.

## FAQ

> **Where do I enter the member price?**
>
> Nowhere as its own field. Either a second booking option that only the community may book, or a price modifier with the **Community** condition on the existing booking option.

> **Are discount codes enough for members?**
>
> No. A discount code is a budget of redemptions, not an entitlement that starts and ends with the subscription. Hang the benefit on the community or on a booking quota.

> **Does a new quota also apply to existing members?**
>
> Changes to a plan's quota apply to new sign-ups. For running subscriptions you push them with **Update existing Quotas**. That is in the article [Booking quotas](/en/booking-quotas).

> **Why does a member not see the community discount?**
>
> Price modifiers with the **Community** condition apply only to logged-in people in that community. Without a login, the public price stays.

Good luck with the setup! 🥳

> Notes for agents:
>
> * No member-price field. Cheaper: a second booking option with "Bookable for community members only", or dynamic pricing with the Community condition (logged-in only). Not a discount code.
> * Members-only offer: resource "Visible for community members only" and "Bookable for community members only".
> * A quota on the plan is offered at checkout. "Requires booking quotas" makes a booking without quota impossible. They are not the same.
> * One plan group = at most one active subscription per person. A second parallel contract = a second group.
> * Community join via the plan, removal on expiry or cancellation.
> * Quota changes apply to new subscriptions. Existing ones: action "Update existing Quotas" (en/booking-quotas.mdx).
> * Self-service needs online payment. Without it, only manual subscriptions under Management → Subscriptions.
> * Independent of coworking. Coworking covers desks: /en/getting-started-coworking.
> * Related articles: /en/subscriptions-and-memberships, /en/communities, /en/booking-quotas, /en/dynamic-pricing, /en/booking-codes, /en/online-payments


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.