Skip to main content

Landing Pages & Public URL Routing

Navigation Path: Sidebar → Experience Manager → Overview → Landing & URLs (tab=overview:landing) Permission: visible to anyone who can open Experience Manager. Changing the Primary Surface needs Manage Org Level Global Settings for StoreFront.

Landing & URLs answers one question: where does each public URL actually send a visitor? It is read-only apart from a single setting — the Primary Surface — so you can explore it safely.

Figure 1 — The three rules the whole page rests on.

The three rules, spelled out:

  1. Every public page belongs to a surface — Storefront, Marketing, Resolve or Papers — and that is decided by the page's module, not by its URL. You cannot move a page to another surface by changing its slug.
  2. Shared account pages (login, profile, generic help) have no module of their own, so they borrow the Primary Surface's header and footer.
  3. The default root (<your-org>.dev-orbit.com/) serves the organization home page. A custom domain can point its root somewhere else — at a specific project or page. That target is the domain's landing.

1. Primary surface​

The Primary Surface does not choose your homepage

This is the most common misreading of this screen. Primary Surface decides which header and footer wrap the shared account pages — login, profile, generic help. It does not decide what the root URL / serves; the root always serves the organization home page (rule 3 above).

Figure 2 — The selected surface is filled in the brand colour and carries a check. Selection saves immediately.
FieldControlOptionsEffectNotes
Primary surfaceCard selector, single choiceStorefront · Marketing · Resolve · Papers · AccountSets which surface's chrome wraps login, profile and generic help pages.Saves immediately on click — there is no Save button. A toast confirms; on failure the previous choice is restored.

A surface card only appears if your organization subscribes to its package — Storefront needs pkg_e_commerce, Marketing pkg_mrkt_suite, Resolve pkg_orbit_resolve, Papers pkg_papers. Account is the neutral login/profile frame and needs no package, so it is always offered.

Without Manage Org Level Global Settings for StoreFront the cards render disabled and the pane says so in the subtitle.

Which one should you pick?

Pick the surface your visitors already recognise. If they arrive from a shop, Storefront; from a blog or campaign, Marketing; from a help centre, Resolve. Pick Account when you want the sign-in screen deliberately plain — no shop search, no promo bar — which is usually the right answer for a B2B portal.

2. Organization home​

Figure 3 — The org's public landing page, with a shortcut into its editor.

The organization's HOME page is what the bare org subdomain serves. Edit home page → jumps to the Customer & Account Pages tab; the pill on the right opens the live URL in a new tab.

3. Project public URLs​

Every project is listed with its URL prefix, and under it one card per audience surface showing whether that surface's home page is live.

Figure 4 — One row per project, one card per surface. Project names are blurred here.

There are no text status badges on this panel — the icons are the status:

IconMeaningWhat clicking it does
↗ on a green circleThe surface's home page is published and liveOpens the public page in a new tab
↗ in amber, no circleNot active — either the home page isn't published, or the project has no slugNothing; hover for the reason
✎ pencilYou hold that surface's edit permissionOpens the home page in Page Builder Studio
Manage pages →—Jumps to that project + surface's Pages tab in the hub

Each surface's home page is a specific page code — STORE_001 (Storefront), PULSE_HOME_001 (Marketing), HELP_001 (Resolve), PAPR_001 (Papers). If a surface card shows Not active, that page is the one to publish.

"Not active" is usually an unpublished page, not a broken setting

Hover the amber icon and it tells you which: "the home page is not published yet", or "Set a project slug first". A project with no slug cannot serve any public URL at all.

4. Custom domains & their landing​

Figure 5 — Where each custom domain's root actually points.

This panel is read-only; domains are added and verified under Settings → Custom Domains, reachable from the Manage domains → link in the card header.

ColumnMeaningExample
HostnameThe address visitors type.shop.agiledigest.com
TypeWhether the domain is org-level or project-level.organization / project
ProjectThe project it belongs to, or — for org-level.Alpha
Root serves (landing)What the domain's root resolves to — scope, plus a page slug if one is pinned. Shows default when nothing overrides it.project · /shop
StatusVerification / SSL state.active

If you have no custom domains, the card says so and reminds you that the org subdomain is being used with the organization home at its root.

The whole panel is hidden if you lack the domains permission.