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

> ## Agent Instructions
> Cognite Data Fusion (CDF) is an industrial DataOps platform. English is the canonical locale unless the reader asks for another.
> The documentation catalog is https://docs.cognite.com/llms.txt. Subgroup indexes live under https://docs.cognite.com/_llms/. Each published page has a Markdown twin at the same path with a .md suffix.
> REST APIs: calendar version 20230101 is stable. Preview versions are 20230101-beta and 20230101-alpha, for clients already on a preview API. Concept pages are under /api-reference/concepts/<version>/. Versioned requests use the Cdf-Version header. The default SDK is the Python SDK (cognite-sdk). JavaScript and TypeScript projects use the JavaScript SDK.
> Topic hubs: platform overview /cdf/index.md; data modeling /cdf/dm/index.md; data integration /cdf/integration/index.md; access /cdf/access/index.md; Cognite Toolkit /cdf/deploy/cdf_toolkit/index.md; REST quickstart /dev/quickstart.md; Python SDK /dev/sdks/python/index.md; Atlas AI /cdf/atlas_ai/concepts/index.md; Flows apps /cdf/flows/index.md; Aura UI /cdf/aura/index.md; MCP and IDE setup /dev/guides/ide_ai_integration.md.

# Configuration

> Create and retrieve immutable configuration revisions for an integration in Cognite Data Fusion (CDF).

Configuration lets you manage versioned settings for an integration. Each change creates a new revision, which preserves a history of which configuration was active. Extractors fetch the active revision at startup. Each check-in response notifies the extractor of newer revisions.

Integration configuration is a revisioned document associated with an integration. Every time you push a new configuration, CDF stores it as a new revision rather than overwriting the previous one. This lets you audit configuration changes and know exactly which revision an extractor was running at any point in time.

## Managing configuration revisions

You create a new configuration revision when you want to change how an extractor behaves. You can list all revisions for an integration to review its configuration history, or retrieve a specific revision, the revision that was active at a timestamp you specify, or the revision an extractor currently reports using.

<Info>
  Configuration revisions are immutable once created. To change behavior, create a new revision rather than editing an old one.
</Info>

## Key operations

* **Create revision**: Push a new configuration revision for an integration.
* **List revisions**: Review the configuration history for an integration.
* **Retrieve**: Get a specific revision, or the revision that was active at a timestamp you specify.

Versioned configuration ties together what an extractor is running with the task and error data it reports, so you can correlate behavior changes with configuration changes.