Choose a role based on the work the person needs to do. Owners manage the business and team access; schedulers organise work; team members work with assigned Visits. Verify the actual signed-in view before handing over responsibility, because a role label alone does not explain every workflow.
Match responsibilities to the current controls
This table summarises the product routes and actions checked for these guides. Plan availability and an active business membership also apply. It is a practical workflow summary, not a claim that every internal field is visible to every person in a role.
| Task | Owner | Scheduler | Team member |
|---|---|---|---|
| Invite/manage team access | Yes, subject to plan/seats | No owner invitation controls | No |
| Create/reschedule work and change assignments | Yes | Yes | No management action |
| Review booking/change requests | Yes | Yes | No |
| Import Customer CSV | Yes | Yes | No |
| Update assigned Visit progress | Yes | Yes | Assigned Visits |
| Edit working Availability | Yes | Yes | View own arrangement |
Check the assigned person's working view
A team member should be assigned to the Visit they need to open and update. Customer and Job administration pages have broader management boundaries, so do not assume they can browse the whole business to find an instruction.
Put necessary attendance detail into the fields available in the Visit workflow. Test the handover with the person's role and a clearly labelled practice scenario before relying on it for a customer booking.
Review access when responsibilities change
If someone begins scheduling for others, decide whether the scheduler role is appropriate instead of sharing an owner's credentials. If someone stops working with the business, use the owner's team-management process to review access and future assignments.
Keep notification preferences separate from scheduling authority. A person receiving an email about a Visit does not by itself establish permission to edit every related business record.
Sources and scope
An original operational guide from the Daylane team at Blu Mint Digital. Scenarios, durations and message wording are illustrative planning examples, not customer results or industry benchmarks. Product references were checked against the Daylane implementation on 5 September 2026. Adapt the workflow to your service, customer agreements and working conditions.
How we write and maintain our guides. Free templates and planning tools.
