> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/checks/app/app_0003.md).

# Demo users enabled

<table><thead><tr><th width="138">Check ID</th><th>APP_0003</th></tr></thead><tbody><tr><td>Category</td><td>Security</td></tr><tr><td>Summary</td><td>Demo users is a feature in Mendix that will create test users for you automatically when you run your app (locally or in the cloud). Although this is a handy feature for quickly testing different user roles, it presents a possible security risk as the names of demo users are easy to guess and they bypass SSO. Demo users should never be enabled in an app deployed to the cloud. Note: Mendix prevents demo users from being created in non SANDBOX environments, thus this check is only relevant (and will only be checked) in Mendix Cloud sandbox environments.</td></tr><tr><td>Options</td><td>This check does not have any options.</td></tr><tr><td>Pass</td><td>Demo users are disabled for revisions deployed to a SANDBOX environment.</td></tr><tr><td>Fail</td><td>Demo users are enabled and the revision is deployed to a SANDBOX environment.</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluestorm.io/checks/app/app_0003.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.