Every CRM eventually needs a change that is too big to do record by record: a salesperson leaves, a region is reorganised, or a list from last year’s event needs a label. Bulk editing makes that a few minutes of work. It also makes it possible to overwrite the owner of every open deal in the company with one click. Pomio CRM recommends treating bulk rights as a deliberate decision rather than a default: who may do it, on which records, and for which fields.
Why bulk edits need a rule
A normal edit touches one record, and the person making it can see the result straight away. A bulk edit touches whatever the current filter happens to include. If the filter is slightly wrong, the change spreads quietly into deals, companies and contacts that nobody meant to touch. Because the records still look plausible, the error tends to surface only when forecasts, targets or commission no longer add up. A short rule prevents most of that without slowing down the people who really need the feature.
Match bulk rights to scope
The simplest approach is to let bulk rights follow the scope people already have. A sales rep may bulk-edit their own records, for example to add a label to their own prospects. A sales manager may bulk-edit within the team, for example to redistribute deals when someone is on leave. Changes that cut across the whole organisation, such as renaming a label everywhere, belong with an administrator, and in a small business that should be one or two people, as explained in how many administrators a CRM should have.
Decide which fields may change in bulk
Not every field carries the same risk. Owner, labels and archive status are good candidates for bulk changes, because they are often needed in groups and easy to check. Amounts, stages and expected close dates are better changed one deal at a time, because each one says something about a specific customer and feeds the forecast. Deleting in bulk is best avoided altogether: archiving instead of deleting keeps the history and makes a mistake reversible. When the reason for a bulk change is an owner leaving, follow the same steps as reassigning open deals when an owner leaves.
Filter, count, then change
Before running a bulk action, check how many records the filter returns and whether that number makes sense. If you expect around thirty deals and the list shows three hundred, stop. Look at a few records at the top and bottom of the selection. For large changes, export the selection first so you have a copy of the original values, and write down in a note or team message why the change was made. Merging duplicates is a related but separate case with its own risks; see who should be allowed to merge duplicate CRM records.
Check the result and know how to undo it
After the change, open a handful of affected records and confirm they look as intended. If something went wrong, the fastest route back is a clear history: an audit trail of who changed what shows when the change happened and who made it, archived records can be restored, and an export taken beforehand gives you the original values. Agree in advance who to contact when a bulk change goes wrong, so the fix starts the same day.