Team & permissions
Managers and drivers have different needs. Accounts, roles and permissions let you tailor available actions and visible data to your organisation.
In the backoffice
Your team's access
A team member's roles and permissions.
What you can do
An organisation that respects everyone's responsibilities.
Define both what a member sees and what they can do.
Separate roles and actions
Assign a role to the account and adjust permissions. Depending on the module, viewing, creating, editing, deleting or confirming a payment are separate actions. A colleague can view information without being able to edit it.
- Reusable roles
- Permissions by module and action
- Member-specific adjustments
The right data scope
Define the account's visibility scope. Lists, records and dashboards respect the members it can access. Notification preferences do not grant additional access to records.
- Own or extended scope depending on role
- Filters consistent with access rights
- Notifications and access managed separately
A catalogue for each member
Assign a selection of products to the member, or the whole catalogue with exclusions. Product visibility and member assignment are complementary settings for organising what can be booked.
- Product selection
- All products with exclusions
- Catalogue visibility taken into account
Coordinate the office and logistics
Organise driver relationships and delegation between members. Delivery and collection groups retain their organisation. Available histories help trace actions on records.
- Driver members
- Delegation and logistics groups
- Change history
The workflow
Define access, then check its scope
Define
Identify who views, prepares or edits records.
Configure
Assign roles, permissions and visibility scope.
Check
Check the workflow available to each account type.
Module scope
Features included
- Member accounts
- Roles and permissions by module
- Visibility scopes
- View or edit access
- Driver organisation
- Operation history depending on the screen
Points to clarify
Can editing records be restricted?
Yes. Permissions distinguish available actions according to module and role.
Can several members be organised?
The backoffice supports members and their scopes. The demo lets you check how this organisation fits yours.
Connections to other modules
To then organise the people responsible for routes
Personalised demo
Let's map out your team's access.
We walk through this module with your needs and questions.