[GH-ISSUE #4863] Add ability to (re)assign peer to user #9454

Open
opened 2026-08-05 01:22:10 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @hgaiser on GitHub (Nov 26, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4863

Is your feature request related to a problem? Please describe.
Peers connected using a setup key are not assigned to any user. That itself is not a big issue, but the admin dashboard also doesn't allow to assign a user afterwards.

(granted, also not a big issue, but nice to have)

Describe the solution you'd like
Two solutions, both valuable:

  1. An option to assign a setup key to a user, such that peers created with that setup key are automatically assigned to that user.
  2. An option to (re)assign a peer to a different user.

Describe alternatives you've considered

  1. A CLI option to choose a user, but that doesn't seem very secure.
  2. Remove the reference to the user in the Peer dashboard entirely, since there doesn't seem to be any use for it anyway (?).

Additional context
N/A

Originally created by @hgaiser on GitHub (Nov 26, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4863 **Is your feature request related to a problem? Please describe.** Peers connected using a setup key are not assigned to any user. That itself is not a big issue, but the admin dashboard also doesn't allow to assign a user afterwards. (granted, also not a big issue, but nice to have) **Describe the solution you'd like** Two solutions, both valuable: 1. An option to assign a setup key to a user, such that peers created with that setup key are automatically assigned to that user. 1. An option to (re)assign a peer to a different user. **Describe alternatives you've considered** 1. A CLI option to choose a user, but that doesn't seem very secure. 2. Remove the reference to the user in the Peer dashboard entirely, since there doesn't seem to be any use for it anyway (?). **Additional context** N/A
saavagebueno added the feature-request label 2026-08-05 01:22:10 -04:00
Author
Owner

@MichaelUray commented on GitHub (Nov 30, 2025):

  1. An option to assign a setup key to a user, such that peers created with that setup key are automatically assigned to that user.

  2. An option to (re)assign a peer to a different user.

3. An option to allow a user to create setup keys which assign then the devices automatically to him if used.

<!-- gh-comment-id:3592477155 --> @MichaelUray commented on GitHub (Nov 30, 2025): > 1. An option to assign a setup key to a user, such that peers created with that setup key are automatically assigned to that user. > > 2. An option to (re)assign a peer to a different user. **3. An option to allow a user to create setup keys which assign then the devices automatically to him if used.**
Author
Owner

@sOliverBa commented on GitHub (Feb 5, 2026):

Well, even with activated "DNS WIldcard Routing" i wasn't able to set a peer (be it a device like OPNsense, or anything else) to the dedicated sub-domain name i wanted it to be.

My plan is to have dedicated sub-domains for seperation (could be departments or different locations) and more memorable names. My example here uses locations as the primary distinction here and example.nbd is used as the base domain.

opnsense.muc.example.nbd
opnsense.nue.example.nbd
adam-mbp.muc.example.nbd (User Adam with a MacBook Pro in Munich bureau))
adam-macmini.muc.example.nbd (and with a Mac mini in Munich bureau))
eva-mbp.nue.example.nbd (User Eva with a MacBook Pro in Nuremberg bureau)
eva-imac.nue.example.nbd (User Eva with an iMac in Nuremberg bureau)

Now because the Netbird GUI on OPNsense and macOS doesn't offer any field for the DNS entry, you may end up with either the complete fqdn of it and or opnsense-22-123.example.nbd (the numbers are part of the WAN-IP it connected to the control plane). Try changing this now in the CLI or the Netbird GUI to "opnsense.muc.example.nbd" doesn't work (mind you, the "Allow Extra DNS Labels" option was set while creating the setup key). You only get "opnsense-muc.example.nbd" – see the missing dots as sub-domain seperator? You surely can imagine the other examples.
The only way of achiving this would be to only use the CLI on all machines while doing the initial setup. But then they are forever only simple machine peers.

So no invite, no SSO, no enforcement of the Session Expiration, no visualizing in the Control Center as user.

All what we need is either/and or an GUI accessible field for entering the desired domain name or at least the power for an admin to change it afterwards (like with the virtual IP) and all would be good. Lets make use of this great feature.
Whenever i need to access one of the devices/machines i could phrase the fqdn directly of my mind. In this example then user-machine.location.base.domain or eva-imac.nue.example.nbd

I see this as a shortcoming and missed opportunity.
Hopefully some Devs read this and can implement it.

BUT: thanks to all all developers and for making it Open Source (you're heros on the keyboard!).

Oliver

<!-- gh-comment-id:3855557027 --> @sOliverBa commented on GitHub (Feb 5, 2026): Well, even with activated "DNS WIldcard Routing" i wasn't able to set a peer (be it a device like OPNsense, or anything else) to the dedicated sub-domain name i wanted it to be. My plan is to have dedicated sub-domains for seperation (could be departments or different locations) and more memorable names. My example here uses locations as the primary distinction here and example.nbd is used as the base domain. opnsense.muc.example.nbd opnsense.nue.example.nbd adam-mbp.muc.example.nbd (User Adam with a MacBook Pro in Munich bureau)) adam-macmini.muc.example.nbd (and with a Mac mini in Munich bureau)) eva-mbp.nue.example.nbd (User Eva with a MacBook Pro in Nuremberg bureau) eva-imac.nue.example.nbd (User Eva with an iMac in Nuremberg bureau) Now because the Netbird GUI on OPNsense and macOS doesn't offer any field for the DNS entry, you may end up with either the complete fqdn of it and or opnsense-22-123.example.nbd (the numbers are part of the WAN-IP it connected to the control plane). Try changing this now in the CLI or the Netbird GUI to "opnsense.muc.example.nbd" doesn't work (mind you, the "Allow Extra DNS Labels" option was set while creating the setup key). You only get "opnsense-muc.example.nbd" – see the missing dots as sub-domain seperator? You surely can imagine the other examples. The only way of achiving this would be to only use the CLI on all machines while doing the initial setup. But then they are forever only simple machine peers. So no invite, no SSO, no enforcement of the Session Expiration, no visualizing in the Control Center as user. All what we need is either/and or an GUI accessible field for entering the desired domain name or at least the power for an admin to change it afterwards (like with the virtual IP) and all would be good. Lets make use of this great feature. Whenever i need to access one of the devices/machines i could phrase the fqdn directly of my mind. In this example then user-machine.location.base.domain or eva-imac.nue.example.nbd I see this as a shortcoming and missed opportunity. Hopefully some Devs read this and can implement it. BUT: thanks to all all developers and for making it Open Source (you're heros on the keyboard!). Oliver
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#9454