---
title: "2.5.21 How to bulk-manage users on the User tab?"
description: "On the project User tab select multiple existing users and Assign (Checklist/RFI), Remove (Checklist/RFI), Edit (Role/Access/Permissions via side drawer) or Delete in bulk. Only changed fields apply; existing assignments stay; Associate (view-only) users skipped; sole-approver users skipped on delete."
url: https://help.digiqc.com/en/articles/266-2521-how-to-bulk-manage-users-on-the-user-tab
collection: "2.5 Web Setup, Monitoring, Tracking and Analysis"
updated: 2026-11-05
language: en
---

# 2.5.21 How to bulk-manage users on the User tab?

On the project User tab select multiple existing users and Assign (Checklist/RFI), Remove (Checklist/RFI), Edit (Role/Access/Permissions via side drawer) or Delete in bulk. Only changed fields apply; existing assignments stay; Associate (view-only) users skipped; sole-approver users skipped on delete.

### Overview

On a project's **User tab** you can **select several existing users at once** and manage them together — **assign** or **remove** their checklist/RFI access, **edit** their role/access/permissions, or **delete** them in bulk.

### 🧭 How to use

1.  Open the **project** → **User tab**.
    
2.  **Tick the users** you want (select multiple).
    
3.  A toolbar gives you **four actions** — **Assign, Remove, Edit, Delete:**
    

**Assign** — add access to the selected users:

-   **Checklist**
    
-   **RFI**
    

**Remove** — take away access from the selected users:

-   **Checklist**
    
-   **RFI**
    

**Edit** — opens a **side drawer** to update, for all selected users:

-   **Role**
    
-   **Access**
    
-   **Permissions**
    

**Delete** — deletes the selected users **in bulk.** If a selected user is a **sole approver**, that user is **skipped** (not deleted), so no approval is left without an approver.

### ⚠️ Important — how bulk changes behave

**For Edit (role / access / permissions):** Only the **fields you explicitly change** are applied. **Unselected fields stay unchanged** for each user. **Associate-role users are not affected** — they have view-only access.

**For Assign & Remove:** **Only the current changes are applied.** **Existing checklist assignments stay unchanged.** **Associate-role users are not affected** — they have view-only access.

### ❓ FAQ

**What do the four bulk actions do?** **Assign** adds checklist/RFI access · **Remove** takes checklist/RFI access away · **Edit** updates role/access/permissions · **Delete** removes the users.

### Will bulk Edit overwrite everything? **No —** only the fields you actually change **are applied; every other field stays as it was** for each user.

### Will I lose existing checklist assignments when I Assign or Remove? **No —** only the current change **is applied; existing assignments** stay unchanged.

**What happens if I bulk-delete a user who is the only approver?** That user is **skipped** — they won't be deleted, so approvals don't break. Reassign the approver first, then delete.

**Why aren't Associate users changing?** **Associate-role** users have **view-only** access, so bulk actions don't affect them.

**Can I edit just one user instead?** Yes — open that single user and edit as usual (see 2.5.16).

### 💡 Good to know

-   **Assign** and **Remove** each work on **Checklist** and **RFI** access.
    
-   **Edit** changes **Role, Access and Permissions** from one side drawer.
    
-   A **sole-approver** user is always **skipped** on bulk delete.
    
-   **Associate-role** users are always skipped — they're **view-only.**
    

### 🔗 Related articles

-   2.5.19 How to add or edit a project user (role, permissions & access)?
    
-   How to bulk-assign Checkers across checklists?
    
-   How to bulk-assign RFI Initiators across checklists?