Brand Guard. Per-app access control. One governance layer across 52 apps.
Purview controls not just what the configuration says, but who can change it and where. Brand Guard monitors compliance across every business unit. Per-app configuration access determines which team members can modify settings in which apps. Role scopes define the boundary — a location manager sees different controls than a regional director, who sees different controls than headquarters. Pre-configured access templates from the Blueprint store connect to any data point in any Calisto Pro app.
Brand compliance monitoring across every business unit and every app.
Brand Guard watches for brand violations across the platform — unauthorized naming, off-brand imagery, policy drift, configuration overrides that break headquarters standards. Violations surface in the review queue. Centralized brand enforcement without manual audits of every location.
Violation detection. Review queue. Resolution tracking.
Brand Guard scans configuration, content, and catalog entries across all purviews for compliance with brand standards. Violations are flagged and routed to the review queue. Each violation carries the purview, the app, the field, and the deviation. Resolution tracking from detection through correction. Headquarters sets the standard. Brand Guard monitors it.
Who can change what. In which app. At which business unit.
Per-app configuration access control. Define which team members and roles have permission to modify settings in each of the 52 apps, per purview. A location manager can configure terminal settings but not modify catalog definitions. A regional director can adjust policies across a purview group. Headquarters retains full configuration access. The access model is granular to app, purview, and role.
Per-app, per-purview, per-role
Location manager. Regional director. Headquarters. Each with a defined configuration boundary.
Role scopes define the configuration boundary for each level of the organization. Each scope determines which apps, which purviews, and which configuration surfaces a role can modify. The scope is the governance mechanism — not per-feature toggles, but a defined operational boundary per role.
One change from headquarters. Every business unit updated.
For multi-location operations, Purview is the headquarters control surface. A policy change at the top pushes through to every purview in the group. A catalog update propagates to every location. A brand standard revision takes effect across the platform. The single-system architecture means there is no sync delay, no integration, no re-entry. One change. Immediate propagation.
Purview groups. Shared operations. Inherited configuration.
Purview groups declare shared operations between co-located business units. A group of purviews inherits configuration from the group level — shared policies, shared catalog elements, shared brand standards. Per-purview overrides are possible where the group allows them. The hierarchy model supports a single location with multiple business types, a regional cluster of locations, or a national portfolio — each governed from one control surface.