Real-World Example
A Super Admin user can view data across creditors. Any bulk action must be scoped carefully so it cannot accidentally update consumers, payments, merchant settings, or communications for the wrong creditor.
Visual Flow
How It Should Work
- It should treat cross-creditor access as high risk by default.
- It should require explicit scoping for creditor, consumer, merchant, payment, communication, and membership records.
- It should use confirmation, auditability, and focused tests for bulk or destructive changes.
How It Should Not Work
- It should not reuse creditor-scoped assumptions blindly in Super Admin pages.
- It should not perform silent bulk changes across creditors.
- It should not expose payment or consumer data without a clear platform-support purpose.
Last modified on July 30, 2026
