Real-World Example
A platform operator opens Jane’s consumer record while helping a creditor support case. The portal should show enough account, payment, and communication history to investigate without exposing unrelated consumers.
Visual Flow
How It Should Work
- It should help platform users investigate consumer account issues across creditors when authorized.
- It should preserve payment history, schedule state, and communication context.
- It should apply the same safety rules as creditor support actions when edits are available.
How It Should Not Work
- It should not expose consumer details to non-Super Admin users.
- It should not let support changes bypass payment, status, or communication rules.
- It should not mix records from different consumers with similar identifying details.
Developer Notes
- Super Admin consumer detail can include soft-deleted records through route behavior.
- Use this page as the platform-support version of creditor consumer profile docs.
routes/superadmin.phpapp/Livewire/Creditor/ManageConsumers/ViewPage.phpapp/Livewire/Creditor/ManageConsumers/ListPage.php
Last modified on May 26, 2026
