[GH-ISSUE #5725] Support resource group in Networks #11694

Open
opened 2026-08-05 01:30:31 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @4piu on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5725

Is your feature request related to a problem? Please describe.
In the current NetBird “Networks” experience, organizations with many resources (multiple CIDRs across sites/regions + multiple domain resources) end up with a flat list of individual entries in the client Networks view, making it tedious to enable/disable the right set of resources.

NetBird already has Groups, and resources can be associated with them, but today Groups are primarily used for access control/policies. They are not used for resource management (bulk operations) and are not reflected in the client Networks UI, so users still have to toggle resources one-by-one.

This becomes error-prone and time-consuming when switching contexts (e.g., enabling “Asia office” + “AWS prod” resources for a task, then disabling them afterward).

Describe the solution you'd like
Extend the existing Group concept (or add a dedicated “Resource Group” view built on top of it) so that network resources (IP/CIDR/Domain) can be organized and managed as a set, and have that structure shown in the client Networks UI.

Concretely:

  • In the client Networks view, display resources grouped by Group (collapsible sections).
  • Add a group-level toggle to enable/disable all resources in that Group at once.
  • Support an “indeterminate” state when only some resources in the group are enabled (optional but nice).
  • Keep the ability to toggle individual resources inside the group.

Describe alternatives you've considered

  • Naming conventions/prefixes to sort resources (helps readability, doesn’t solve bulk toggle).
  • Collapsing CIDRs into larger ranges (often not possible and can broaden access too much).
  • Reducing who can see resources via policies (doesn’t help users who legitimately need multiple sites).

Additional context
Key use cases:

  • Multi-site orgs: each site has several CIDRs + internal domains; users want one toggle per site.
  • Hybrid cloud/on-prem: quick switching between prod, dev, dc1, dc2 resource sets.
  • Temporary access windows: enable a partner/vendor/site group during maintenance, disable afterward with one click.
  • Troubleshooting: quickly disable a whole group to isolate routing/DNS issues.
Originally created by @4piu on GitHub (Mar 29, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5725 **Is your feature request related to a problem? Please describe.** In the current NetBird “Networks” experience, organizations with many resources (multiple CIDRs across sites/regions + multiple domain resources) end up with a *flat list* of individual entries in the client Networks view, making it tedious to enable/disable the right set of resources. NetBird already has **Groups**, and resources can be associated with them, but today Groups are primarily used for **access control/policies**. They are **not** used for **resource management** (bulk operations) and are **not reflected in the client Networks UI**, so users still have to toggle resources one-by-one. This becomes error-prone and time-consuming when switching contexts (e.g., enabling “Asia office” + “AWS prod” resources for a task, then disabling them afterward). **Describe the solution you'd like** Extend the existing **Group** concept (or add a dedicated “Resource Group” view built on top of it) so that network resources (IP/CIDR/Domain) can be **organized and managed as a set**, and have that structure **shown in the client Networks UI**. Concretely: - In the client Networks view, display resources **grouped by Group** (collapsible sections). - Add a **group-level toggle** to enable/disable all resources in that Group at once. - Support an “indeterminate” state when only some resources in the group are enabled (optional but nice). - Keep the ability to toggle individual resources inside the group. **Describe alternatives you've considered** - Naming conventions/prefixes to sort resources (helps readability, doesn’t solve bulk toggle). - Collapsing CIDRs into larger ranges (often not possible and can broaden access too much). - Reducing who can see resources via policies (doesn’t help users who legitimately need multiple sites). **Additional context** Key use cases: - **Multi-site orgs:** each site has several CIDRs + internal domains; users want one toggle per site. - **Hybrid cloud/on-prem:** quick switching between `prod`, `dev`, `dc1`, `dc2` resource sets. - **Temporary access windows:** enable a partner/vendor/site group during maintenance, disable afterward with one click. - **Troubleshooting:** quickly disable a whole group to isolate routing/DNS issues.
saavagebueno added the feature-request label 2026-08-05 01:30:31 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11694