Project Overrides & Surface Management
Navigation Path: Sidebar → Experience Manager → Project (the amber-bordered panel) Project context: set with the inline project picker in that panel's own header.
The Project section is where one project departs from the organization defaults. Anything you save here beats the blue panel's version — for this project only.
1. Choosing the project
The picker sits in the PROJECT panel header, not in the global top bar. Until you pick one, every project tab tells you to select a project and shows nothing else, and the project-scope badges in the rail stay blank.
| Control | Type | Options | Effect |
|---|---|---|---|
| Project picker | Compact dropdown, shows each project's logo | Every project in the organization | Switches the project context for all project tabs at once. The choice is shared with the rest of the portal. |
2. What a project surface adds
Both scopes have Menu & Header/Footer. Project scope adds two more tabs — and, for three surfaces, a link-out.
| Tab | Storefront | Marketing | Resolve | Papers |
|---|---|---|---|---|
| Brand — logo, colours, name for this project | ✅ | ✅ | ✅ | ✅ |
| Menu & Header/Footer | ✅ | ✅ | ✅ | ✅ |
| Pages | ✅ | ✅ | ✅ | ✅ |
| Link-out ↗ | Store Settings | — | Configurations | Configurations |
Home page codes, if you need to find the surface's landing page: STORE_001 (Storefront), PULSE_HOME_001 (Marketing), HELP_001 (Resolve), PAPR_001 (Papers).
There is no per-surface Brand tab under Organization — organization branding is the single Brand Identity tab shared by every surface. The per-surface Brand tab appears only once you are in project scope, and it is what overrides that shared identity for this project's visitors.
Where each surface's Brand is written. Marketing and Resolve keep a per-surface branding block in portal settings. Storefront is different: its editor reads and writes the project's ecommerce store settings directly, because that is the single source of truth the storefront itself reads.
You never leave Experience Manager for any of them — all four Brand editors are embedded in the hub.
The link-out tabs
Three tabs carry an ↗ icon and open a full editor on its own route, because those editors need the whole viewport:
| Tab | Opens | Permission |
|---|---|---|
| Storefront → Store Settings | /org/ecom/storesettings | Menu Listing of Store Front settings |
| Resolve → Configurations | /org/resolve/settings | Manage Helpdesk Settings or Allows viewing Integration Telemetry charts and settings |
| Papers → Configurations | /org/papers/project-settings | Papers module limits, defaults, integrations and signature-provider toggles. |
A Back to Experience Manager bar appears at the top of those pages and returns you to the exact tab you left.
3. Creating project pages (tab=project:<surface>:pages)
Both paths end in the same editor. The difference is what is on the canvas when you arrive.
Path A — Create with wizard
A right-hand drawer (680px), not a modal, with five steps across the top: Basics → Layout → Sections → Header & footer → SEO.
| Step | What you choose |
|---|---|
| Basics | Page type (searchable — it decides which starting layouts and blocks are offered), page name, and URL slug. The slug is normalised as you type and checked live against the project for availability. |
| Layout | A starter template from the gallery, or a blank page. |
| Sections | Toggle the template's optional sections off before the page is built. |
| Header & footer | Inherit the shared chrome, or give this page its own. |
| SEO | Meta title and description, plus Personalize copy with AI. |
If you chose a blank page — or a template that declares no optional sections — the wizard strikes Sections through in the rail and steps over it. Nothing is wrong; there is simply nothing to toggle.
The SEO step's AI toggle runs the PAGE_COPY_FILL AI utility to rewrite the template's placeholder copy in your organization's voice. If that utility is not enabled for your organization the toggle is disabled and says so. It is best-effort: if the call fails, the page is still created with the template's original copy.
Path B — Create custom page
| Field | Control | Notes |
|---|---|---|
| Page type | Searchable select | Drives the builder palette. Any type still gives you header, footer, rich text and the rest. |
| Name | Text input | The page's display title. |
| URL slug | Text input | One segment, under /<project>/<slug>. Letters, numbers and hyphens only — the drawer says so under the field. |
Then Create & open builder. There is no starting-layout gallery on this path — that is the wizard's job. You arrive at an empty canvas.
4. After the page exists
Click Edit on any page row to open the Page Builder Studio and start assembling blocks.