Administration and access
Manage access, configuration and accountable changes.
On this page
Assign access by responsibility
System manages users and roles. Assign permissions by responsibility; read, write, publish and channel-scoped access are separate. The backend enforces every request.
Use the central configuration workspace
System → Configuration groups settings with independent scope and save/publication actions. Older installations may expose the same screens directly in navigation.
| Setting | Scope |
|---|---|
| Delivery & pickup | Selected store; immediate policy changes. |
| Delivery fee | Installation-wide; new checkout reviews. |
| Tax | Highest-priority active matching geographic rule. |
| Markets | One reviewed live market per installation. |
| Themes | Permitted channel assignments. |
| Assistant | New requests after configuration changes. |
Make a traceable administrative change
- Confirm the owning screen, store/channel and current state.
- Check required permissions and affected records.
- Enter a reason where requested.
- Save/publish that form; there is no cross-section bulk save.
- Verify the result and use audit history when investigating changes.
Resolve missing controls
- Missing links can indicate missing read permission.
- Disabled controls can indicate read-only access.
- Theme editing does not grant publication or assignment.
- Reload and reconcile stale revisions.
- Limit customer diagnostics and exports to authorized operators.