# Membership Authorization User Experience
This page details the user experience of the different [**types of Membership Authorization**](https://documentation.movatic.co/admin-site/memberships/authorization-types).
## Admin Authorization
On the admin site, you have set the authorization as Admin approval:
On the user side, a user will need to click on **Memberships** > **Search for the Membership** (In this example it's Testers Club 1) > **Select the Membership** > **Request Access.**
The app will send their request to the admin once they have clicked **Request Access.** Alternatively, they 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.
Going back to the dashboard, once the user has requested access, you can go to **Memberships** > Click on the **Pending User Membership tab** > **Click on the User** > **Approve or Reject** the user.
When you have approved the user, the user can check back on the status by going to **Memberships**. Alternatively, a pending status will also display if you haven't made a decision yet.
If you decide to click the **Reject** button on your dashboard, you will be asked to provide a reason for why the request was rejected. Keep in mind this note is only for internal use and will not be shown to the user.
On the user side, it will show that their request has been rejected and when they click "**Your account was rejected**" they will be prompted to contact [**Customer Support**](https://documentation.movatic.co/admin-site/customer-support).
If you decide to change your mind and want to approve the rejected user, you can go to your **Users** > **Select** **the User** > look for the **User Memberships** section and click **Approve** button. The user will immediately be added to the Membership and their status on the app will be updated.
## Email Authorization
This authorization requires a user to have a specified domain on their email. For this example, only users with the "**@movatic.co**" domain can join the membership.
The user will need to go to **Memberships** > **Search for the Membership** (In this example, it's Testers Club 2) > **Select the Membership** and they will be asked to enter in a "@movatic.co" email domain.
If they input a different domain, the screen will display a red banner that will indicate that they have used an **invalid email**. If they enter the correct email domain, a **4-digit code** will be sent through their email for verification.
The user will receive an email from **** with their confirmation code. When they are able to input the code on the app, they will see a green banner that will display that they been successfully added to the membership.
## Password Authorization
This authorization requires a user to join a membership by entering a password. In this example, we have set the password to "Yellow".
The user will need to go to **Memberships** > **Search for the Membership** (In this example, it's Testers Club 3) > **Select the Membership** and they will be asked to enter a password.
If they enter the wrong password, a red banner will display that they have input an incorrect password. If they enter the correct password, a green banner will indicate that they have been successfully added to the membership.
{% hint style="info" %}
Alternatively, a user can also look up your memberships by clicking on the **Station pin** on the map > Select the **Rate** > Select **Membership Required** > **Select a Membership**
{% endhint %}
---
# Agent Instructions: 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:
```
GET https://documentation.movatic.co/admin-site/memberships/authorization-types/membership-authorization-user-experience.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
