Docs/Experience & Studio

Branding, Studio components and publishing roles

Screens 7.4, 7.5 and 7.6 — branding and layout bounds, the Studio component catalog, and designer vs publisher authority.

PEEK Platform Administrator

/peek/customers/tenant-a/7-5

Live walkthrough · Branding, Studio components and publishing roles

Branding, Studio components and publishing roles — /peek/customers/tenant-a/7-4 — /peek/customers/tenant-a/7-4

Branding, Studio components and publishing roles — /peek/customers/tenant-a/7-6 — /peek/customers/tenant-a/7-6

7.4 Branding & layout boundaries — approved logo formats, colors, layout bounds and required governance notices. Branding can never hide restriction text, source markings, identity scope, safety notices or focus indication.
7.5 Component catalog — versioned component manifests with data/action contracts and declared capability dependencies. Components cannot add arbitrary scripts, connectors or permissions; a missing peer disables only dependent components.
7.6 Studio roles — separates designer from publisher. Routine within-bound publishing happens in the agency app; a designer without publish permission calling the publication API is denied.

7.4 · Branding & Layout Boundaries

Set permitted branding and layout changes. Open it at /peek/customers/tenant-a/7-4 (any tenant ID you can access works in place of tenant-a). The primary action is Publish branding boundaries, which requires branding_policy.publish.

How 7.4 works

1. Set allowed logo assets, colors, layout bounds and required governance notices
2. Preview changes

Screen 7.4 contract

Fields shown: Logo rules, colors, navigation limits, accessibility requirements
Primary action: Publish branding boundaries
Required capability: branding_policy.publish
Validation: Assets must use approved formats; critical markings, identity scope and safety notices cannot be hidden.
Successful outcome: Within-bound agency branding is available without overriding access or accessibility requirements.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.7.4.action (acceptance test AT-UI-7.4)
Requirements: R02, R06, R19, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-7.4

Boundary — Agency branding cannot hide restrictions, source markings or audit-relevant notices.

Rejected even if the browser allows it — Choose branding that removes focus indication or obscures restriction text; reject publication.

7.5 · Studio Component Catalog & Boundaries

Govern reusable page components. Open it at /peek/customers/tenant-a/7-5 (any tenant ID you can access works in place of tenant-a). The primary action is Release component version, which requires component_catalog.publish.

How 7.5 works

1. Version component manifests with data/action contracts, optional SI needs and required capabilities

Screen 7.5 contract

Fields shown: Component manifest, data contract, SI dependency, allowed actions
Primary action: Release component version
Required capability: component_catalog.publish
Validation: Components cannot introduce arbitrary scripts, new connectors or permissions. Missing peers disable only dependent components.
Successful outcome: Catalog shows compatible components; standard Core experiences remain usable without Studio.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.7.5.action (acceptance test AT-UI-7.5)
Requirements: R02, R06, R19, R28, R32, R38, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-7.5

Boundary — Declare component capability dependencies. Standard pages, Core intake and basic branding remain available without Studio.

Rejected even if the browser allows it — Install a component with an undeclared source or tool action; reject it.

7.6 · Studio Roles & Publishing Authority

Separate page design from agency publication. Open it at /peek/customers/tenant-a/7-6 (any tenant ID you can access works in place of tenant-a). The primary action is Publish role boundary, which requires experience_role.publish.

How 7.6 works

1. Define designer, publisher, scope and agency review separation for experience changes

Screen 7.6 contract

Fields shown: Designer, publisher, scope, review rule, capability boundary
Primary action: Publish role boundary
Required capability: experience_role.publish
Validation: Routine within-bound publishing stays in the agency app; PEEK technical review applies to platform capability changes.
Successful outcome: Agency receives clear design and publication capabilities without new business-data rights.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.7.6.action (acceptance test AT-UI-7.6)
Requirements: R02, R05, R06, R19, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-7.6

Boundary — Routine within-bound agency publishing occurs in the customer portal.

Rejected even if the browser allows it — A designer without publish permission invokes the publication API; deny it.

Related guides

Experience overview, personas and navigation

Screens 7.1, 7.2 and 7.3 — Core experience and Studio entitlement, persona layout recommendations and module visibility rules.

Experience preview, release and rollback

Screens 7.7 and 7.8 — preview the agency experience with synthetic identities, then release or roll back platform components.