Skip to main content

Real-World Example

A new mail response operator joins the team. Maya opens Manage Users, creates the user with name, email, password, and phone, and the new user can log into EcoMail Hub / EcoPortal. Later, Maya edits the user’s phone number or deletes the user when access should be removed.

Visual Flow

How It Should Work

  • It should let authorized EcoMail Hub users create, edit, search, and delete EcoMail Hub users.
  • It should keep email addresses unique across active EcoMail Hub users.
  • It should mark newly created EcoMail Hub users as email verified.
  • It should show the currently logged-in user clearly in the list.

How It Should Not Work

  • It should not create creditor, consumer, or Super Admin users from this page.
  • It should not allow duplicate active email addresses.
  • It should not leave removed users with active portal access.

API Mapping

The list and detail responses include is_current_user, actions.can_edit, and actions.can_delete so the frontend can render the current-user badge and hide self-edit/self-delete actions.

Developer Notes

  • The list sorts the current user first when no explicit sort column is selected.
  • The create form requires password rules; edit does not require a password.
  • app/Livewire/ConsumerResponseManager/ManageUsers/ListPage.php
  • app/Livewire/ConsumerResponseManager/ManageUsers/Create.php
  • app/Livewire/ConsumerResponseManager/ManageUsers/Edit.php
  • app/Livewire/ConsumerResponseManager/Forms/UserForm.php
  • app/Services/ConsumerResponseManagerService.php
Last modified on July 5, 2026