> 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/faq/general/how-to-setup-and-test-new-system.md).
# How to Setup and Test New system
To successfully setup and test your new system at your company, please follow the steps outlined below:
1. Create a[ new hardware](https://documentation.movatic.co/admin-site/modes/add-a-new-hardware) for your system based on its specific type.\
-Ensure that all required[ assignments](https://documentation.movatic.co/admin-site/modes/assignments) are accurately made.
2. Generate a free[ membership](https://documentation.movatic.co/movatic-app/user-membership-on-users-page) for the system. By default, new systems operate in demo mode and require memberships. You can identify if your system is in demo mode by checking the settings, where you will encounter the following warning message: "This system is a demo system and is not visible without a membership.
Please contact your setup partner to activate this system.
1. If you haven't already done so,[ register](https://documentation.movatic.co/movatic-app/user-account/account-set-up) for the[ Movatic mobile app](https://documentation.movatic.co/movatic-app).
2. Once you have logged into the app,[ add the new membership](https://documentation.movatic.co/movatic-app/user-membership-on-users-page) to your account.
3. Attempt to initiate a[ new rental](https://documentation.movatic.co/movatic-app/rentals/first-rental) to test the functionality of the system.
By following these steps, you will be able to add resources to your new system and perform a comprehensive test to ensure everything functions as expected. You won’t be charged with testing your system.
---
# 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/faq/general/how-to-setup-and-test-new-system.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.
