Overview
How SiteWall policies work
Understand scope, inheritance, effective state, prerequisites, and the safety boundaries of enforcement.
Last reviewed September 12, 2026
Control overview
Control is SiteWall’s layered policy workflow. Review observed behavior, choose a global default, use provider policies for service-wide decisions, and use resource policies for the narrowest exceptions. Validate the effective state and website behavior after every consequential change.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Policy hierarchy | Read the configured value at Global, Provider, and Resource layers and identify the resolved effective state. Apply the narrowest approved change, validate critical journeys, and retain the previous state for recovery. |
| Observation-to-decision flow | Trace the relationship from the loading resource to the observed destination or capability. Confirm required service endpoints and regional behavior in representative journeys before restricting access. |
| Enforcement boundary | Review enforcement boundary in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
Policy prerequisites and safety
Before enforcing a policy, confirm the project and domain, active installation and supported enforcement path, representative observations, business and technical owners, essential journeys, test environment, change window, monitoring plan, and exact rollback state.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Policies in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Record the effective policy
Inspect Global, Provider, and Resource layers. Capture both the configured value at each layer and the resolved effective state, together with the critical journeys and current working behavior.
- 3.
Supported path
Read the configured value at Global, Provider, and Resource layers and identify the resolved effective state. Apply the narrowest approved change, validate critical journeys, and retain the previous state for recovery.
- 4.
Rollback
Preserve the failing state, test the most local dependency first, and make one reversible change at a time. Reproduce the original journey after each check and stop when the evidence points to a different layer.
- 5.
Validate the effective result
Reload the policy view and confirm the resolved effective state. Exercise every affected critical journey and verify required browser access and network requests before expanding the change.
- 6.
Document approval and recovery
Record the policy layer, previous and new effective values, reason, approver, validation journeys, result, monitoring window, and exact recovery action.
Policy inheritance
SiteWall resolves policy from Global to Provider to Resource. Inherit keeps the upstream decision; Allow or Block creates an explicit decision at the current layer. When behavior is unexpected, inspect the resource first, then its provider, then the global default to find the effective source.