Publishing workflow for apps
This folder is for app developers who need to know how content gets from an editor to the app, and who set up the accounts the app runs as. Editors work in the administration; the app sees only what is published and what its user may read.
Contents
From draft to app
editor saves a draft -> (approval workflow, if any) -> published version -> REST read (may be cached) -> app- The REST API reads the published version only.
- Approval and scheduled publishing are configured on the server; the app sees the item once it is published (Drafts and pending items, Workflows).
- Server and app caches add their delay (Caching on the server).
- What the app's user may read decides what appears at all (Permissions for app users).
Pages in this folder
| Page | Answers |
|---|---|
| Drafts, preview and publishing | What the app can see of drafts and versions, and how editors preview app screens |
| Permissions for app users | Integration users, roles, limitations, and auditing what the app does |
Related pages
- Publishing and versions
- Roles and policies
- Headless Exponential: preview and drafts
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.