> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/examples.md).

# Examples

The following examples help explain how to setup the "Details" section of the **Data Location** screen depending on you situation, when you select **Network Share** as the location type.

* [Example 1: Single user, same network location for all folders](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/examples.md)
* [Example 2: Single user, different network locations for folders](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/examples.md)
* [Example 3: Different users, different network locations for folders](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/examples.md)

#### Example 1: Single user, same network location for all folders

1. Enter details in the three fields in the top part of the screen, (i.e. the **Username** and **Password** of the user, and the source file name into the **File name** field).

   No other fields need completing as all the folders are on the same network location.

   **Note:** If you don't know the source file name, or you want to import more than one source file, you can use wildcard characters. Refer to [Wildcard characters](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/wildcard-characters.md).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-32cbf3f463c160453503029a394615067e896e94%2Fdatalocationtab_networkshare_example1.png?alt=media)

#### Example 2: Single user, different network locations for folders

1. Enter details in the three fields in the top part of the screen, (i.e. the **Username** and **Password** of the user, and the source file name into the **File name** field).
2. Enter the individual folder paths into the **Source folder**, **Completed folder**, **Failed folder** and **Image folder** fields.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0627f5fee7150b2fe77fb5e0ac88b93819e16328%2Fdatalocationtab_networkshare_example2.png?alt=media)

   **Note:** As a valid folder path is entered into each of these fields, the **Logon with** checkbox directly below it becomes enabled. These can be ignored as the **Username** and **Password** of the single user has already been entered.

#### Example 3: Different users, different network locations for folders

**Scenario 1:**

In this scenario:

* User A will access the Source folder and the Completed folder
* User B will access the Failed folder
* User C will access the Image folder

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e350c4a2acb9b5d452fa704a74d586381c7d0084%2Fdatalocationtab_networkshare_example3.png?alt=media)

1. Enter User A's **Username** and **Password** into the fields in the top part of the screen.

   **Note:** Alternatively, these fields can be left blank, and User A's **Username** and **Password** can be entered into the appropriate fields directly below the **Source folder** and **Completed folder** fields.
2. Enter the source file name into the **File name** field.
3. Enter the folder paths into the **Source folder** and **Completed folder** fields.

   As a valid folder path is entered into each of these fields, the **Logon with** checkbox directly below it becomes enabled. These can be ignored as User A's **Username** and **Password** have already been entered in the top part of the screen.
4. Enter the failed folder path in the **Failed folder** field.
5. Check the **Logon with** checkbox directly below the **Failed folder** field, and enter User B's **Username** and **Password**.
6. Enter the image folder path in the **Image folder** field.
7. Check the **Logon with** checkbox directly below the **Image folder** field, and enter User C's **Username** and **Password**.

**Scenario 2:**

In this scenario:

* User A will access the **Source folder**
* User B will access the **Completed folder**
* User C will access the **Failed folder**
* User D will access the **Image folder**

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8ac68a46d788b007b95c58e6ae5e42f0de7f4b4d%2Fdatalocationtab_networkshare_example4.png?alt=media)

1. Enter the source file name into the **File name** field.
2. Enter the source folder path in the **Source folder** field.
3. Check the **Logon with** checkbox directly below the **Source folder** field, and enter User A's **Username** and **Password**.
4. Enter the completed folder path into the **Completed folder** field.
5. Check the **Logon with** checkbox directly below the **Completed folder** field, and enter User B's **Username** and **Password**.
6. Enter the failed folder path in the **Failed folder** field.
7. Check the **Logon with** checkbox directly below the **Failed folder** field, and enter User C's **Username** and **Password**.
8. Enter the image folder path in the **Image folder** field.
9. Check the **Logon with** checkbox directly below the **Image folder** field, and enter User D's **Username** and **Password**.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/defining-the-source-data-location/examples.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.
