Analytics When Users Are Merged

Overview

Zluri runs the Analytics Merge process during a user merge. It transfers dashboards, widgets, ownership, and user roles from the source user to the target user in the Analytics module.

Pre-Merge Validation

Before the merge begins, Zluri checks whether both users are analytics users:

If the source user isn't an analytics user, Zluri skips the merge step.
If the target user isn't an analytics user, Zluri creates a new analytics profile automatically.

Merge Process

The merge runs in the background and covers the following:

Dashboard Migration

Item	Behavior
Ownership	Zluri reassigns dashboards owned by the source user to the target user, who gets full access to create, edit, and delete.
Visibility Settings	Zluri keeps existing sharing and visibility settings.
Shared Dashboards	Dashboards shared with the source user remain visible to the target user, but ownership doesn't change.
Draft Dashboards	Zluri transfers all drafts created by the source user, and the target user can edit them.
Last Updated	The "last updated by" field continues to show the source user.

Widget Migration

Zluri doesn't transfer widget ownership.
The target user can't edit or delete widgets owned by the source user.
On dashboards, the target user can view and remove these widgets, but can't edit them.
Ownership labels continue to reflect the source user.

Overview Dashboard Handling

Scenario	Result
Both users have a personal Overview	The target user keeps their own Overview.
Target user has the Zluri Default Overview, and source user has a personal Overview	The target user keeps the Zluri Default Overview. The source user's Overview isn't migrated.

Role Management

During the merge, Zluri compares the two users' roles and assigns the higher-priority role to the target user.

Source User Post-Merge

The source user is marked as inactive.
Inactive users can't sign in or access Zluri.

Updated 18 minutes ago

Did this page help you?