App Studio
Everything in the Revenue Cloud is an app, including the ones that were there on your first day. App Studio is where you see which apps are installed, add new ones from the Marketplace, configure them, and control what each is allowed to reach. It is the smallest Studio by screen count and the one with the widest blast radius: what you install here decides which screens the other Studios have.
/apps prefix. The neighbouring Settings area (/settings) is not a Studio — it holds your tenant's account, team, billing and security — and is documented under Administration.What lives here
An app is a self-contained piece of commerce functionality. Products, prices, customers, orders, inventories, shipping, payments — each is an app, not a built-in module. An app brings its own data model and its own Cockpit screens, and it declares both rather than hard-coding them. This is why Commerce Studio's sidebar changes when you install something: the app tells the Cockpit which navigation entries, list screens, detail screens and dashboard widgets it contributes, and the Cockpit renders them.
The practical consequence is worth stating plainly: your Cockpit is not the same as anybody else's. A tenant without the inventories app has no Stock screens. A tenant that installed a punchout connector has screens a pure webshop tenant does not. When a colleague describes a menu entry you cannot find, the first question is which apps each of you has installed.
Where an app comes from decides how it is managed.
| Kind | Where it comes from | Notes |
|---|---|---|
| Included | Bundled with your billing package | Activated for you. The core commerce apps are usually these. |
| Public | The Marketplace | Available to any tenant. May be free or paid on top of your subscription. |
| Private | Built for you | By your own team or your implementation partner. Visible only on your tenant. |
This is also how the platform grows: the planned core apps — Search, Localization, Quotes, Promotions, Cost Centers, Approval Workflows, configurators and Smart Reordering among them — arrive through exactly this install path, from the Marketplace, with the same permission list to read and the same dependency prompts, rather than as a platform upgrade that changes your Cockpit overnight.
Dependencies are declared, not assumed. An app can require another app to function. Some are installed automatically alongside it; others — typically the ones that cost money or that you should choose consciously — are presented for you to install yourself, so nothing paid appears on your bill without a decision. If an install prompts you for a second app, that is this mechanism, not an error.
Permissions are the part to read slowly. Apps get no access by default. An app declares what it needs — which data it touches, whether it may call out to the internet, which storage it uses — and you are shown that list at install time. For an app from a vendor you do not know, this list is the entire basis for trusting it. The same review applies to updates that ask for more than the version you approved.
Settings are per-tenant, and where it matters, per-market. An app declares which settings it has and the Cockpit renders the form; there is no separate configuration file to find. This is how the same shipping app can carry one rate matrix for Germany and another for Austria.
Uninstalling is not a neutral act. Removing an app removes its screens from every Studio that hosted them, and the entities it owned stop being editable in the Cockpit. Treat an uninstall on a live tenant as a change with a rollback plan, not a tidy-up.
The screens
| Screen | Path | What it does | Documented in |
|---|---|---|---|
| Dashboard | /apps/dashboard | Install count, executions and build success, plus the SDK quickstart. | Dashboard |
| Extend and Develop › Marketplace | /apps/marketplace | Browse and install public apps. | Marketplace |
| Extend and Develop › Installed Apps | /apps/installed | Every app on your tenant, with its version and permissions. | Installed apps |
| Extend and Develop › My Apps | /apps/my-apps | Private apps you or your partner built, and their deployments. | My apps |
| Extend and Develop › API & SDK | /apps/api | Signpost into the developer documentation. | API & SDK |
| Apps › (one entry per installed app) | /apps/installed/{owner}/{name} | The app's own page: what it does, its permissions, its changelog. | Installed apps |
An app's configuration form opens at /apps/settings/{owner}/{name}, from the Settings tab of its detail page rather than from the sidebar — see App settings.
Adjacent: Settings
Settings sits below the Studios in the Cockpit's rail, behind the gear icon. It is your tenant's own administration rather than part of any Studio. Its reference pages live under Settings; the concepts are covered under Administration.
| Screen | Path | What it does | Documented in |
|---|---|---|---|
| Dashboard | /settings/dashboard | Account KPIs and what needs attention. | Dashboard |
| Overview | /settings | Project profile and legal details. | Overview |
| Account › Profile | /settings/profile | Your own user account and preferences. | Profile |
| Account › Team | /settings/team | Who has access to the Cockpit. | Team |
| Account › Billing | /settings/billing | Plan, invoices, payment methods and addons. | Billing |
| Account › Partner | /settings/partner | A publisher-dashboard preview with sample data. | Partner |
| Services › Mail | /settings/mail | Your tenant's transactional mail service. | |
| Services › Search | /settings/search | The search indexes and their collections. | Search |
| Services › Auth & Security | /settings/security | The login policy for your storefront customers. | Auth & Security |
| Developer › API Keys | /settings/api-keys | Keys for calling the platform. | API keys |
| Developer › Git Accounts | /settings/git | Git connections used for deploying sites and apps. | Git accounts |
Domain management is not in Settings: the Domains card on the Settings dashboard opens Experience Studio › Domains.
Single sign-on for your Cockpit users is covered in Single sign-on.
Common tasks
- Install an app from the Marketplace — and read the permission list before you confirm.
- Understand the tenant model — what "your tenant" contains and where its boundaries are.
- Invite your team — the first people who need access.
- Set up users and roles — who may see prices, approve orders, or change the catalog.
- Set up single sign-on — federate with Active Directory or Azure AD.
- Review security — API keys, sessions and what to check quarterly.
What is planned for this Studio
App Studio itself changes least. Its screens are the Marketplace, the installed list, your own apps and the API reference, and that is unlikely to grow — the mechanism is already the mechanism.
What changes is the Marketplace's contents. Seven areas of this Help Center are written at their 12-month state, and every one of them is an app you will install here: Search and Localization for the catalog, Quotes for sales, Promotions for marketing, Procurement & Approvals for the customer domain, Configurable Products & Spare Parts, and Recurring Orders & Subscriptions with Smart Reordering behind it in AI Studio.
Two things follow from that, and both are decisions rather than clicks. Installing is a billing question — some of these are included in a package and some are paid, which is exactly why a dependency that costs money is presented for you to confirm rather than pulled in silently; see Billing. And installing is a permission question: an app that reads your customers' cost centres and approval limits is handling your buyer's internal organisational data, and the permission list at install time is where you check what it may reach. Read it the same way you would read a new supplier's contract, and do it before the app is live rather than after.
How it relates to the other Studios
App Studio decides what the other Studios contain. Commerce Studio in particular is assembled entirely from installed apps — its sidebar sections are populated by whatever each app declares. Experience Studio's themes and Integration Studio's connectors follow the same install and permission model, and AI Studio's agents do too. One mechanism, four surfaces.
It does not hold your data. Apps own entities; App Studio manages the apps. You look up a product in Commerce Studio, not here. What you do here is decide whether the products app exists on your tenant at all, at which version, and with which permissions.
Billing runs through it. Which apps are included follows your billing package, and paid apps from the Marketplace add to what you pay. If a screen someone expects is missing, the answer is sometimes a package question rather than a configuration one — see Billing.
Building on this Studio?
If you are writing code against it rather than working in it, the Developer Portal documents the same Studio for developers — APIs, SDKs and extension points.