> ## 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.

# External dataset lookups

> Configure a keyword's external value lookup, scope it to document types, and test its query before use.

## Prerequisites

You need `keyword-configuration.manage`. Open **Admin settings → Keywords → External datasets**. Agree on the source values and supported query with the person maintaining that data source.

An external dataset supplies candidate values for **one keyword**. An [autofill set](/configuration/autofill-keyword-sets) fills several related keywords from a lookup. Use the mechanism that matches the indexing behavior you need.

## Configure the lookup

Choose **Add configuration**, select the keyword type, and choose a document type or **All document types**. Enter the lookup query using the editor's supported shape and supplied examples. This is a restricted query editor, not an arbitrary database-administration console.

The query can use the supported search-input placeholder shown in the UI. Use **Test Query** to inspect returned values before saving. Testing executes against the configured data source; use representative test values and check empty as well as matching input.

After saving, open an indexing form for the intended document type and verify that the keyword offers the expected values. Repeat for a type outside the intended scope when using a specific-type configuration.

<Frame caption="An external dataset configuration combines keyword scope, a constrained query, and a query test.">
  <img src="https://mintcdn.com/nobly/vtIE7VxmxD31SQoh/images/guides/external-datasets.png?fit=max&auto=format&n=vtIE7VxmxD31SQoh&q=85&s=3a37e8a4b3fa590f8cdd347d02953dbe" alt="An external dataset configuration combines keyword scope, a constrained query, and a query test." width="512" height="664" data-path="images/guides/external-datasets.png" />
</Frame>

## Maintain the configuration

Edit a configuration to change the query or scope. The keyword type is fixed when editing; create a separate configuration for another keyword. The list shows query and scope details, and the page provides **Audit History** and **Clear Cache** for investigation.

Deleting the lookup configuration removes that lookup behavior; it does not erase keyword values already stored on documents. Confirm whether the keyword should fall back to another configured value source before deleting it.

## Where to read next

<Card title="Client defaults and document actions" icon="gear" href="/client-administration/defaults-and-actions" horizontal>
  Configure shared upload behavior, distinguish personal overrides from enforced defaults, and expose document actions to selected groups.
</Card>

<Card title="Keyword behavior" icon="sliders" href="/configuration/keyword-behaviour" horizontal>
  Configure how keywords are presented and edited after their values and lookups are defined.
</Card>
