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:
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.
Permission evaluation rules
The system evaluates user permissions according to the following rules:
- The primary account always has operation permissions for all folders
- If the current folder or any of its parent folders have a bound team, the user must belong to that team to have permissions
- If no team is bound anywhere in the folder chain, all users can operate
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.
