Configuration control
Configuration Studio
Inspect published effective state and make schema-governed tenant changes through Platform Core. Drafts never reach Runtime until an authorized publish succeeds.
Configuration context
Choose a customer context from Customer Workspace for structured editing. Legacy inspection remains available when no context is supplied.
Effective configuration
Published state only. Draft values remain local to the editor until persisted and published.
Schema-governed editor
Fields and constraints come from the canonical schema. Unknown extension properties remain intact.
Provide a schema version through a canonical context to inspect fields.
Tenant override draft
Save is a draft operation. Publish is a separate reviewed transition and never implies runtime activation.
Advanced base version
Values
Structured values are validated against the selected schema; secrets and arbitrary code are rejected.
Plan pin and adoption impact
This control is unavailable until the corresponding persisted adoption endpoint is exposed by Platform Core. No implicit latest-plan release is shown or applied.