# Discover apps: overview, listing, and data and access

The overview shows every app that is open to your organization and tells you what each one costs you. An app’s listing answers, in five tabs, what it can do, what it runs on, and what it does with your data. Read the section that fits your question. The tables are complete.

> **Type:** reference
> **For:** Anyone who wants to look for, compare, or check an app before installing it.
> **Prerequisite:** The read permission for apps. Without it, **Apps** does not appear in the navigation.
> **Where in the portal:** **Apps** › **Discover apps**

## The two pages under Apps

**Apps** separates what you have from what exists.

| Page | What you see there | How to get there |
|---|---|---|
| **My apps** | Only your organization’s installed apps, as a table with class, data areas, scenes, and status. | Navigation › **Apps** |
| **Discover apps** | The overview titled **Apps for your displays**: all apps that are open to your organization, plus the video wall. | The **Discover apps** button at the top right of **My apps** |

## The overview

Below the title is the count, calculated for your organization: how many apps there are, how many of them are in your package, and how many only from a larger package. If an app can be booked as an add-on, the line says that too. To the right of it, you choose the order under **Sort**.

| Sorting | Order |
|---|---|
| **Recommended** | The default. Apps for your industry come first, if your organization has one. Next come the apps you can install right away, then those that can be booked as add-ons, and last those that require a larger package. |
| **New** | The apps that have been in the store the shortest time come first. |
| **Recently updated** | The apps with the most recent version come first. |
| **A to Z** | By the app’s name. |

The **Search apps** field searches the name, the tagline, and the identifier of an app and filters immediately. If an update is waiting for your decision on an installed app, a banner such as “One update is waiting for your decision” with the names of the apps appears below it. For one app, **View** leads to its **Update** tab, and for several apps to **My apps** with the **Needs attention** filter.

Nothing is ever installed from the overview. A click on a card always leads to the app’s listing first, which says what it does with your data.

### Filters

The filters are on the left next to the cards. On a phone, the **Filters** button opens them in a sheet, and with filters set it reads something like **Filters (2)**. Each group allows exactly one choice, and **All** clears it again. Each value is followed by the number of apps that carry it, and a value without an app cannot be selected.

| Group | Values |
|---|---|
| **Category** | The store’s categories, see [All apps at a glance](/docs/apps/all-apps). |
| **Availability** | **In your package**, **From Pro**, and **Available as add-on**. If several packages are missing, the middle value is called **From a larger package**. |
| **Status** | **Installed**, **Update waiting**, **No setup needed**, and **Not installed**. |
| **Industry** | Only if your organization has an industry, and then only this one, for example **For pharmacies**. It is not preselected. Owners set the industry in the [Master data](/docs/organization/master-data). |
| **Language** | The languages in which the apps provide their texts. |

As soon as you search or filter, the number of results appears above the cards, for example “6 apps found,” with **Reset filters** next to it. If nothing matches, it says “No app matches your selection.”

### Collections and the video wall

Above the cards, the collections appear as a narrow strip, each with the prefix **Collection** and its title, such as **Ready right away**. A click shows only the apps in the collection, in their order and with the collection’s title and description above them. A second click clears the choice. A collection that applies to an industry is seen only by organizations in that industry. Next to the collections is **Updated this week** with the number of apps that received a new version in the last seven days.

As long as you are neither searching nor filtering, the tile **Core feature** with the title **Video wall** appears before the cards: “Combine several displays into one surface and play content on them together. Each video wall is booked separately.” **Book a video wall** leads to the **Order** page. The video wall is a function of the platform, not an app. It therefore appears neither among the cards nor in **My apps**. You can read more in [Video wall](/docs/apps/video-wall).

## The card of an app

At the top, each card shows the app’s main view, that is, what ends up on the display. An app without a widget shows its icon there. Below that are the icon and name, the publisher, with a shield for a verified publisher, then the tagline and the badges. In the footer, the left side says what the app costs you, and the right side its status.

