> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Folder management

> Use a tree-structured folder hierarchy to organize alert rules with team-based access control

Monitors uses a tree-structured folder hierarchy to organize and manage alert rules. Every alert rule must belong to a folder. You can use the hierarchical structure for categorized management and configure team access permissions at different levels.

**Menu Entry**: Alert Rules (left-side tree navigation)

## Folder tree

The left side of the page displays the folder tree structure. You can:

* **Create folders**: Create subfolders within the tree
* **Select folders**: Click a folder to view its details and associated alert rules
* **Nested hierarchy**: Supports multiple nesting levels to meet complex organizational needs

## Folder details

When a folder is selected, the right side displays its detailed information:

| Property       | Description                                                                   |
| -------------- | ----------------------------------------------------------------------------- |
| **Name**       | Folder name; authorized users can click the edit icon to modify               |
| **Notes**      | Supplementary description; authorized users can click the edit icon to modify |
| **Updated By** | The user who last modified this folder                                        |
| **Created By** | The user who created this folder                                              |
| **Updated At** | Last modification time                                                        |
| **Created At** | Creation time                                                                 |

## Team access control

Folders support team-based access control by binding teams to folders to restrict operation permissions.

### Permission inheritance

The **Permission Inheritance** table below the folder details shows the complete path from the current folder to the root node, along with the team bound at each level.

| Column              | Description                                                                      |
| ------------------- | -------------------------------------------------------------------------------- |
| **Node Path**       | Complete path from the root node to the current node                             |
| **Associated Team** | The team bound at this level; authorized users can click the edit icon to modify |

### Permission evaluation rules

The system evaluates user permissions according to the following rules:

1. The **primary account** always has operation permissions for all folders
2. If the current folder or any of its parent folders have a bound team, the user must belong to that team to have permissions
3. If no team is bound anywhere in the folder chain, all users can operate

<Tip>
  It is recommended to bind teams at the top-level folders so that subfolders naturally inherit the access scope. This allows you to partition alert rule management permissions by department or project.
</Tip>