> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/administration/security/folders.md).
# Folders
The "Folder Security" allows administrators to control access to individual folders and files within the data catalog and enables them to define permissions at a granular level.
When establishing a connection with a File System type connector, the default security applies to the root folder and inherits down to its subfolders.
**Folder Security Advantages:**
* **Selective Permissions:** Define security for specific folders or files, enabling different access levels for various data assets.
* **Bulk Permission Management:** Efficiently update role permissions and governance roles across multiple folders simultaneously.
* **Hierarchical Inheritance:** Changes to a child folder's access security automatically propagate to its subfolders.
* **File-Level Security:** Folder permissions extend to all associated files and their columns.
Based on the selected Data Source (Connection Name), the corresponding folders are displayed along with the governance roles, users, and roles with metadata and data permissions on those folders.
**Applying Separate Security to Child Folders**
To grant different access levels to a child folder compared to its parent, SGA or OE\_ADMIN can:
1. Click "Add New Folder."
2. Specify the Datalake and path of the child folder.
3. Assign metadata and data access permissions for specific roles or users.
**Permissions and Governance (SGA & OE\_ADMIN only):**
* **Update Permissions and Governance:** Modify permissions and governance roles for individual or multiple folders.
* **Delete Role Access:** Remove permission assignments for roles on individual or multiple folders.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ovaledge.com/release8.2/administration/security/folders.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.