Public pages
Route: /org/ecom/customerpages · Permission: Browse & View Public Pages records
Module: org_ecom_customerpages — 6 permissions
1. What this screen is
The list of storefront pages — which exist, which are live, and where each one lives on the web. Building a page happens in Page Builder Studio; this screen decides what exists and whether customers can see it.
| This screen | Page Builder Studio | |
|---|---|---|
| Answers | What pages exist? Are they live? | What is on the page? |
| Permission | Browse & View Public Pages records · .publish | Build Public Pages |
The same component serves Storefront, Orbit Papers and Orbit Resolve, switching its permission prefix — Browse & View Public Pages records, Browse & view Papers customer-portal pages. and Browse & View Service Desk Pages — and its edit routes by context.
So this page looks identical in three places and is governed by three different permission sets. The route you arrived by decides which.
2. How a page becomes visible
A page whose slug is shop is not at /shop. It is at /<projectSlug>/shop — for the demo
tenant, /kitchen/shop. The unprefixed path returns the storefront's own 404,
"This page took a wrong turn".
system_pages.route_path records the pattern (/shop); the project slug in front is what makes
it a real address. Any link written without it will 404 even though the page is live.
3. The page list
Live versus Draft
A page is Live when it has published settings — that is, when someone has pressed publish at least once. Everything else is Draft.
Publishing snapshots the page. Later edits sit in the working copy until the next publish, so a page can read Live and still not show your changes.
4. Creating a page
| Field | Required | Notes |
|---|---|---|
| Page type | ✅ | From the system page catalogue |
| Name | ✅ | |
| URL slug | ✅ | Checked live |
The slug check reports one of four states:
| State | Message |
|---|---|
checking | checking… |
free | available |
taken | already used by another page in this project |
invalid | enter letters, numbers or hyphens |
Creation is blocked until the slug reads available.
5. Field reference — the six permissions
| Permission | Gates |
|---|---|
| Browse & View Public Pages records | The list |
| Create new Public Pages records | Creating |
| Edit existing Public Pages records | Editing metadata |
| Delete Existing Public Pages records | Deleting |
| Publish Pages to Live | Making it live |
| Build Public Pages | Opening Page Builder Studio |
Someone can be allowed to design a page without being allowed to put it in front of customers. If
that separation matters to you, grant builder widely and publish narrowly.
The Resolve exception
HELP_001 is a lightweight storefront support page. Where the organization subscribes to the full
Orbit Resolve, it is hidden from this list and tenants are directed to the dedicated Resolve
portal instead; otherwise it is shown with a clarifying badge.
6. The admin contract
| Prerequisite | Without it |
|---|---|
| Browse & View Public Pages records | No access |
| Publish Pages to Live | Pages can be built and never go live |
| A selected project | Pages are per project |
| A storefront domain | The pages have no public address |
7. Don't confuse this with…
| Thing | Where |
|---|---|
| Public pages (this page) | What exists and what is live |
| Page Builder Studio | What is on the page |
| Page blocks | Reusable fragments |
| Experience Manager | Menu, header and footer |
| Papers / Resolve pages | The same screen, different permission prefix |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| A live page 404s | The URL is missing the project slug |
| Edits are not visible | The page has not been re-published |
| Cannot publish | Missing Publish Pages to Live |
| Slug rejected | Taken by another page in this project, or has invalid characters |
HELP_001 missing | The org subscribes to Orbit Resolve |