# Install or book an app

After this guide, the app is installed for your organization, its widgets are ready in the scene editor, and you have knowingly agreed to the app’s permissions and terms. You book paid apps beforehand on the **Order** page. If you are not allowed to install, you ask the owners to do it.

> **Type:** guide
> **For:** Owners. Instead of **Install**, managers see the **Ask the owners to install** button. Members see the store in full but without a button.
> **Prerequisite:** A package that includes the app or, for an add-on, the willingness to pay a monthly price.
> **Where in the portal:** **Apps** › **Discover apps** › the app’s listing › **Install**

Nothing is ever installed silently from the store. A click on a card always leads to the app’s listing first, and before the app becomes active, the portal asks for your explicit consent. You reach the store through **Apps** and the **Discover apps** button at the top right, or through the quick action of the same name on the **Dashboard**.

## Steps

1. In the action card on the right of the app’s listing, click **Install**. The consent dialog opens. Its title is **Install** followed by the name of the app, and below it reads “Review what the app does with your data, then confirm the installation.”
2. Check the **Data & access** section with its blocks **Creates for you**, **Reads existing data**, **Adds data**, **External connections**, and **When you uninstall**.
3. Expand **Roles & permissions** if you want to know who on the team may operate the app later. These permissions are added to your organization’s permission catalog with the installation. They control who operates the app, not what the app accesses.
4. Read the **Important note** section, if the app brings one. It is the short summary of its terms. The link **The app’s full terms** opens the full text in a new tab, and the half-completed dialog stays where it is. You find the same text in the listing’s **Data & access** tab.
5. Select the required checkbox. If the app brings terms, it reads **I have read the permissions and the app’s terms and agree to them.**, otherwise **I agree to the access and the notes.** It is deliberately a single checkbox for the whole process.
6. Click **Install**. The button becomes active only once the checkbox is selected.

## Options

### Book a paid app

Apps in the **Add-on** class are not part of any package. Their card carries the **Add-on** badge and, in the footer, the price as **+ … net per month**. In the listing, the button is called **Book and install**, and the sentence below it says how billing works, for example “Prorated until October 31, 2026, monthly after that. Cancel at the end of any month.”

Booking does not happen in the store but where money changes hands. **Book and install** leads to the **Order** page with its sections **Scope**, **Invoice profile**, **Payment**, and **Review**. At the top is the occasion, “You are adding the … app.” At the end come the message “Order accepted.” and, under **Next step**, “The booked app is ready to install.” **Install now** leads back to the app’s listing and opens the consent dialog there as described above. The order is covered in detail in [Change your contract](/docs/billing/change-contract).

The action card then says “Booked · … net per month.” After a cancellation, the sentence below it names the last day, for example “Canceled as of October 31, 2026. You can use the app until then.” What applies when you remove a booked app is described in [Uninstall an app](/docs/apps/uninstall-app).

### Ask the owners to install an app

Only owners may install. As a manager, you ask the owners to do it, with a sentence from you.

1. In the app’s listing, click **Ask the owners to install**. The dialog **Ask the owners to install …** opens: “The request goes to all owners of your organization, in the bell and by email.”
2. Under **A sentence for the owners**, write what you need the app for. The field is optional and accepts up to 280 characters, and below it **… characters left** counts along.
3. Click **Send request**. The message **Request sent** appears, and the action card shows “Request sent on …” instead of the button.

Every owner receives the request in the bell (“… asks for an app”) and by email with your sentence. The link in it leads to the app’s listing. The same request goes out only once within seven days. A second attempt reports “The owners already have your request. We will not send it again.” Once an owner installs the app, the request is settled.

### What your package includes

Every app belongs to a **Class**. It decides whether your package includes the app. Which classes exist and how the store shows them is described in [All apps at a glance › Classes: what your package includes](/docs/apps/all-apps#classes-what-your-package-includes).

If your package does not include the app, it stays visible. The action card then shows, for example, “From Pro” with the sentence “Calendar is part of the Pro package.” and names apps that the package also brings. **View packages** leads directly to [What do you pay for: packages, seats, and add-ons?](/docs/billing/about-packages-and-seats).

## Check the result

- The message **App installed** appears, and the portal takes you to the app’s page. Its **Overview** tab shows the setup, if the app requires steps.
- In the scene editor, the app’s widgets are in the palette, under the category that also appears in the store.
- In **My apps**, the app shows the status **Ready** until a scene uses it.
- You agreed to exactly the set of permissions you saw. If it changed between display and confirmation, we decline: “The permissions of the app have changed. Please reload the page.”

## If the app does not fit every display

Under **Runs on**, the listing names the device types the app runs on, and the action card counts how many of your displays match. If you assign a display a program or a scene with an app that does not run on its device type, the assignment warns under **Not everything runs on this display**: “According to its publisher, … does not run on …. The assignment applies anyway.” The assignment is saved regardless. Check on the display whether the scene looks the way it should, or choose a display whose device type the app supports.

## If something goes wrong

| Symptom | Meaning | Solution |
|---|---|---|
| **Install** stays gray in the dialog | The required checkbox is not selected. | Select the checkbox. |
| **Ask the owners to install** appears instead of **Install** | Only owners may install. | Send the request, see above, or talk to an owner directly. |
| The action card has no button, only “Your role cannot install apps or ask the owners to do so.” | Your role may neither install nor ask. | Talk to an owner, see [Permissions by role and by area](/docs/organization/permissions-by-role). |
| “This app is only included from a larger package.” | The class is above your package. | Click **View packages** and adjust the package. |
| “This app is paid and must be booked first.” | An add-on app. | Choose **Book and install**. The button leads to the **Order** page. |

The remaining messages at this point are listed with their solutions in [When an app does not run](/docs/apps/troubleshooting). They include already installed, not available, no further apps, retired, changed permissions, and failed installation.

## Related

- [Discover apps](/docs/apps/discover-apps) — overview, filters, collections, and an app’s listing.
- [When an app update is waiting for your decision](/docs/apps/app-update-decision) — what to do after an update with new permissions.
- [What do you pay for: packages, seats, and add-ons?](/docs/billing/about-packages-and-seats) — which package includes which apps.