> 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-activate-a-system.md).

# How to Activate a System

Please be advised that we do not have an option to temporarily activate a System. If you want to test the transactions, I would advise you to activate the system instead.<br>

To activate your system, please email <accounting@movatic.co> to pay for your license.

1. Once paid, the system will be moved out of the demo mode.
2. Customer Support will provide you with an update that the system is already activated.

In addition, once it's activated, you can setup the system by completing several system setups, including new customer setup options, admin user setup, system access, entering terms of service, and personalized branding. You can also set your system to be open or temporarily closed on the app by going to Settings > General > System Status.

<figure><img src="https://3693766063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxId4PbGGTlBib03KztrO%2Fuploads%2F11QczbfqAfaTOuTFmHFL%2Fimage.png?alt=media&amp;token=2b90c7b4-c04e-4757-b290-eee520578208" alt=""><figcaption></figcaption></figure>


---

# 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-activate-a-system.md?ask=<question>&goal=<user_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.