For provider teams
A team member works for the provider, not for Provzo.
A provider running a small outfit issues a private code. Their workers join under it. Jobs are still booked with the provider; the team member is who turns up.
Joining
Private codes, not public ones.
- The provider generates a code. It is random, expires after 30 days, and can be replaced at any time.
- Codes cannot be listed or searched. Knowing one exact code is the only way to use it.
- Joining creates a request. Only the provider who issued the code can approve it.
- The worker sees the decision as it happens, and can withdraw the request while it is pending.
Access
Only the jobs assigned to them.
- A team member sees a booking only after the provider assigns them to it — never the provider’s whole queue.
- They can mark a job on the way, started, or completed. Their travel location publishes only while they are on the way.
- They cannot accept, decline, cancel or reassign a job, and cannot change a price.
- Membership does not establish employment by Provzo, and does not prove identity, qualification, licensing or background checks.
Removing access
Immediate, and it cleans up after itself.
- The provider removes access and the member immediately loses the ability to read assigned bookings.
- Any active job assigned to that member returns to the provider, and the customer-facing "who is coming" details and travel location are cleared with it.
- If that cleanup is interrupted, the provider can retry it — removing access does not strand stale details on a customer’s screen.