Organization Defaults & Navigation
Navigation Path: Sidebar → Experience Manager → Organization (the blue-bordered panel)
| Tab | Link | Permission |
|---|---|---|
| Customer & Account Pages | ?tab=org:pages | Manage Essential Customer Pages |
| Account Pages — Header/Footer | ?tab=org:account:chrome | Manage Org Level Global Settings for StoreFront |
| Site Map | ?tab=org:sitemap | any pages-view permission |
| Surface → Menu & Header/Footer | ?tab=org:<surface>:menu | that surface's view permission |
Whatever you set here is the default every project inherits — until that project saves an override of its own.
1. Menu & Header/Footer
Each of the four audience surfaces has its own editor at ?tab=org:storefront:menu, ?tab=org:marketing:menu, ?tab=org:servicedesk:menu and ?tab=org:papers:menu. They are the same editor with a different audience.
The pane opens with the precedence panel telling you what visitors currently see, then two sections: Menu, and Header & Footer.
1.1 The menu
This is a top-nav editor: the menu shown to that surface's customers. Items reorder with the ▲▼ buttons and delete with the bin.
Every item has a label and exactly one of three link kinds, chosen with the compact toggle on the right of the row:
| # | Kind | What you then pick | Resolves to |
|---|---|---|---|
| 1 | Org | An org page slug | A page under the org subdomain, e.g. support |
| 2 | Project | A project, then one of its pages | e.g. /oo/support/kb |
| 3 | URL | Any external address | Opens in a new tab |
Switching kind clears the fields that no longer apply, so a saved row never carries stale values from a previous kind.
Two things worth knowing:
- Sub-items make dropdowns. + Add sub-item nests a child under an item; the storefront renders those as a dropdown. The heading above them reads SUB-ITEMS (DROPDOWN).
Links to:is a live preview. Under each configured row the editor prints the exact path the item will resolve to —/oo/support/kb. Use it to catch a wrong project or page before you publish.
An empty menu shows a dashed placeholder telling you to press Add item.
1.2 Header & Footer
These are the chrome slots the page renderer injects into any page that doesn't declare its own:
| Slot | What it is | Default |
|---|---|---|
| Site header | Top bar on every page of the surface — logo, menu, cart, account. | On |
| Announcement bar | Thin notice strip above the header — promotions, shipping notes. | On |
| Site footer | Bottom area — copyright, social links, newsletter. | On |
| Floating widgets | Pinned to a screen corner. Add as many as you like: WhatsApp chat, Call us, floating cart, live chat (Tawk / Intercom / Drift / Crisp / Tidio), back-to-top, cookie consent. | None |
| Mobile fixed footer | Bottom nav bar on mobile only. Up to 5 slots — two left, a raised centre, two right — each linking to a project page, org page, category or external URL. | Off |
Each singleton slot expands into its own configuration form, plus a Hide on these pages multi-select: name page types there and the slot is not injected on them. Hiding the header on the checkout page is the usual reason.
Turning a slot off flips its auto-inject flag but keeps everything you configured. Toggle it back on and your settings are still there.
Press Save when you are done — a toast confirms, and the badge in the rail flips to Configured.
2. Account Pages — Header/Footer (tab=org:account:chrome)
This is the neutral header and footer used by shared account pages — login, profile, generic help — and it is the same editor as above.
This chrome is used when Primary Surface is set to Account in Landing & URLs. Set the Primary Surface to Storefront and account pages take the Storefront chrome instead, leaving whatever you configure here unused.
Keep it minimal — usually just your logo and a simple footer. A visitor signing in might be a shopper, a blog reader or a support user; a shop search bar and a promo banner help none of them. There is no project-level version of this tab.
3. Site Map (tab=org:sitemap)
A read-only inventory: the Organization block first, then one block per project with its Storefront, Marketing, Resolve and Papers trees.
- Each block is gated by its own permission and by your organization's packages — so the map shows what you are allowed to see, not necessarily everything that exists.
- Use it to answer "does this page already exist, and on which surface?" before creating a duplicate.