PRDs: User Management

In recommended reading order, top-down. Status is synced from Plane on every build - the all-module view lives on the PRD Register.

#	ID	Name	Description	Surface	Status
1	PRD-AUTH-001	Authentication & account verification	Product requirements for authentication sign-up and the onboarding wizard on Client unified sign-in across Client, Sale and Back Office with cross-page blocking by role tier password change and self-service forgot-password over email or SMS OTP setting a password for an employee account created on someone's behalf identifier management after onboarding in Account Settings	ClientSale POSBack Office	Ready to dev
2	PRD-USR-001	User account & configuration	Product requirements for the user account a unique system-generated ID with soft delete multiple login identifiers that never collide across accounts a profile page with an avatar and language preference a status lifecycle (activate, deactivate, block, archive) driven by assigned permission and a default personal configuration set seeded at registration and self-managed by the user	ClientBack Office	Ready to dev
3	PRD-USR-002	User identifiers & configuration management	Product requirements for managing a user's login identifiers and personal configurations as first-class resources a multi-scheme identifier surface (username/email/phone) where adding one always binds to the caller and starts unverified, with a removal rule that keeps at least one verified email and one verified phone in place a per-user configuration surface grouped by code (system/table), readable right after sign-in before a merchant is chosen, with an auto-saving custom table view cloned from a base layout	Client	Ready to dev
4	PRD-EMP-001	Employee management	Product requirements for employee management on the Client app the staff table and merchant-scoped permissions form the Grant login toggle that controls sign-in and set-password mail guards blocking self-removal and removing an Owner	Client	Ready to dev
5	PRD-EMP-002	Merchant User Administration (Back Office)	Product requirements for the Back-Office merchant-user admin where our operations team manages the staff accounts of merchants across the platform create a merchant user, assign them to an organizer and merchant with roles, edit, lock/unlock moving toward multi-merchant assignment, reassignment, removal, and showing + manually toggling identifier verification state	Back Office	Ready to dev
6	PRD-OPS-001	Operations Staff & Access Administration (Back Office)	Product requirements for administering internal operations staff accounts from the Back Office a dedicated system-user list create internal accounts and assign the fixed Super Admin / Admin / Operator roles by hierarchy edit profiles, change status, trigger password resets every action is individually permission-gated	Back Office	Ready to dev