| Place | Values |
|---|---|
| Badges | **Pro** for an app included from the Pro package on, **Add-on** for an app with a monthly price of its own, **Trial** for an app we are still testing, **Beta** for a version your organization receives before it is released to everyone, **Essentials** for an app without which your displays lack basic building blocks, and **Grandfathered**. Apps included in every package carry no class badge. An app can carry several badges. |
| Footer left | **In your package**, **From Pro**, **+ … net per month** with the price, **Booked**, or **Stays free for you**. |
| Footer right | **Installed**, **Update waiting**, **Not in your package**, or **View**. |

No card shows installation counts, ratings, or a “popular” label.

## The listing of an app

At the top is the header with icon, name, publisher, with the note **verified publisher** for a verified publisher, and the category. If the app serves an industry, that appears there too. Below that come the tagline, the badges, and the facts of the offered version, for example “Version 1.4.0 · updated on October 12, 2026 · German.” The action card is on the right, and five tabs sit below it. Each tab has its own address, so a link leads directly into it.

| Tab | Contents |
|---|---|
| **Overview** | What is new in the latest version, **What the app does**, the **Description**, **Runs on** with the device types, the **Orientation** (landscape or portrait) and the behavior **Without a network**, plus **Goes well with** with related apps. |
| **Views** | Every view of the app as a labeled picture in its true aspect ratio. A click shows it in full size. Below is the **Scene example**: “This is how the app looks in a scene.” Each view can be picked separately in the scene editor. |
| **Data & access** | The five blocks from the section further below. Next come **Privacy** with **Recipients** and **Storage location**, the app’s **Terms**, and, where they exist, **Connects accounts** and **Unlocks in the portal**. |
| **Setup** | The steps to the display, **Roles & permissions**, **Publisher and help**, and the **Technical details** with identifier, version, size, signature, and category. If the app needs nothing, it says “This app needs no setup. It runs as soon as its widget is in a scene.” |
| **Versions** | Every version your organization has received or would receive, the latest first. For each version it shows the date, what is new, whether the change required consent, and whether it has been retired. Your installed version carries **Your version**, the offered one **current**. |

If an app does not exist in the store, it says “This app is not in the store.” If it is in the store but no version reaches your organization, it says “This app is not offered to your organization at the moment.” In both cases **Back to overview** takes you back. An app that we have temporarily switched off is missing from the overview. Its listing remains reachable and states the reason.

## The action card: one situation, one button, one reason

The card on the right states in its first line how the app stands for your organization. Below that it carries exactly one button and the reason as a full sentence. Next come the quick facts, the short summary of the terms with the **Full text** link, the app’s manual, and **Contact support**.

| First line | Button | Sentence below, for example |
|---|---|---|
| “Included in your Starter package” | **Install** | “No extra cost, uninstall at any time.” |
| “From Pro” | **View packages** | “Calendar is part of the Pro package.” In addition, the sentence names apps that the package also brings. |
| “+ … net per month” | **Book and install** | “Prorated until October 31, 2026, monthly after that. Cancel at the end of any month.” |
| “Booked · … net per month” | **Install** | “Booked at … net per month. Cancel at the end of any month.” |
| “Stays free for you” | **Install** | “Your package does not include this app. It stays free for you because you already use it.” |
| “Installed · version 1.4.0” | **Open app** | “Active in 3 scenes. Setup complete.” |
| “Installed · version 1.2.0” with **Update waiting** | **View update** | “Version 1.3.0 is waiting for your decision: new permissions.” |
| “Not in your package” | **View packages** | “Your package no longer includes this app. It runs again from Pro.” |
| “Switched off” | none, **Open app** for an installed app | “We have switched the app off for the time being.” |

