Customer portal manual

Workflow IDs: CUS-001 registration, CUS-002 login, CUS-003 company selection, CUS-004 ledger
Approval: Approved baseline

Access

Customers use the party guard, not staff or provider login. Registration and login are public. Ledger, linked companies, email verification, and reviews require an active, unblocked party identity with an active company mapping.

Workflow

1. Open portal.register, enter name and mobile, accept customer terms, complete captcha when shown, and request OTP.
2. Submit the latest OTP and password confirmation. The mobile number becomes the global Padappai customer identity.
3. Later, use portal.login with password, OTP, or the configured Google flow.
4. At portal.company.select, choose an existing linked company or link an eligible company using the verified identity.
5. Open portal.ledger to view that company's ledger, invoices, work context, running balance, and eligible review actions.
6. Use Logout when finished, especially on a shared device.

Company-specific address, notes, invoices, and work records stay inside that company. Shared name, mobile, and email belong to the global customer identity.

Errors and recovery

• A blocked or inactive identity or mapping cannot sign in. Contact the relevant company or Padappai support.
• If the mobile already has active access, use login instead of creating a duplicate identity.
• If no company is available, return to company selection and use the supported linking flow.
• A party session entering a staff route must be denied and redirected to portal login when authentication is required.

Result and next step

Registration creates or reuses one party_users identity and one active party_user_accounts mapping. Company selection scopes the ledger session. Validate with CommonCustomerIdentityTest, PartyPortalOtpLoginTest, CustomerGoogleAuthTest, and portal browser UAT.