Team Management & Permissions

25+ granular permissions, rota visibility controls, leave approvals, and bulk cover flow.

25+ PermissionsLeave WorkflowBulk Cover
iOSAndroidWeb Dashboard
Screenshot coming soon

When you hire your first walker or your fifth groomer, Wagify scales with you. Invite team members by email — they get their own login, their own view of the calendar, and access to exactly the features you choose.

Permissions are granular. "Can view clients but not edit them." "Can see bookings but not financials." "Can sell products but not modify the catalogue." "Can view the full rota or only their own assignments." Twenty-five individual permissions cover every screen, every action, and every data type — and they're enforced at the database level, not just hidden in the UI.

Role presets give you sensible defaults — a "Senior Walker" sees more than a "Junior Walker" — but every permission can be overridden per person. Need to give someone temporary access to invoicing while your office manager is on holiday? Set an override with an expiry date. When the date passes, their access quietly reverts to their base role. No manual cleanup.

Booking assignment lets you allocate specific jobs to specific team members. They see their assignments on their calendar, get notified of changes, and can only access the client and pet data relevant to their bookings (unless you grant broader access). The rota view shows who's doing what at a glance — team members with the full-rota permission see everyone; others see only themselves. One toggle controls the difference.

When someone takes leave, the workflow is built in. Team members submit a request from their own calendar. You see pending requests with a dashboard badge, review them with the dates and reason, and approve or deny with an optional note. The team member is notified either way. On approval, any bookings that would be affected are automatically flagged — a "3 bookings need cover" badge appears on your dashboard. Tap it and a bulk cover screen opens with one row per affected booking and a picker on each row. Assign cover for all of them at once, or handle some now and leave the rest flagged for later. Cross-pool reassignment is allowed with a warning. Nothing falls through the cracks.

Key highlights

  • 25+ granular permissions enforced at database level — including full rota vs own-assignments visibility
  • Role presets with per-person overrides and auto-expiry for temporary access
  • Leave request workflow — submit, approve/deny, notify, auto-flag affected bookings
  • Bulk cover screen — one row per booking, picker per row, commit all at once

Available on

iOSAndroidWeb Dashboard

Use this with launch access

Get started

No plan tiers during launch