Overview
Profile Types are used by the Zipline system to distinguish different kinds of workers from a compliance, reporting and permissions perspective.
This article explains:
New and old behaviour
How to change profile types in Zipline for customers with an integration.
How to manage workers with multiple profile types (e.g. volunteer and employee).
New and old behaviour
If you've been using Zipline for a while, you will be familiar with the requirement for phone numbers to be unique within the platform. The intention behind this design was to ensure that workers had a consistent, predictable and unique URL they could access to upload compliance evidence and receive notifications through.
As the platform matured, this limitation meant that certain employment scenarios, such as an Employee performing Volunteer work or an individual who had worked as a contractor and was wanting to apply for a permanent role were operationally difficult to support or required significant offline process to maintain compliance.
New behaviour which is currently rolling out, relaxes this to allow sharing phone numbers across different profile types. While the phone number must be unique within profile types (for example, two employees cannot share the same phone number), the phone number can now be shared across different profile types, such as allowing an Employee to also have a Volunteer profile.
Please contact us if you would like to have the new behaviour enabled.
How to change profile types in Zipline for customers with an integration
Should a worker be changing profile type (e.g. Volunteer moving to Employee), you will want to create a new application to collect any missing compliance, similar to internal role changes as outlined in this article.
You should also set up a flow that can be used for these purposes. An ideal setup would be a flow with no checks in it, with the exception of an "Ad-Hoc Admin" check which is optional and admin only. This flow, for example, could be named "Z. Volunteer | Ad-Hoc Check".
Instructions
Create the new application (via integration or manually), keeping the profile type the same as the worker's current profile type. For example, if a worker is currently a Volunteer, create an application under the Volunteer profile type. Use the Ad Hoc flow you have set up, and ensure the role and location match the worker's current role and location.
You can opt to NOT send notify the worker when creating the application, if desired.
Once the application is created, manually identity the checks you need to add for the worker's new role, and add these to the application manually.
Once the application is approved, checks for their new role will be moved to their Profile.
When your HRIS updates their role and profile type, they will be compliant for their new role.
Creating an additional profile with a different type for a worker
If you have an employee who is also going to start volunteering, or a student who is applying for a permanent role (for example), you will need to create a new application for the new profile type.
Instructions
From the Applications screen, create a new Application
Enter the phone number of the worker
The existing profile should be found
On the next screen, change the profile type (for example from Student -> Employee)
Fill in all other information
The new application will be created, and the worker will have two profiles in the system
How to manage profile with dual profile types (e.g. volunteer and employee).
Should a worker have two or more profile types at the same time, you will need to prioritise one profile type to send Zipline via your HRIS integration, as employee numbers must be unique in Zipline. This may, for example, mean that you prioritise sending the Employee profile type if a person is also a Volunteer, by placing the employee number on the Employee profile. A worker can have multiple profiles sharing the same phone number and/or email address, however compliance data is not shared between them.
Implications & Workarounds
For HRIS
As only one employee number is supported, this will mean that any checks required for the non-primary profile type(s) will not be sent to your HRIS (if you are integrating this). You will therefore need to put in place a process to report on this edge-case scenario. Some guidance:
You may wish to create a filter to report on profile with multiple profile types via your HRIS or internal reporting.
Should you wish to run additional checks for these profile in Zipline, you can do so via an application with ad-hoc checks.
Role and location changes for additional profiles will not be synchronised by the HRIS, as workers are matched by employee numbers. This means that changes to the role, location, manager etc of the additional profiles will require updating Zipline manually. For example, if a worker is an employee and also volunteers, and the nature of their volunteering changes, the volunteer profile will need to be updated using the Zipline Management Portal.
For workers
As each profile is independent of each other, checks that are common across both types (eg Police Check) will be monitored separately and will both notify the worker when they are due
We recommend copying the check data from the primary profile to additional profiles for any common requirements rather than permanently exempting to ensure renewal dates are consistent for reporting
