Real-World Example
A platform operator opens ABC Collections from Manage Accounts to review revenue, consumer-account performance, membership plan details, eco profile information, and company contacts. The view supports platform support work without editing unrelated creditor data.
Visual Flow
How It Should Work
- It should show platform-level creditor context needed for support.
- It should return summary revenue metrics for membership, consumer payments, automated communications, platform campaigns, EcoLetters, and notice responses.
- It should return performance metrics for total active accounts, settlements, plans, successful payments, disputes, and no-pay accounts.
- It should return the eco profile, plan, and contacts tabs from one company-scoped response.
- It should preserve cross-creditor boundaries even for Super Admin users.
- It should keep membership, merchant, user, and consumer impact visible without returning list-page action metadata.
How It Should Not Work
- It should not return row-level list actions in the detail response.
- It should not make broad platform edits look like normal creditor self-service changes.
- It should not update a different creditor because of route or selection mistakes.
- It should not hide whether a value is creditor-owned or platform-owned.
Last modified on July 30, 2026
