Merging of User

Overview

The Analytics Merge process is triggered during a Zluri user merge operation. It ensures that dashboards, charts, ownership, and user roles are transferred from the source user to the target user within the analytics module.

Pre-Merge Validation

Before the merge begins, Zluri validates both users for analytics eligibility:

If the source user is not an analytics user, the merge step is skipped.
If the target user is not an analytics user, a new analytics profile is created automatically.

Merge Process

The merge runs asynchronously in the background and includes the following components:

Dashboard Migration

Item	Behavior
Ownership	Dashboards owned by the source user are reassigned to the target user, who receives full CRUD access.
Visibility Settings	Existing sharing or visibility settings are preserved.
Shared Dashboards	Dashboards shared with the source user remain visible to the target user, but ownership does not change.
Draft Dashboards	All drafts created by the source user are transferred and editable.
Last Updated	The "last updated by" field continues to show the source user. (Planned improvement.)

Charts Migration

Chart ownership is not transferred.
Target users cannot edit or delete charts owned by the source user.
Charts embedded in dashboards:
- Can be viewed by the target user
- Can be removed, but not edited
Ownership labels continue to reflect the source user.

Overview Dashboard Handling

Special rules apply for Overview Dashboards:

Scenario	Result
Both users have a personal Overview	Target user retains their own Overview
Target user has the default Zluri Overview, and source user has a personal Overview	Target user continues to see the default Overview; the source user’s is not migrated.

Role Management

During the merge, Zluri compares role priorities.
The higher priority role is assigned to the target user.

Source User Post-Merge

The source user is marked as inactive.
Inactive users are restricted from login or future access.

Updated 1 day ago