> 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/admin-site/users/adding-user-to-a-paid-membership.md).
# Adding User to a Paid Membership
Adding a new user to a paid membership in our system is incredibly straightforward. The process has been simplified to ensure that administrators can quickly and easily extend the benefits of our premium features to more users. By simply navigating to the "Users" section in the Admin Site, select the user you would like to add a membership to, select the "Add Membership" option on the "User Membership" panel, click on the dropdown menu and select the membership you want to add to the user, and lastly, add one free renewal to the newly added membership, this will ensure that the membership will be active after completing the process.
When adding 0 Free renewal, our software will try to charge the user for the first time purchase of the membership. However, adding 1 Free Renewal, allow our software to charge the user by the end of the membership period.
Adding paid membership to user
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.movatic.co/admin-site/users/adding-user-to-a-paid-membership.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
