In some cases, it is possible for a worker record to exist in the system without an Organization or Role assigned. When this happens, the worker may not be visible or searchable within Mosaic, even though the record exists behind the scenes.
This article explains why this can occur, what impact it has, and how to avoid it.
Why this happens
During worker creation, assigning an Organization and Role is an important step. If both of these are intentionally left unassigned, the worker record can still be created successfully. However, Mosaic relies on this information to display and manage workers within the application.
Because this scenario requires deliberate user action, it does not occur during standard workflows.
Impact
The worker record exists securely within the system.
The worker will not appear in Mosaic until an Organization and Role are assigned.
There is no negative impact to system performance, data integrity, or other users.
This behavior has been reviewed by our development team and is working as designed.
Current Position
At this time, we are not planning to change this behavior. Our development efforts are focused on broader improvements to Mosaic, and this scenario does not present a direct risk or system issue.
We appreciate customers raising edge cases like this, as they help inform future decisions and platform improvements.
Recommended Best Practice
To avoid visibility issues:
Always ensure that a worker is assigned both an Organization and a Role during creation.
Share this guidance with users who are responsible for managing or creating worker records.
If a worker cannot be found in Mosaic, checking whether these fields have been assigned is a good first step.
If you believe a worker is missing from Mosaic or need assistance updating an existing worker record, please contact support for help.