> For the complete documentation index, see [llms.txt](https://documentation.ardoq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ardoq.com/integrations/basics/configurations.md).

# Configurations

Configurations save your mappings in the tabular importer and let you easily re-apply them to new imports.

A configuration is the entire set of mapping of columns in the tabular importer to specific Ardoq fields, types, and references.

Any time you perform an import in Ardoq through an integration — whether through an Excel import or any other integration — you will be creating a configuration.

Configurations are the basis for creating scheduled imports. Once you've created and saved a configuration, a scheduled import will apply that configuration to any new data pulled from an integration. In other words, once a certain column is configured with a given Ardoq data type, all new data appearing in that column will be treated as that same data type based on the configuration.

## During the Import <a href="#h_a1ec119265" id="h_a1ec119265"></a>

When performing an import in Ardoq, you are encouraged to save your configuration as you map your table in case you want to save your progress and return to the work later. This can be done at any time using the Save configuration button in the top-right corner:

<div data-with-frame="true"><figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FmCMUDxz1GdOArQgXQKUz%2Fimage.png?alt=media&amp;token=e2ea2de4-c956-4d81-9c08-0db091614596" alt=""><figcaption></figcaption></figure></div>

Finally, as the last step of the import process, you'll be prompted to create a configuration of your entire mapping if you haven't made one already. Though you can discard your configuration, especially if you've made a one-off import, they are useful to have in case you want to save yourself the effort of re-creating mappings.

## Post-Import Configurations <a href="#h_a98aa4ae57" id="h_a98aa4ae57"></a>

You can find your integration-specific configuration in the Configurations tab for that integration. The **View details** button provides a summary of which tables are mapped to which workspaces, though it does not display individual column-level mappings. If you need to replicate this configuration in another integration setup, you can use the **Copy to** feature.

<div data-with-frame="true"><figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FICmUHae8VQmFhUbAkyI7%2Fimage.png?alt=media&amp;token=bd2b5807-f34c-4783-a734-b72d9663340e" alt=""><figcaption></figcaption></figure></div>

## Technical Details <a href="#h_19f9794a10" id="h_19f9794a10"></a>

Under the hood, each configuration is represented by a JSON file that specified the connection between Ardoq data types and the columns in the tabular importer.

Each integrations stores its own set of configurations and they cannot be applied across integrations. That is, a configuration for Excel cannot be re-used for a ServiceNow integration.

Additionally, when exporting a workspace to Excel from the Asset Manager, Ardoq will automatically add a new worksheet containing the configuration for the workspace's components and references. When importing the Excel file back into Ardoq, the importer will ask you if you want to automatically apply the embedded configuration:

<div data-with-frame="true"><figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FWTN5KO9SiVHi9wbjuiL4%2Fimage.png?alt=media&amp;token=9481ad3f-d24c-4786-93ab-3c30a0df9df9" alt=""><figcaption></figcaption></figure></div>

Configurations embedded in exported Excel files are also capable of creating new workspaces and should be manually adjusted before