> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/sources/sources-catalog/import-crm-users/users-file-importer.md).

# Users file importer

### File structure <a href="#data-importcrm-filestructure" id="data-importcrm-filestructure"></a>

* One line per user
* Header on the file is needed for the matching
* Encoding: utf8
* The variable can not be calculated. It must be one line, one variable
* PGP or GPG key encryption are not supported. Files must be unencrypted before import.

Variables :

* it must be the same name of data variable (Variables are in uppercase, they will transcribe automatically in lowercase)
* You can add new variables. Don't forget to define them in DataCommander variable interface
* The CRM variables should be prefixed with "person." and custom variables by "person.custom."

### File example

{% file src="/files/7xBQTvh9yjcvHp68NjG9" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.commandersact.com/features/sources/sources-catalog/import-crm-users/users-file-importer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.