> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/movatic-app/user-membership-on-users-page/add-a-membership.md).
# Add a Membership
## Membership that require access
A user will need to click on **Memberships** > **Search for the Membership** (In this example it's Testers Club 1) > **Select** t**he Membership** > **Request Access.**
Admins can setup three different types of access:
* Administrator Authorization: Requires that an administrator of the system approve the request made by the user.
* Email Authorization: Users must have an email address ending in a specific domain, a code will then be sent to the email in order to verify the membership.
* Password Authorization: Users must enter a predefined password that has been setup by system admins.
Users can see on their Memberships if their access is still pending and if they click **Authorization Pending**, they will be prompted to contact support to follow up on their status.
The admin decides is this membership requires a payment or not, this will be indicated before selecting the membership, by agreeing to a paid membership charges will be made to the user based on the payment terms indicated.
---
# 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://documentation.movatic.co/movatic-app/user-membership-on-users-page/add-a-membership.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.