Is your feature request related to a problem? Please describe.
Access List rules only show the raw IP/CIDR value. When a list has more than a few entries, it's hard to remember what each one represents (e.g., "office VPN," "client A's static IP," "monitoring server") without cross-referencing external notes.
Describe the solution you'd like
Add an optional label/description/comment field next to each IP/CIDR entry in the Access List "Access" tab. This would just be a UI-level annotation (not passed to nginx config, or optionally added as a # comment above the corresponding allow/deny line) so admins can identify at a glance what each rule is for.
Describe alternatives you've considered
Keeping a separate spreadsheet/doc mapping IPs to their purpose — error-prone and easy to let go stale.
Naming separate Access Lists per purpose — doesn't scale well when one list legitimately needs multiple distinct IPs/CIDRs.
Additional context
This would be purely additive (an optional text field per row) and wouldn't change existing behavior for lists that don't use it.
Is your feature request related to a problem? Please describe.
Access List rules only show the raw IP/CIDR value. When a list has more than a few entries, it's hard to remember what each one represents (e.g., "office VPN," "client A's static IP," "monitoring server") without cross-referencing external notes.
Describe the solution you'd like
Add an optional label/description/comment field next to each IP/CIDR entry in the Access List "Access" tab. This would just be a UI-level annotation (not passed to nginx config, or optionally added as a # comment above the corresponding allow/deny line) so admins can identify at a glance what each rule is for.
Describe alternatives you've considered
Keeping a separate spreadsheet/doc mapping IPs to their purpose — error-prone and easy to let go stale.
Naming separate Access Lists per purpose — doesn't scale well when one list legitimately needs multiple distinct IPs/CIDRs.
Additional context
This would be purely additive (an optional text field per row) and wouldn't change existing behavior for lists that don't use it.