> For the complete documentation index, see [llms.txt](https://docs.valorx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valorx.com/valorx-fusion/getting-started/getting-started-with-valorx/apps-list.md).

# Apps List

With connection(s) established, a list of Apps will be displayed. If you have multiple connections, the list of Apps will change by switching the **Active** **Connections** tab.

The Apps List will change dynamically for App Designer and Runtime User - allowing them access different functionalities. 

### App Designer View

An App Designer can run an app in **Runtime** mode, edit an app in **Design Studio** mode, and administrate the Apps. 

![](/files/-MGHUGPm2g6e996xA0Ge)

#### Runtime User View

Runtime users can only run Valorx Fusion Apps that are assigned to them by the App Designers using Access Control.

![](/files/-MGHT5xDFK1lNZ0fnwx9)

{% hint style="info" %}
Access Control is only honored in Production environment. 

Sandboxes are usually used for development and UAT. To streamline the process, runtime users can run any apps in sandboxes, as long as they have the Valorx Permission set assigned to them.
{% endhint %}


---

# 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.valorx.com/valorx-fusion/getting-started/getting-started-with-valorx/apps-list.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.