# Apps for the Dasbhoard

The Apps created with MyApps are published in the Cloud4Wi Dashboard and they offer the option to show in the Admin Panel configuration page when they are opened.

This can be used, for example, to create a **configuration page** of an App but also to create pure back-end applications meant to be displayed on the Admin Panel, such as a reporting dashboard.

The apps show up on the Apps page under the category configured when initializing the app and also under the Dev tab.

Here, is an example of an app (Video Advertising) built with MyApps, that offers a configuration page that can be opened directly from the Cloud4Wi Dashboard.

‍

![](https://uploads-ssl.webflow.com/5eb42691bf103600ee3afc30/6083091813f76729c1130f71_dashboard_example.gif)

### How it works

The diagram below shows the flow of launching the app from the Cloud4Wi Dashboard.

‍

![](https://uploads-ssl.webflow.com/5eb42691bf103600ee3afc30/608309432189ebcfd2552c84_dashboard_workflow.png)

‍<br>

For example, if your app is hosted on your server on a domain

**<https://myapp.mydomain.com>**

‍<br>

your app server will receive an HTTP call with the following structure:

<https://myapp.mydomain.com?**sk**=skvalue&**trg**=trgvalue&**opts**=optsvalue&**cburl**=cburlvalue><br>

‍

There the list of parameters appended to the URL:

* **sk**: is the session key. This parameter allows you to use the Context APIs to retrieve session context (info about the user, the location etc..)
* **tgr**: this parameter includes some values that represent the step of the Access Journey that invoked the app:\
  \- trOpn: Connect\
  \- trRgt: Sign up\
  \- trPlgn: Log in Attempt\
  \- trLgn: Log in\
  \- trLgt: Disconnect\
  \- false: When not part of the Access Journey
* **opts**:  this is a system value used by the Javascript SDK
* **cburl**: this is the econded value of the next step of the Access Journey. You can use this parameter to redirect the user to the next step of the Access Journey<br>

In this context, you can use the [Context APIs](/dev-hub/myapps/myapps-apis-and-sdk/context-apis.md) to gather info about the Organization where the app is launched. For advanced usage, you can also use the [REST APIs](/dev-hub/api-reference/getting-started.md).<br>

### Notes

Since Cloud4Wi is a cloud-based multi-tenant platform, an App can be installed in different Cloud4Wi Organizations. It is up to the developer to create the logic that allows an app to have different settings on different Organizations.

When a Manager opens the app from the Cloud4Wi Dashboard, Cloud4Wi calls the App Server with a **session key** that allows the retrieval of the Account data (Organization ID, Location ID) so that the app can save different settings per each Account.

Note that all the settings and saved data are the responsibility of the app developer and are hosted in the developer's Application Server.

‍


---

# Agent Instructions: 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:

```
GET https://create.cloud4wi.ai/dev-hub/myapps/creating-apps/apps-for-the-dasbhoard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.