Only owners may install. Anyone who may ask the owners sees **Ask the owners to install** instead, with the sentence “Only owners can install apps. We send them your request along with a sentence from you.” After the request, it says, without a button, “Request sent on October 17, 2026.” If someone else on the team has asked, the sentence says so. If you also lack the permission to ask, it says only “Your role cannot install apps or ask the owners to do so.” How the request works is described in [Install or book an app](/docs/apps/install-app#ask-the-owners-to-install-an-app).

| Quick fact | Values |
|---|---|
| **Runs on** | How many of your displays the app supports, for example “all 4 displays,” “3 of 4 displays,” or “none of your 4 displays.” Only displays whose device type is known are counted. If the platform does not know any device type yet, the fact names the app’s device types. If the app gives no information, it says **Not specified**. |
| **Own data** | The number of data areas the app creates, otherwise **None**. |
| **External** | **Fetches data** or **No connection**. |
| **Setup** | The number of steps, otherwise **Ready to use**. |
| **Views** | The number of views. |
| **Languages** | The languages in which the app provides its texts. |

## Beta: new versions before everyone else

Some versions appear first in the **Beta** channel. Your organization receives them there if it has enrolled in the channel, for a single app or for all. The card and the listing header then carry the **Beta** badge. In the **Update** tab of the installed app, such a version appears as an **Offer**: “Version … is ready for you in the Beta channel.” You decide yourself whether to accept. Until then, your installation stays on its version. A version in the Beta channel has been tested but is not yet released to everyone.

Today, an organization can enroll in and withdraw from the channel through the API, see [What can your own programs do with Szenera?](/docs/developers/about-integrations). The portal does not have a switch for this yet.

## Data & access: the five blocks

The same section appears in three places: in the listing’s **Data & access** tab, in the installation’s consent dialog, and later in the **Settings** tab of the installed app. It answers what the app does with data, even when the answer is “nothing.” In the store it applies to the offered version, and on the page of an installed app to the installed one.

| Block | What it answers | Example |
|---|---|---|
| **Creates for you** | Which data sets of its own the app creates. If it creates none, it says “This app does not store any data of its own.” | **Pharmacies on duty** creates **Locations** and **Duty rosters**. |
| **Reads existing data** | Whether the app accesses data sets you already have. Named are **Organization details**, **Organization logo**, **Media library**, **Team and accounts**, and **Display locations**. | **Weather** and **Calendar** read the **Organization details**. Most apps read nothing: “This app does not access any of your existing data.” |
| **Adds data** | Whether the app contributes to existing data sets. “Changing or deleting is impossible. An app can only contribute.” Where an app adds something, the name of this access appears. | For all of today’s apps, this reads “This app does not add anything to your existing data.” |
| **External connections** | Which outside service the app talks to, what for, and what is transmitted (“What is sent: …”). | **Pharmacies on duty** queries public duty directories. The address and radius of the locations you created are sent. |
| **When you uninstall** | What happens to the app’s data, with the names of its data areas. If the app creates nothing, it says “This app leaves no data of its own behind.” | “Locations and duty rosters are kept. You can have them deleted for good afterwards.” How that works is described in [Uninstall an app](/docs/apps/uninstall-app#delete-the-data-of-an-uninstalled-app). |

Two cards follow in the **Data & access** tab. **Privacy** names the **Recipients** outside the platform with their purpose and the **Storage location**, plus the link to the **Privacy policy**. **Terms** shows the short summary of the app’s terms with **Full terms of the app**. If the app brings none, it says “This app does not come with terms of its own.”

## Roles & permissions: the other question

**Roles & permissions** appears in the **Setup** tab, in the consent dialog, and in the **Settings** of the installed app. It does not answer what the app accesses, but who on the team may operate it. With the installation, these permissions are added to your organization’s permission catalog. If the app brings none, it says “This app does not bring permissions of its own.”

## Related

- [Install or book an app](/docs/apps/install-app)
- [All apps at a glance: categories, classes, and collections](/docs/apps/all-apps)
- [My apps and the page of an installed app](/docs/apps/my-apps)