Deleting users
You can delete users from the Users section of the Management Console. Deleting an active or disabled user frees up a user entitlement that can be assigned to another user. Deleting a pending user removes the user record from the system, and they won't be able to register through the email invitation.
When a user is deleted from Qlik Cloud, such as when they leave an organization, any assets they own will no longer have an owner. This can lead to app and script reload failures and other access issues. Make sure to reassign ownership of spaces, apps, scripts, and data connections that the deleted user owned to resolve these issues.
What happens when you delete a user
Deleting a registered tenant user—a user with status Active or Disabled—has several implications beyond simply removing their entry from the Management Console. This section outlines the various aspects affected by the deletion, including their personal information, account status, and data ownership.
User information of deleted users
When a user is deleted, all personally identifiable information is removed. If a user is deleted while logged in to the tenant, their session is invalidated.
Deleted users who are part of an identity provider
When using your own identity provider, invalidating the user session doesn't prevent a deleted user from logging in again. If they attempt to log in after deletion, a new tenant user record is created, possibly leading to an automatic license assignment. To prevent this, remove the user from the identity provider. If you have configured your own identity provider, you can remove the user yourself.
Qlik Account of deleted users
Users with a Qlik Account cannot log in after deletion from the tenant unless they are invited again. Deleting a user from the tenant does not remove them from Qlik Account.
Consequences of deleting a user
- The user is no longer available in the tenant.
- API keys associated with the user are revoked.
- User entitlement becomes available for reassignment.
- Spaces, apps, scripts, and data connections must be reassigned to a new owner.
- If the user is the owner of a reload schedule, ownership must be reassigned or a new schedule created to prevent scheduled reload failures.
- Audit logs in the Management Console contain details of the deleted user event.
- Notifications and alerts owned by the user are also deleted from the system.
Reassigning ownership of spaces and resources
When a user is deleted, any spaces, apps, scripts, and data connections they owned will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Additionally, ensure that reload schedules have a new owner, or the reloads will fail.
Tenant admins can change space ownership, reassign ownership of apps, scripts, and data connections, and move these resources to other spaces. Analytics admins can perform these actions in shared and managed spaces, and data admins in data spaces.
Do the following:
-
In the Management Console, go to Spaces.
-
Use the filter to locate spaces owned by the deleted user.
-
Click
next to a space and select Change owner. -
Specify a new owner of the space and click Apply.
Repeat the process for apps, scripts, or data connections in the Content page. For more detailed instructions on changing ownership and managing reload schedules, see the following topics:
Deleting a user from the tenant
As a tenant admin, you can delete users from the tenant. You can only delete one user at a time, and you cannot delete yourself as a user. Make sure to remove the user from your identity provider, if applicable, and reassign any resources owned by the user before deletion.
Do the following:
-
In the Management Console, open the Users section.
-
In the row for the user to be deleted, click the
button to the far right. -
Select Delete to delete an existing user or Delete invitation to delete an invitee.
-
Confirm the deletion.