Apps and the Marketplace
Everything in your platform is an app, including the ones that were there on day one; see Tenants, apps and markets. This page is the day-to-day handling: adding one, configuring it, and taking it away again.
Where things are
App Studio has a dashboard, four entries, and one line per installed app:
| Screen | What it is |
|---|---|
| Dashboard | Installed apps and their executions over 24 h, 30 or 90 days |
| Marketplace | Everything you could install, from revenexx and approved partners |
| Installed Apps | Everything you have, with version, type and status |
| My Apps | Apps built for your company alone |
| API & SDK | For developers writing against the platform |
Below them, the navigation lists each active installed app so you can open it directly.
Install an app
- Go to App Studio › Marketplace.
- Open the app. Read three things on the detail page before anything else: the Publisher and whether it carries the Verified badge, the Pricing (Included, Free or Paid), and the Permissions requested.
- Install it.
The app is provisioned into your tenant, its tables are created, and its screens appear in the Cockpit navigation. Installed Apps shows the progress: Pending, Provisioning, then Installed, or Failed if something went wrong. If the row shows Consent required instead, the app is waiting for you: open Review & approve from the row's menu, read what it asks for, and approve it. Until you do, nothing of that app runs.
Approve an update that asks for more
This is the part worth knowing before it happens.
When a new version of an installed app asks for access it did not have before, it is not rolled out. The installation goes to status Consent required and your tenant keeps running the version you already consented to. Nothing breaks; the update waits. The App Studio dashboard shows the same thing as a card titled Waiting for your approval.
To act on it, open the app from Installed Apps and choose Review changes. The review shows what is different, section by section:
- New access requested — what the app can now reach that it could not before.
- New API operations — routes this version starts serving.
- New permissions you can assign — capabilities that become grantable.
- New scope dimensions — dimensions the app registers platform-wide, so other apps can scope their data by them.
- Removed API operations — what stops being served. Anything calling those gets a 404 from then on.
That last section is the one to read carefully if you have integrations built against the app. Approve new access when you are satisfied, and the version rolls out. If a version asks for nothing new, the same screen offers Record consent instead, which does what it says.
Configure an app
Each installed app has a Settings tab, generated from what the app declares. Two things about it are worth knowing:
Sensitive fields are write-only. An API key or password is marked sensitive and shows as set rather than showing its value. Leaving it blank keeps the current value; typing something replaces it.
Settings can be per market. A field is either global, one value for the whole tenant, or market-scoped. With Global selected in the top bar you edit the Global baseline, which applies to all markets. Switch to a market and the market-scoped fields below override that baseline for this market only; tenant-wide fields stay global. Each field carries a badge, inherited, market or all markets, so check before assuming a change applied everywhere.
Remove an app
Uninstalling, from the Danger zone on the app's Settings tab, removes the app from your tenant and its screens from the Cockpit. The data stays. The tables the app owns are preserved in your tenant database, and reinstalling from the Marketplace restores access to them.
That makes uninstalling reversible and therefore safe to try. It also means uninstalling is not a way to delete data. If you need data gone, that is a separate request; see Security and data protection.
Apps built for you
My Apps is where a custom app lives: one built for your company by your team or your implementation partner. It is a developer workflow rather than an administration one; the Developer Portal documents it.
The administration-relevant part: a private app is only installable by your tenant, it is not listed publicly, and it goes through the same access declaration and update-consent flow as anything from the Marketplace.
What to check
After installing, confirm the app reached status Installed and that its navigation entries appeared. If a colleague cannot see them, that is a user access question, not an installation one.
Next
- Subscription and billing — what a paid app does to your invoice.
- Tenants, apps and markets