Users wanting to use BookIt must be approved and assigned an appropriate role by an Admin.
Where a company has Single Sign On integration, users should self register by simply trying to login, rather than an Fleet Admin adding them in advance.
If enabled, adding BookIt users will add and sync drivers to MyEROAD, reducing double-handling user creation.
Application workflow
- Users within an company are given the address to the BookIt system where they're invited to register.
- They're sent a verification email, they click the embedded email link, and they await being verified by the Admin.
- Verification could mean the Admin assigns the user roles, states and groups.
Verified
Verified users attempted to log into BookIt, were onboarded by the automatic registration process, and have verified their email addresses.
This page also allows Admins to add new Bookers.
Add new Users to your system:
- Users > Verified > Add. A panel slides out.
- Fill in the details.
- Add.
The user is added to the system, is emailed a verification, and the entry is passed into the Unconfirmed email state.
More (...) tools
- Quick verify: Forces a verification on behalf of the user (not recommended).
- Edit: Update a user's details.
- User login history: A time-based look at a user's interactions with BookIt
- History - changes by user: A changelog of a user's actions.
- History changes to user: A changelog of changes made to a user account, either by an Admin or the user.
- Delete
- Show email history: Audit log of the email history with the user, usually tracking booking confirmation/alert messages.
EROAD Support: BookIt <--> MyEROAD Driver integrationMyEROAD driver integration for BookIt aims to reduce double-handling driver/user management between BookIt and MyEROAD. When enabled, Booker accounts are sent, created, and updated to MyEROAD as Drivers. Bookers will also be able manage their own PINs. This section is included so that customers may understand more about how BookIt will sync with MyEROAD. Setting up the integration is largely handled by EROAD Support from an accepted work order. Only those with the Organisation Admin roles may add new users. Enabling MyEROAD driver integration on BookIt
New Booker creationWhen a new Booker is created, BookIt checks to see if a matching MyEROAD driver exists. If so they are matched; if not, a new driver record is created. (see below). Customers using this integration should cease duplicating BookIt-only driver profiles in MyEROAD. Syncing with MyEROAD These tools are not available to customers. When enabled, Support agents will sync appropriate features of MyEROAD with BookIt. Verified Bookers will have their existing MyEROAD Driver records matched, or have new MyEROAD Driver accounts created and populated with appropriate details. Once two profiles are matched, any future changes made to the Booker will automatically be applied to the MyEROAD Driver profile. This matching process occurs daily at midnight, or if the Sync drivers button is pushed. If entering a licence is disabled in BookIt, MyEROAD will populate this new Driver with a dummy licence entry (licences are a mandatory Driver field in MyEROAD). The trigger for matching and driver creation is the user being set to Verified. It doesn't matter if single-sign-on or auto verification has been enabled. How Bookers and Drivers are matched
If a new Driver is created, Bookers will be prompted to set a Driver PIN on the next BookIt login. This matching process is only important if a customer already has Drivers in MyEROAD when BookIt synchronisation is enabled. If a customer is new and has no Drivers, they’re matched automatically when they are created by BookIt as new Drivers. All MyEROAD Drivers must have a Fleet and PIN assigned to them on creation, so EROAD Support agents will assign a default MyEROAD Fleet for your BookIt instance, based on your recommendation. A Booker cannot see, select, nor change their Fleet. Driver AliasMyEROAD requires a Driver's username and alias to be unique to the organisation.
Driver PINsSet this number in the Organisation > Integrations > EROAD Drivers > EROAD Driver PIN length field. Bookers can change their PIN later in their profile settings. Bookers cannot see their existing PIN; only update it. Administrators cannot see or update a user’s PIN. Changes to a Driver PIN do not update immediately on the Ehubo. It typically takes minutes but can take hours to update – and will not update if the Ehubo does not have cellular coverage (e.g. in an underground parking building). Bookers should not update their PIN just prior to taking a vehicle. Deactivating and Reactivating UsersWhen a user is disabled in BookIt the associated MyEROAD driver will be deactivated. If this user is then re-enabled in BookIt the associated MyEROAD driver will also be reactivated. When a user is deleted in BookIt the associated MyEROAD driver will be deactivated. If this user is re-created, you will see an error message on the Drivers list, and you will need to manually reactivate the Driver in MyEROAD. Error statesIf an error has occurred when creating a driver in MyEROAD, an error icon will be visible next to the user on the Verified Users list. Detailed error information is available when you hover on the icon. Detailed Supported Use CasesNew Booker added by admin, licence not required
New user added by admin, licence required
New user self-sign up
New Booker self-sign up with auto-verification enabled
Existing Booker edits PIN, or other profile information
Other details such as name, email address and phone will also be synced. licence is currently unsupported. Existing Booker is edited by AdminAssuming the integration is enabled, and the user previously exists:
LimitationsThe EROAD API does not support updating licence information. BookIt will send the latest information, but this will not be updated in MyEROAD. |
User roles
Bookers
Booker: Can view the welcome page, make bookings for themselves, book seats in other vehicles, and view their past and future bookings.
Multibranch Booker: An addon that gives the ability to book vehicles from any branch.
On Behalf Booker: An addon that gives the ability to book on behalf of other users. Under manage bookings, they can view and manage the bookings they've made for themselves, and those they've made for others.
Administrators
Booking Approver: May approve bookings of vehicles that have been assigned an Approval flow. (If a branch has no Booking Approver, bookings will skip assigned Approval flows.)
Booking Admin: Has the ability to view and manage all bookings for a branch, but none of the additional features a Branch Admin has.
Branch Admin: Has most of the reporting and functionality of an Organisation Admin but is restricted only to their own branch. For example, they can add users, or enable vehicles, but only to their own branch.
Under Manage Settings branch admin can only access Welcome message, Accessories, Groups and Locations - and can only create or modify these for ones that only exist in their branch(s). Branch admins can only see and approve pending users if "Allow users to add themselves to this branch at sign up" is enabled for their branch.
Multibranch Admin: Ability to be a branch admin for multiple branches.
Organisation Admin: Highest level of access - can access everything and is the only user that can create branches. Is the only user that can:
- Change organisation settings
- Create a branch
- Set or edit a user agreement
- Create or edit booking policies
- Create or edit booking reasons