Overview
Profile Types are used by the Zipline system to distinguish different kinds of workers from a compliance, reporting and permissions perspective.
Currently, only one Profile Type is supported at any one time. This article explains:
How to change profile types in Zipline for customers with an integration.
How to manage profile with dual profile types (e.g. volunteer and employee).
How to change profile types in Zipline for customers with an integration
Should a worker by 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.
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 only one profile type at a time is currently supported. This may, for example, mean that you prioritise sending the Employee profile type if a person is also a Volunteer.
Implications & Workarounds
As only one profile type is supported, this will mean that any checks required for the non-primary profile type(s) will not be monitored in Zipline. You will therefore need to put in place a process to monitor compliance for 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.
You may wish to then log the additional checks required for each person and their non-primary profile types in a separate source (e.g. a spreadsheet), as well as expiry dates.
Should you wish to run additional checks for these profile in Zipline, you can do so via an application with ad-hoc checks.