Registered individual provider manual
Workflow IDs: PRO-001 registration, PRO-002 application, PRO-003 operations
Approval: Approved baseline
Access
An individual provider uses a dedicated record in providers and the provider guard. This is not the same as a web user assigned the legacy provider_user company role. Provider accounts are restricted to provider routes and their own workspace.
Workflow
- Open
provider.register, provide a unique mobile, request OTP, set a password, and accept provider terms. - Complete mobile verification and the required provider application fields and documents at
provider.application.edit. - Verify email when required and submit the application.
- Wait for main-company approval or respond to requested changes.
- After approval, sign in through
provider.loginby password or OTP and useprovider.dashboard. - Maintain public listing details, availability, leads, appointments, and active work that belong to the provider workspace.
Errors and recovery
- Duplicate mobile: use provider login or the supported account recovery path; do not create another provider.
- Draft, pending, rejected, suspended, or blocked providers cannot operate as approved providers.
- Requested changes must be completed on the existing application.
- Provider access to staff administration or another workspace must return 403/404 without revealing data.
Result and next step
Registration creates a provider workspace, provider, listing, application, terms acceptance, and verified identity state as defined by the approved registration flow. Approval unlocks provider operations and public visibility remains subject to listing and availability rules. Validate with RegistrationFlowTest, ProviderManagementModuleTest, and provider-host UAT.