> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/security/whitelisting-directories.md).

# Whitelisting Directories

## Description

Some functions in the LogicNets Designer allow the Designer to reference external directories. One example of this is the *File Upload* part, which allows you to give your application users the ability to upload files. These files can be saved to a named drive/directory that is external to the LogicNets application and folder structure.

For security reasons, LogicNets blacklists all external directories, but you can use the System Configuration package to whitelist named directories if needed.

## How to Whitelist a Directory

Whitelisting a directory means that you identify it to the LogicNets system so the system allows you to access that directory from LogicNets application. The steps to whitelist a directory are as follows:

1. Navigate to the *System Configuration* package on your LogicNets landing page. Note: You may not have the permissions required to access this package and may need to ask your LogicNets administrator to provide you access.
2. Open the package, and select the *Security* tab.
3. In the *Whitelisted directories* field, enter the directory to be whitelisted. For multiple folders, click the *+* button to enter the names of additional directories.
4. Click *Save* to save your updates.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ef0d0416f04490a44a10315cb931a739b32115f5%2F88d73fb9-dc1b-426c-8e18-e5adc868312f.png?alt=media)


---

# 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://community-test.logicnets.com/release-9/platform-documentation/system-administration/security/whitelisting-directories.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.