> For the complete documentation index, see [llms.txt](https://help.memberplyhub.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.memberplyhub.net/membership-tiers/create-and-manage-membership-tiers.md).

# Create and manage membership tiers

## Create a tier

1. Open **Membership tiers**.
2. Select **Add membership tier**.
3. Enter a name and optional description.
4. Choose whether the tier is active.
5. Select the currency.
6. Choose a charging option:
   * Free
   * One-time fee
   * Monthly
   * Yearly
   * Monthly and yearly
7. Enter the relevant prices and an optional one-time joining fee.
8. Select **Add membership tier**.

For a yearly tier, you can add joining-date prices when new members pay different initial amounts depending on when they join. The normal yearly fee remains the renewal price.

## Update, deactivate or delete a tier

Select **Edit** on a tier to change its details. Make a tier inactive when it should remain in existing records but should not be assigned to new members.

Select **Delete** only when the tier is no longer needed. Memberply will protect records that must remain for operational history and offer an appropriate alternative where available.


---

# 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://help.memberplyhub.net/membership-tiers/create-and-manage-membership-tiers.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.