[P11] Configure a Site

Summary

The operator adjusts how a site behaves: portal address, sign-in offer, defaults for parts, store options. Settings can come from part properties, the event page, the settings screen or the hosting environment, with a clear rule for which wins.

Actor & Context

Actor: Operator
Frequency: Occasional
Precondition: The site is onboarded
Entry point: The site’s settings screen, the hosting configuration, or remote operation (P12)

Main Flow

  1. The operator opens the settings screen; each setting shows its current value and where it comes from.

  2. The operator changes a setting; the site applies it at once.

  3. Settings fixed by the hosting environment are shown as fixed and cannot be changed on the screen.

Alternative Flows

  • AF-1: Secret: shown only as set or not set; never displayed or exported.

Acceptance Criteria

  • Precedence is part, event page, settings screen, with hosting values fixed (PS-CF-01)

  • Secrets are never shown or logged (PS-CF-02)

API Surface

The calls below are named by purpose; their exact form is defined in the public site design.

Call Purpose

Site: read effective configuration

Without secrets

Out of Scope

  • Theme and layout settings of the CMS

Design Anchors

Notes

This use case is independent of the CMS. How each implementation realises it is documented with that implementation.