sales.scaffolding.view allows the person into the product and can trigger local provisioning.Passing one layer does not bypass the next. Administrators should test both page visibility and API denial for unauthorised users.
| Access | Review |
|---|---|
| User login | Core identity active and correct product grant |
| Local role | Only permissions needed for the job |
| Branches | Only locations the user operates |
| Manager/Finance actions | Explicit approval/verification permissions |
| API token | Named owner, purpose, least privilege, expiry/rotation and revocation path |
| Deployment access | Separate from day-to-day application administration |
Review leavers immediately and privileged access periodically. Do not share accounts or machine tokens.
The system can contain customer identity/contact/address, prices, payments, refund evidence, user profiles and operational locations. Use production data only for approved operational purposes. Redact customer and credential data from logs, screenshots, tickets and documentation.
.env files, Supabase service keys, OAuth secrets or customer exports.Disable or revoke the affected user/token, preserve logs, identify actions and branch scope, rotate related credentials, assess customer/financial exposure, notify the responsible owner, correct permissions/data through supported workflows and record the incident outcome.