Apps
An app is an installable unit inside your instance: its data structure
plus the pages, forms, navigation and roles that belong to it. The built-in core app
hosts the platform itself; your own apps live alongside it.
Why apps
- Isolation inside the instance. Each app's tables live in the app's own
data space. A
crmapp'scontacttable iscrm.contact— it can't collide with another app's tables. - Access follows the app. Creating an app also creates an
<app>_accessrole. Only users holding it can reach the app's data and navigation, which gives you a two-tier model out of the box: global roles for platform features, app roles for app data. - Portability. Apps are the unit of packaging: the marketplace installs apps, releases promote app changes between environments.
Creating an app
Apps → New app — pick a slug (this becomes the app's namespace) and a display name. The platform provisions the app's data space, the access role, and an empty navigation container.
Installing from the marketplace
Apps → Marketplace lists packaged apps published for your core version. Installing creates the app, its structure, UI and seed data in one step, and records everything as an update set so the install is versioned like any other change.
App context in the API
Every data API path names the app explicitly:
GET /v1/<org>/<app>/<table>
GET /v1/acme/crm/contact?limit=20