Bulk Operations
The /tags/bulk page lets you assign or remove tags across many entities at once. Use it when you need to retag a lot of items quickly — for example, after restructuring vocabularies, importing legacy data, or running a yearly clean-up.
What you can do
- Bulk assign — pick a set of entities and a set of tags; everything matched gets the tags.
- Bulk remove — strip a tag from every entity that currently has it, optionally filtered by entity type.
- Bulk move — move tags between vocabularies (preserves assignments).
Required permissions
Bulk operations require:
tag-assignment:createfor bulk assigntag-assignment:deletefor bulk removetag:managefor bulk move
Filters and selection
You select which entities are touched by combining:
- Entity type (
File,Project,Task, ...). - Existing tag filter (e.g. "all entities currently tagged High").
- Workspace scope (defaults to current workspace).
- Optional context match (
workspaceId,userId,projectId).
The page shows a count before you confirm, so you always see exactly how many entities will be affected.
Atomicity
Bulk operations run as single transactions in the backend — either every change applies, or none of them do. If a partial failure happens (e.g. permission denied on some rows), the whole operation is rolled back and you see an error with details.
Audit trail
Every bulk operation emits one audit event with the count and the filters used, plus per-entity assignment events. You can replay the trail under /tags/:tagId → History.
Tips
- Always preview the affected count before confirming.
- For very large operations (>10,000 entities), schedule the job during low-traffic hours.
- If you're undoing a previous bulk apply, use bulk remove with the same tag — don't try to delete the tag itself, that destroys assignments permanently.