Security and operational controls
Understand access and operational security controls.
On this page
Identity and authorization
Customer requests are identity- and ownership-scoped. Admin requests require sessions and current permissions. Read, write, publish and channel access are independent.
Server checks enforce access; identifiers and navigation visibility grant no authority.
Request and secret handling
- Protected admin mutations enforce request/origin safeguards.
- Authentication throttling follows trusted ingress configuration.
- Store secrets server-side; exclude them from bundles, logs and exports.
- Delegate scoped assistant capabilities without general commerce credentials.
- Restrict customer diagnostics and exports.
Public and private content boundaries
Public documents require approved identity and active/published records. Private drafts are excluded; theme previews require admin sessions.
Indexing preferences and robots directives do not replace access control.
Operate the controls
- Assign named users and review roles as responsibilities change.
- Manage and rotate secrets through approved deployment controls.
- Review audit evidence and restrict diagnostic permissions.
- Monitor readiness, dependencies and failed jobs.
- Back up data and test restoration.
- Verify public-edge controls and client isolation.