Roles and permissions

Shipora separates web staff (business users) from drivers. Drivers never get a web “role” in Settings → Users; they are invited under Settings → Drivers and use the mobile app.

Role summary

• Role: Owner · Access level: Full control: business profile, billing-related fields, integrations, locations, users, drivers, orders, routes, messaging, reports

• Role: Administrator · Access level: Same operational and configuration access as Owner for day-to-day work (locations, users, integrations, driver-app settings, reports). Creating a brand-new business at signup is Owner-oriented

• Role: Dispatch manager · Access level: Day-to-day dispatch: orders, routes, drivers, assignments, messaging/inbox. Cannot change organization settings, integrations, customer notification templates, or driver-app configuration JSON. Sensitive business fields (payment connection secrets, subscription details) are hidden

• Role: Driver · Access level: Mobile app only: on-duty locations, assigned orders/routes, status updates, POD, messages with dispatch

Permission matrix (practical)

• Capability: Live dispatch board · Owner: ✓ · Admin: ✓ · Dispatch manager: ✓ · Driver: —

• Capability: Create / edit / assign orders · Owner: ✓ · Admin: ✓ · Dispatch manager: ✓ · Driver: Scoped in app

• Capability: Build / optimize routes · Owner: ✓ · Admin: ✓ · Dispatch manager: ✓ · Driver: Scoped in app

• Capability: Invite / manage drivers · Owner: ✓ · Admin: ✓ · Dispatch manager: ✓ · Driver: —

• Capability: Assign drivers to locations · Owner: ✓ · Admin: ✓ · Dispatch manager: ✓ · Driver: —

• Capability: Create / edit locations · Owner: ✓ · Admin: ✓ · Dispatch manager: ✗ (view only) · Driver: View as needed

• Capability: Invite web users (Admin / Dispatch manager) · Owner: ✓ · Admin: ✓ · Dispatch manager: ✗ · Driver: —

• Capability: Business profile, branding, SLA defaults · Owner: ✓ · Admin: ✓ · Dispatch manager: ✗ · Driver: —

• Capability: Driver-app settings (POD, routes toggles, etc.) · Owner: ✓ · Admin: ✓ · Dispatch manager: ✗ · Driver: —

• Capability: Integrations (Square, Partner API keys, etc.) · Owner: ✓ · Admin: ✓ · Dispatch manager: ✗ · Driver: —

• Capability: Reports (performance, tips, etc.) · Owner: ✓ · Admin: ✓ · Dispatch manager: ✗ · Driver: —

• Capability: Messaging / inbox · Owner: ✓ · Admin: ✓ · Dispatch manager: ✓ · Driver: Own threads

• Capability: Billing / subscription fields · Owner: ✓ · Admin: ✓* · Dispatch manager: ✗ · Driver: —

\*Administrators generally share Owner-level settings access for operations; treat billing and plan changes as Owner-led unless your team policy says otherwise.

Choosing roles for your team

• One owner + dispatch managers — common for small teams: Owner owns Settings; managers run the board.

• Owner + administrators — when multiple people need to change locations, Square, branding, or reports.

• Don’t use Admin for every dispatcher — if someone only needs the board, give them Dispatch manager so Settings stay locked down.

Drivers and permissions

Drivers:

• Only see work for businesses/locations they’re part of

• Must go on duty (with location permissions) for live tracking

• Cannot change business settings or invite staff

Dispatch managers can invite and manage drivers, even though they cannot edit locations or integrations.

Related platform note

Shipora’s internal SaaS operator console (platform admins) is separate from your business roles. Your customers and drivers never use those roles.

Next steps

• Create your business and invite your team

• Locations and business settings