# Export settings

## Command Description

<figure><img src="/files/f6cd3MPn8OCYxnLmSabG" alt=""><figcaption></figcaption></figure>

The *Export settings* command helps users easily save the Be.Smart T4I settings into an XML or REG file, which can then be shared with other users / deployed to multiple workstations, so the process of configuring multiple T4I installations is greatly reduced.

### Export using the REG file

Only **ONE** file is exported, including user-specific settings (*General* section of the *Be.Smart T4I Settings*).

{% hint style="info" %}
This type of export is recommended for individual users who want to back up their settings.
{% endhint %}

### Export using the XML file

**TWO** files (XML and REG) are exported. The XML file contains all application settings except the user-specific settings, and the REG file contains the user-specific settings.&#x20;

{% hint style="info" %}
This type of export is recommended for use in corporate installations where it is undesirable to distribute purely individual user settings to other users. Also, the XML file can be stored in a network location easily accessible from all workstations where the T4I is installed.
{% endhint %}

## Command Location

All environments.

## Command Settings

This command has no settings.

## Workflow Overview

1. Run the command.
2. Select the file type to store settings.
3. Save the file.
4. (Use the file to import settings back to T4I.)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.besmart.software/t4i/commands-overview/be.smart-t4i/export-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.