Batch Delete Members

Use Batch Delete only when selected member records should be removed from the library. This is a high-friction workflow by design because deleted members may affect history, reports, or later circulation/accounting records.

In Cloud setup, large batch deletes run through a batch job so Libcodesk WebApp and Standalone app can show live processed, deleted, failed, skipped, and remaining counts instead of waiting for one long request.

Screenshot To Add

Add screenshots of selected member rows, the Delete action in the selection toolbar, the confirmation popup, and the result summary.

Who Can Batch Delete

The action is visible only to staff roles with Batch Delete Members permission. If it is hidden, ask an admin to review Settings > Staff Roles.

Delete Selected Members

1. Open Member Manager > Members.
2. Search or filter to locate the records.
3. Select the member rows.
4. Click Delete in the selection toolbar.
5. Read the confirmation message.
6. Type confirm.
   • The word is not case-sensitive.
   • The Delete button stays disabled until the confirmation is typed.
7. Click Delete Members.

Libcodesk shows the result count after the batch finishes.

The popup is kept small on purpose. It should focus the user on the count, the confirmation word, and the final action.

Why Type "confirm"

Batch delete can remove many records at once. The confirmation step protects the library from accidental clicks, especially after selecting all filtered results.

Skipped And Protected Members

In V1, deletion is allowed where the member has no protected future dependency. As circulation, payments, invoices, history, and other operational modules are connected, members with important linked records can be skipped or blocked instead of deleted.

The batch result reports:

• Deleted/success count.
• Failed count.
• Skipped count.

Profile Images

When a member's linked account can be safely removed, Libcodesk also clears the member profile image where appropriate. Shared or still-linked accounts are protected.

Do And Don'ts

Do

• Filter carefully before selecting members.
• Read the selected count before typing confirm.
• Export or review data before deleting large groups.

Don't

• Don't batch delete expired members if you only need to block or deactivate them.
• Don't delete members with useful history unless the library policy allows it.
• Don't type confirm until you have checked the count and selection.

FAQ

Can deleted members be restored?

The current workflow is designed as a delete operation, not a soft undo. Use deactivate or blocked status when you want to keep records available.

Why were some members skipped?

Members can be skipped when they are protected by linked operational data or a validation rule. The result summary shows failed and skipped counts.

Can I delete all filtered members?

Yes, but only after explicitly selecting all filtered results and confirming the delete popup.

Should I delete inactive members?

Usually no. Inactive or blocked status is safer when the library may need history later.