> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt
> Use this file to discover all available pages before exploring further.

# Mass value editing

> Preview and replace a stored alphanumeric keyword value across a selected document scope, then monitor the background job.

## Prerequisites

You need `keyword-configuration.manage`. Open **Admin settings → Keywords → Mass value editing**. This operation changes stored metadata on existing documents; use it for an agreed correction, not to change a keyword's definition.

## Check the impact

Choose an **alphanumeric** keyword type, enter the current stored value and its replacement, and select document types. Leaving document types empty covers all types to which the keyword is assigned.

Choose **Check impact** and review the number of affected documents. Changing the keyword type, current value, or document-type scope invalidates the preview; run the impact check again. The screen does not permit a replacement with no matches, an empty replacement, or a replacement identical to the current value.

If document auto-names depend on the keyword, review the option to recompute those names. Keyword values can also drive security rules, folder grouping, external integrations, and reporting, so include those owners in the change review where relevant.

<Frame caption="Choose the keyword and document scope, enter the old and new values, then check impact before replacing.">
  <img src="https://mintcdn.com/nobly/vtIE7VxmxD31SQoh/images/guides/mass-values.png?fit=max&auto=format&n=vtIE7VxmxD31SQoh&q=85&s=16772fba3200e0db18bb42a58ed32103" alt="Choose the keyword and document scope, enter the old and new values, then check impact before replacing." width="1200" height="650" data-path="images/guides/mass-values.png" />
</Frame>

## Replace and monitor

After checking the exact scope and values, choose the replacement action and confirm. The update runs as a batched background job, with normal keyword transaction-log entries for updated documents. Inspect the job monitor on the same page; an accepted request is not a completed replacement.

Another replacement cannot be started while the current job is running. Review failures and sample resulting documents before repeating the operation.

## Recovery considerations

There is no general undo implied by this page. Replacing the new value back with the old value could also affect documents that already had the new value before this job. Retain the approved scope and impact information, and investigate partial results before planning a corrective update.

## Where to read next

<Card title="External dataset lookups" icon="sliders" href="/configuration/external-datasets" horizontal>
  Configure a keyword's external value lookup, scope it to document types, and test its query before use.
</Card>

<Card title="Permissions and access" icon="shield-halved" href="/permissions/introduction" horizontal>
  Review the account and content-access rules affected by configuration changes.
</Card>
