đ Note: This information was missed from the original Mosaic 25.2.0.0 release notes. We're sorry for the delay in sharing it with you.
If you use Access Evo, Mosaic creates workers from the Access Evo Members tab using a default organisation, two roles, and a virtual worker. Mosaic added these automatically during the upgrade to Mosaic 25.2.0.0.
If you don't currently use Access Evo, you don't use these roles yet and can continue to manage your workers as usual. You must not amend the ACCESS EVO organisation, the ACCESS_EVO role, or the ACCESS_EVO_WEB role, even if you're not currently using Access Evo.
ACCESS EVO organisation: New workers created through Access Evo are added to the ACCESS EVO organisation.
ACCESS_EVO role: New workers are given the primary role ACCESS_EVO, and this role is ended on the previous day. This allows a Mosaic administrator to immediately assign the new worker to the correct organisation and role.
ACCESS_EVO_WEB role: This role is used by the system when creating new workers and has been granted the User Management (USERMGT) system function.
ACCESS_EVO_WEB worker: A worker with the system_user_id ACCESS_EVO_WEB, role ACCESS_EVO_WEB, and organisation ACCESS EVO has been added. The system uses this worker when creating new workers or processing other system-to-system updates from Access Evo.
â ď¸ Important: You must not modify this configuration, as it's required for Access Evo to function correctly.
đ Note: If you use Access Evo, you can still create workers in the Mosaic Workers screen, but you can't amend the Access Identity email on their worker record. This means these workers can't be linked to an Access Identity account in Access Evo. They can still function as virtual workers, or as workers for use from the Mosaic WebAPI.