Some drivers work for more than one company, for example a self-employed driver who drives for two companies that both use PTV Axylog. This article explains how to set up such a driver so they can be assigned to trips in two PTV Axylog contexts.
How it works
For data privacy reasons, drivers are not shared between contexts automatically. Instead, both contexts create the same carrier with the same VAT number, and that carrier contains only this one driver.
- The VAT number connects the two contexts.
- The link becomes active once the carrier has been activated in both contexts with the identical VAT number.
- The company name and master data code can differ between the two contexts. Only the VAT number has to match.
Before you start
- The driver's phone has PTV Axylog App V1.22.0 (Build 259) or later installed.
- You know the carrier's VAT number. If the carrier doesn't have one, agree on your own unique code with the other context and use that instead.
Part 1: Set up the carrier and driver in the first context
The context contributor in the first context does all of the following.
Step 1: Create the carrier master data
- Open the Master data view and select + Create.
- Set the master data type to Carrier.
- In General information, enter the carrier's VAT number. If the carrier doesn't have one, enter your own unique code instead. Write this number down, because the second context needs it in Part 2.
- Fill in the master data code and the company name. Both are required. We recommend a company name that contains the driver's name.
- Select Save changes. The detail page opens in edit mode.
- Optionally, fill in the other cards, such as address details. These aren't needed for this setup.
Step 2: Link the carrier master data to the current context
- Go to Users | Management > Companies active in the context and click Manage.
- Enter the same VAT number or code you used in Step 1, then click Next. Don't use the Generate unique code button here.
- Fill in the company details: name, country, time zone and language.
- Tick Is a carrier company.
- Click Choose, select the carrier master data from Step 1, and click Save.
Step 3: Create the driver
- Go to Users | Management > Mobile App users.
- Create the driver as a new user.
- Assign the driver to the carrier from Step 1.
Important: Assign only this one driver to this carrier. Don't add other drivers to it.
Part 2: Set up the same carrier and driver in the second context
The context contributor in the second context repeats Part 1, using the same VAT number or code as the first context.
Step 1: Create the carrier master data
Create the carrier master data as described in Part 1, Step 1. Enter the same VAT number or code as in the first context. The company name and master data code can be the same or different.
Step 2: Link the carrier master data to the current context
Link the carrier master data to the second context as described in Part 1, Step 2, using the same VAT number or code.
Step 3: Create the driver
- Go to Users | Management > Mobile App users.
- Create the driver as a new user and enter the driver's phone number. Several fields are filled in automatically.
- Complete any remaining fields and assign the driver to the carrier from Step 1.
The driver can now be assigned to trips in both contexts.
Part 3: What the driver does
Once the driver is available in both contexts, a pop-up appears every time they reactivate their phone. In the pop-up, the driver selects which context they're working in that day.
We recommend that the driver finishes their trip and work in the current context before switching to the other one.
Checklist
If the driver can't be assigned in both contexts, check the following:
- The driver's app is V1.22.0 (Build 259) or later.
- The VAT number or code is exactly identical in both contexts, both in the carrier master data and under Companies active in the context.
- The Generate unique code button was not used when linking the company.
- Is a carrier company is ticked in both contexts.
- The carrier contains only this one driver, in both contexts.
Comments
0 comments
Article is closed for comments.