> 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/settings/general/live-system-to-demo-mode.md).

# Live System to Demo Mode

This documentation addresses the scenario where the Movatic Admin System transitions into Demo Mode. This mode temporarily restricts access to certain functionalities, affecting the availability and searchability of the bikeshare program within the Movatic App for operators/admins.

**Impact on Operators/Admins**\
When the Movatic Admin System is in Demo Mode, operators/admins may encounter program unavailability. The program will not be accessible or searchable within the Movatic App during demo mode.<br>

**Recommended Action**

If you experience the above impact due to the Movatic Admin System being in Demo Mode, we recommend contacting Support:

Reach out to our support team at **<support@movatic.co>** to check if there are any account or licensing-related issues associated with the program.

Understanding the implications and recommended actions during the Demo Mode of the Movatic Admin System is essential to navigate any temporary restrictions in functionality. Reach out to our support team for swift resolution and assistance.

<br>


---

# 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/settings/general/live-system-to-demo-mode.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.