Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt

Use this file to discover all available pages before exploring further.

Real-World Example

A Superadmin user can view data across creditors. A developer adds a bulk action and must make sure 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 Superadmin pages.
  • It should not perform silent bulk changes across creditors.
  • It should not expose payment or consumer data without a clear platform-support purpose.

Developer Notes

  • Use this page when adding or reviewing Superadmin features that can affect more than one creditor.
  • This is a developer guardrail page, not an end-user training page.
  • routes/superadmin.php
  • app/View/Composers/SidebarComposer.php
  • app/Livewire/Creditor/ManageCreditors
  • app/Livewire/Creditor/ManageConsumers
  • app/Livewire/SuperAdmin
Last modified on May 25, 2026