> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/circulation-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/circulation-user-manual/11-utilities/import-menu/auth-import.md).

# Auth Import

This utility loads authentication control history from a flat file. Authentication history is used to track subscriber digital access, for AAM and other purposes. This utility can be used as an alternative to iServices Authentication.

#### To use this option:

* Select `Import | Auth Import` to display the Authentication Import window.

![](https://1417315899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ToZXx8io0JJXNBRcPOt%2Fuploads%2FpGbb1cVHnR0xytFhWnFt%2FAuthentication%20Import.png?alt=media\&token=6e98e202-d9bc-4c95-987f-f759a6725853)

* In the File Format field, enter the name of the file map created for this option. The “AuthImport” file mapping usage is used for this import. See Appendix B for the possible data elements.
* In the File Name field, enter the name of the file to import. This file must exist in the `/dti/exchange/cm` folder.
* Select Edit to view the records to be imported or Commit to import the records.
* Click OK to run the utility.

{% hint style="info" %}
**Note:** 

*If the AuthControl data element is not included in the specified file, you will be prompted to enter a valid authentication control ID before continuing with the import.*
{% endhint %}


---

# 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://docs.navigaglobal.com/circulation-user-manual/11-utilities/import-menu/auth-import.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.