Skip to main content

Best Practices for Batch User Deletion

1. Use Cases

When reducing the number of users during renewal and triggering license user count limit validation prompts, or when there are a large number of accounts to be cleaned up, batch user cleanup is required.

2. Overview

This article provides the fastest and most reliable user cleanup methods under different user creation methods.

step1 Determine the number and types of accounts that need to be cleaned up

step2 Identify which accounts can be deleted and transfer account permissions

step3 When cleaning up accounts created through account synchronization, you need to delete them in the account data source and turn off the [Disable Deletion] switch in the account synchronization interface;

When cleaning up accounts created through other methods, you can use interface functions or public api.

3. Specific Cases

3.1 Prerequisites

When the license user count limit validation prompt is triggered (as shown in the figure below), please first confirm which accounts are causing the limit to be exceeded.

p1.png

In Administrator Settings - About - Version Information, by comparing the existing/upper limit of valid users and the existing/upper limit of valid editing users, you can understand which types of accounts mainly need to be cleaned up.

p2(1).png

Additionally, you need to confirm in advance which accounts can be deleted and transfer account permissions to the handover person.

p3(1).png

3.2 Account Creation Methods

3.2.1 Account Synchronization Creation

If the accounts you want to clean up are created through account synchronization,

Correct operation: Please delete the accounts that need to be deleted in the data source of account synchronization, do not delete the accounts that need to be retained, then trigger dataset update and synchronize to the account synchronization dataset.

If the [Disable Deletion] switch is enabled, accounts deleted in account synchronization will be disabled, and you need to turn off this switch and synchronize again.

p4(1).png

Incorrect operation: After clearing the account synchronization dataset and synchronizing users that need to be retained again, all accounts created through account synchronization will be deleted or disabled, and rebuilding will also create new accounts instead of restarting the previous accounts. So proceed with caution.

3.2.2 Other Creation Methods

If the accounts you want to clean up are created through manual creation, Excel batch creation, LDAP association creation, single sign-on association creation, or API creation,

If the quantity is small, it can be completed through interface operations,

p5(1).png

If the quantity is large, you can clean up accounts through public api calls, /public-api/users/delete.

Call method: https://docs.guandata.com/article/1/user-api.html#nav-6-H2