Multiple users in "disable single account mode" #1027

New Issue

Open

opened 2025-11-20 05:22:34 -05:00 by saavagebueno · 20 comments

saavagebueno commented 2025-11-20 05:22:34 -05:00

Owner

Copy Link

Originally created by @Gifff69 on GitHub (Jun 27, 2024).

I am using selfhosted Netbird. I would like to create new network for separate department.
Different network with separate account can be achieved when disabled single account mode. However, no other users can be associated to each separated account. Does Netbird support multiple users with multiple accounts?

Are you using NetBird Cloud?

Self-hosted

Originally created by @Gifff69 on GitHub (Jun 27, 2024). I am using selfhosted Netbird. I would like to create new network for separate department. Different network with separate account can be achieved when disabled single account mode. However, no other users can be associated to each separated account. Does Netbird support multiple users with multiple accounts?   Are you using NetBird Cloud? Self-hosted

saavagebueno added the feature-request label 2025-11-20 05:22:34 -05:00

saavagebueno commented 2025-11-20 05:22:35 -05:00

Author

Owner

Copy Link

@bcmmbaga commented on GitHub (Jun 28, 2024):

Hello @Gifff69, Currently this feature is not yet supported. Could you please share more about why you need multiple department accounts in Netbird? How do you plan to manage and associate multiple users with these separate accounts?

@bcmmbaga commented on GitHub (Jun 28, 2024): Hello @Gifff69, Currently this feature is not yet supported. Could you please share more about why you need multiple department accounts in Netbird? How do you plan to manage and associate multiple users with these separate accounts?

saavagebueno commented 2025-11-20 05:22:35 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jun 28, 2024):

Hello @Gifff69, Currently this feature is not yet supported. Could you please share more about why you need multiple department accounts in Netbird? How do you plan to manage and associate multiple users with these separate accounts?

I would like to manage different department network by using same Management UI.
Each account have owner who can create new user and assign to admin or user role.
The idea is same as Netbird Cloud. https://docs.netbird.io/how-to/add-users-to-your-network
Separated network for each account and associate multiple users under same Management UI. i.e. app.netbird.io.

Do you have roadmap to add this feature? Can share the schedule?

@Gifff69 commented on GitHub (Jun 28, 2024): > Hello @Gifff69, Currently this feature is not yet supported. Could you please share more about why you need multiple department accounts in Netbird? How do you plan to manage and associate multiple users with these separate accounts? I would like to manage different department network by using same Management UI. Each account have owner who can create new user and assign to admin or user role. The idea is same as Netbird Cloud. https://docs.netbird.io/how-to/add-users-to-your-network Separated network for each account and associate multiple users under same Management UI. i.e. app.netbird.io. Do you have roadmap to add this feature? Can share the schedule?

saavagebueno commented 2025-11-20 05:22:35 -05:00

Author

Owner

Copy Link

@bcmmbaga commented on GitHub (Jun 28, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

@bcmmbaga commented on GitHub (Jun 28, 2024): it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

saavagebueno commented 2025-11-20 05:22:35 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jun 28, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

@Gifff69 commented on GitHub (Jun 28, 2024): > it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources. When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

saavagebueno commented 2025-11-20 05:22:35 -05:00

Author

Owner

Copy Link

@bcmmbaga commented on GitHub (Jun 28, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide

@bcmmbaga commented on GitHub (Jun 28, 2024): > > it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources. > > When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account? You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide

saavagebueno commented 2025-11-20 05:22:35 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jun 28, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide

Thanks for reply.
In summary, can selfhosted NetBird support this hierarchy?
Account1, network1, => user01-05
Account2, network2, => user01-05
Account3, network3, => user01-05

@Gifff69 commented on GitHub (Jun 28, 2024): > > > it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources. > > > > > > When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account? > > You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05

saavagebueno commented 2025-11-20 05:22:36 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 1, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide

Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05

@bcmmbaga
Can confirm if Selfhosted NetBird support the hierarchy below? Thanks.
Account1, network1, => user01-05;
Account2, network2, => user01-05;
Account3, network3, => user01-05

@Gifff69 commented on GitHub (Jul 1, 2024): > > > > it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources. > > > > > > > > > When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account? > > > > > > You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide > > Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05 @bcmmbaga Can confirm if Selfhosted NetBird support the hierarchy below? Thanks. Account1, network1, => user01-05; Account2, network2, => user01-05; Account3, network3, => user01-05

saavagebueno commented 2025-11-20 05:22:36 -05:00

Author

Owner

Copy Link

@bcmmbaga commented on GitHub (Jul 2, 2024):

To understand your requirement better, are these user01-05 the same for all three accounts?

@bcmmbaga commented on GitHub (Jul 2, 2024): To understand your requirement better, are these user01-05 the same for all three accounts?

saavagebueno commented 2025-11-20 05:22:36 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 2, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide

Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05

@bcmmbaga Can confirm if Selfhosted NetBird support the hierarchy below? Thanks. Account1, network1, => user01-05; Account2, network2, => user01-05; Account3, network3, => user01-05

To understand your requirement better, are these user01-05 the same for all three accounts?

no, separate users under corresponding account/network.

@Gifff69 commented on GitHub (Jul 2, 2024): > > > > > it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources. > > > > > > > > > > > > When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account? > > > > > > > > > You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide > > > > > > Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05 > > @bcmmbaga Can confirm if Selfhosted NetBird support the hierarchy below? Thanks. Account1, network1, => user01-05; Account2, network2, => user01-05; Account3, network3, => user01-05 > To understand your requirement better, are these user01-05 the same for all three accounts? no, separate users under corresponding account/network.

saavagebueno commented 2025-11-20 05:22:36 -05:00

Author

Owner

Copy Link

@bcmmbaga commented on GitHub (Jul 2, 2024):

it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources.

When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account?

You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide

Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05

@bcmmbaga Can confirm if Selfhosted NetBird support the hierarchy below? Thanks. Account1, network1, => user01-05; Account2, network2, => user01-05; Account3, network3, => user01-05

To understand your requirement better, are these user01-05 the same for all three accounts?

no, separate users under corresponding account/network.

Yes, this is supported.

@bcmmbaga commented on GitHub (Jul 2, 2024): > > > > > > it's not currently on our roadmap. in the meantime, you can manage the network by creating a single account and controlling departmental access with access control policies. This setup allows all users to belong to the same organization account while maintaining segregated access to organizational network resources. > > > > > > > > > > > > > > > When I disable single account mode, it implies that creating separated network. In this case, how to create multiple users for each account? > > > > > > > > > > > > You should use single account mode (do not disable single account mode). This way, all organizational users are managed within the same account. You can add users from your Identity Provider (IdP), and they will be automatically synced to your NetBird instance. For detailed instructions on setting up and integrating with a supported IdP, you can refer to our self-hosting guide at https://docs.netbird.io/selfhosted/selfhosted-guide > > > > > > > > > Thanks for reply. In summary, can selfhosted NetBird support this hierarchy? Account1, network1, => user01-05 Account2, network2, => user01-05 Account3, network3, => user01-05 > > > > > > @bcmmbaga Can confirm if Selfhosted NetBird support the hierarchy below? Thanks. Account1, network1, => user01-05; Account2, network2, => user01-05; Account3, network3, => user01-05 > > > To understand your requirement better, are these user01-05 the same for all three accounts? > > no, separate users under corresponding account/network. Yes, this is supported.

saavagebueno commented 2025-11-20 05:22:36 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 2, 2024):

I can create one account/network only associated with 3users by using default selfhosted "single account mode".
Please advise how to create another account/network.

@Gifff69 commented on GitHub (Jul 2, 2024): I can create one account/network only associated with 3users by using default selfhosted "single account mode". Please advise how to create another account/network. 

saavagebueno commented 2025-11-20 05:22:36 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Jul 2, 2024):

@Gifff69, can you share more about your deployment? We usually advise administrators to use groups and access control to segregate accounts within a single org, especially when this department configuration might need to connect to each other, and disabling the single account mode will make that very hard.

Also, can you share what is your identity provider? Does it support updating JWT claims? It seems like you are using Zitadel from our quick start guide and some Gmail accounts, but that won't work with these domains.

@mlsmaycon commented on GitHub (Jul 2, 2024): @Gifff69, can you share more about your deployment? We usually advise administrators to use groups and access control to segregate accounts within a single org, especially when this department configuration might need to connect to each other, and disabling the single account mode will make that very hard. Also, can you share what is your identity provider? Does it support updating JWT claims? It seems like you are using Zitadel from our quick start guide and some Gmail accounts, but that won't work with these domains.

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 2, 2024):

@mlsmaycon, Understanding that using groups and access control to segregate accounts within a single org. But it would be difficult to manage plenty of peers. Thus, we would like to create another account which act as new organization. Each account associated multiples users form new network and have separated peers.

Yes, you are right, we are using Zitadel from quick start guide and some Gmail accounts.
Kindly advise why that won't work with these domains? How to achieve above requirement?

@Gifff69 commented on GitHub (Jul 2, 2024): @mlsmaycon, Understanding that using groups and access control to segregate accounts within a single org. But it would be difficult to manage plenty of peers. Thus, we would like to create another account which act as new organization. Each account associated multiples users form new network and have separated peers. Yes, you are right, we are using Zitadel from quick start guide and some Gmail accounts. Kindly advise why that won't work with these domains? How to achieve above requirement?

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 2, 2024):

@mlsmaycon, Understanding that using groups and access control to segregate accounts within a single org. But it would be difficult to manage plenty of peers. Thus, we would like to create another account which act as new organization. Each account associated multiples users form new network and have separated peers.

Yes, you are right, we are using Zitadel from quick start guide and some Gmail accounts. Kindly advise why that won't work with these domains? How to achieve above requirement?

@mlsmaycon, in other words, kindly advise if selfhosted netbird support multi-organization.

BTW, I think it is similar case raised before. Can share the update? Thanks.
https://github.com/netbirdio/netbird/issues/446

@Gifff69 commented on GitHub (Jul 2, 2024): > @mlsmaycon, Understanding that using groups and access control to segregate accounts within a single org. But it would be difficult to manage plenty of peers. Thus, we would like to create another account which act as new organization. Each account associated multiples users form new network and have separated peers. > > Yes, you are right, we are using Zitadel from quick start guide and some Gmail accounts. Kindly advise why that won't work with these domains? How to achieve above requirement? @mlsmaycon, in other words, kindly advise if selfhosted netbird support multi-organization. BTW, I think it is similar case raised before. Can share the update? Thanks. https://github.com/netbirdio/netbird/issues/446

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@BJorah commented on GitHub (Jul 22, 2024):

Hi! @Gifff69
Would you please tell me How to set up a self-hosted server to disable single account mode?
so that I can create serval different nets on one server.

@BJorah commented on GitHub (Jul 22, 2024): Hi! @Gifff69 Would you please tell me **How to set up a self-hosted server to disable single account mode?** so that I can create serval different nets on one server.

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 23, 2024):

Hi! @Gifff69 Would you please tell me How to set up a self-hosted server to disable single account mode? so that I can create serval different nets on one server.

Follow this under advanced guide.
https://docs.netbird.io/selfhosted/selfhosted-guide#step-4-disable-single-account-mode-optional

@Gifff69 commented on GitHub (Jul 23, 2024): > Hi! @Gifff69 Would you please tell me **How to set up a self-hosted server to disable single account mode?** so that I can create serval different nets on one server. Follow this under advanced guide. https://docs.netbird.io/selfhosted/selfhosted-guide#step-4-disable-single-account-mode-optional

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@BJorah commented on GitHub (Jul 23, 2024):

@Gifff69
Thanks for replying me!
Follow the guide, I add "--disable-single-account-mode"
Besides,need I remove this line bellow?

@BJorah commented on GitHub (Jul 23, 2024): @Gifff69 Thanks for replying me! Follow the guide, I add "--disable-single-account-mode" Besides,need I remove this line bellow? 

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@Gifff69 commented on GitHub (Jul 23, 2024):

@Gifff69 Thanks for replying me! Follow the guide, I add "--disable-single-account-mode" Besides,need I remove this line bellow?

no, just keep it.

@Gifff69 commented on GitHub (Jul 23, 2024): > @Gifff69 Thanks for replying me! Follow the guide, I add "--disable-single-account-mode" Besides,need I remove this line bellow?  no, just keep it.

saavagebueno commented 2025-11-20 05:22:37 -05:00

Author

Owner

Copy Link

@BJorah commented on GitHub (Jul 24, 2024):

@Gifff69 I truly appreciate your timely help. I have successfully made it :)

@BJorah commented on GitHub (Jul 24, 2024): @Gifff69 I truly appreciate your timely help. I have successfully made it :)

saavagebueno commented 2025-11-20 05:22:38 -05:00

Author

Owner

Copy Link

@ghazyami commented on GitHub (Sep 3, 2025):

Is this not implement yet? Would be nice to have.

• One netbird instance.
• Multiple accounts.
• Each account has an owner and users.

@ghazyami commented on GitHub (Sep 3, 2025): Is this not implement yet? Would be nice to have. - One netbird instance. - Multiple accounts. - Each account has an owner and users.

saavagebueno referenced this issue 2025-11-20 08:04:33 -05:00

[PR #1027] Record idp manager type #2973

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

update/wails-v3.0.0-alpha2.111

fix/routeselector-atomic-exit-node

netmap_progressive_alignment

dependabot/go_modules/aws-sdk-8f849ebaed

dependabot/github_actions/actions-c97fa3f10c

dependabot/go_modules/otel-e34c790afd

dependabot/go_modules/gorm-2271c8195b

dependabot/go_modules/pion-5f703e1eca

dependabot/go_modules/testcontainers-de325c0dd6

dependabot/go_modules/wireguard-dbd6b95108

feat/admin-cli

fix/fail-to-create-upnp-port-mapping-on-opnsense-firewall

nmap/components-impl

refactor/relay-foreign-cache

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.104.2

dependabot/go_modules/golang.org/x/image-0.38.0

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

dependabot/go_modules/github.com/pion/dtls/v3-3.1.4

0.75.0-branch

dmitri-event-aggregation

dependabot/npm_and_yarn/proxy/web/npm_and_yarn-2f40f34922

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.3

dependabot/go_modules/github.com/oapi-codegen/runtime-1.4.2

dependabot/go_modules/github.com/eko/gocache/store/redis/v4-4.2.6

dependabot/go_modules/github.com/pkg/sftp-1.13.10

dependabot/go_modules/github.com/gopacket/gopacket-1.6.1

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.3

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.19.0

dependabot/go_modules/golang.org/x/sys-0.46.0

dependabot/go_modules/github.com/pires/go-proxyproto-0.12.0

peer-acl-multi-source

embedded-vnc

fix/signal-watchdog-sync-stop

docs/agent-network

feature/ios-ssh

client-json-socket

test/affected-logic

fix/revert-ice-filter

refactor/simplify-affected-peers

pascal-filter-policies-by-direction

claude/lock-contention-peer-connect-g8t6au

dmitri-filter-policies-by-direction

refactor/migrate-profiles-to-go

profile-bindings-ios

fix/skip-restart-unchanged-route

fix/mgmt-cache-async-resolve

refactor/wails-update-105

client_lifetime_serialization_refactor

fix/browser-ssh-2

fix/ipv6-and-netstack-accept-loop

fix/browser-ssh

profile-id-name-test

refactor/mgmt-bootstrap

mdm_integration

feat/getting-started-unified-wizard

socket-grpc-permissions

fix/mysql-index-migration

windows-dns-firewall

tests/enable-race-on-tests

ui-refactor-gtk3

feature/affected-peers-grpc

profile-id

lazyconn-first-packet-fix-v2

claude/focused-gates-VMTgb

ui-tray-linux-leftclick

fix/ctx-enrichment

daemon-owner

feature/android-client-ssh

worktree-accept-ra-forwarding

nmap/combined-deploy

task/align_protobuff_toolset

feature/session-extend

add-json-yaml-flags

refactor/ephemeral-cleanup

claude/webtransport-relay-wasm-mUjY9

claude/vnc-udp-feasibility-6KB1U

fix-ssh-authorized-users-multi-rule

fix/wgport-config

e2e-windows-dns-combined

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

release/0.68.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

feature/changeset

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

v0.74.1

v0.75.0-rc.4

v0.74.0

v0.74.0-rc.2

v0.74.0-rc.1

v0.73.2

v0.75.0-rc.3

v0.75.0-rc.2

v0.73.1

v0.75.0-rc.1

v0.73.0

v0.72.4

v0.72.3

v0.72.2

v0.72.1

v0.72.0

v0.71.4

v0.71.3

v0.71.2

v0.71.1

v0.71.0

v0.70.5

v0.70.4

v0.70.3

v0.70.2

v0.70.1

v0.70.0

v0.69.0

v0.68.3

v0.68.2

v0.68.1

v0.68.0

v0.67.4

v0.67.3

v0.67.2

v0.67.1

v0.67.0

v0.66.4

v0.66.3

v0.66.2

v0.66.1

v0.66.0

v0.65.3

v0.65.2

v0.65.1

v0.65.0

v0.64.6

v0.64.5

v0.64.4

v0.64.3

v0.64.2

v0.64.1

v0.64.0

v0.63.0

v0.62.3

v0.62.2

v0.62.1

v0.62.0

v0.61.2

v0.61.1

v0.61.0

v0.60.9

v0.60.8

v0.60.7

v0.60.6

v0.60.5

v0.60.4

v0.60.3

v0.60.2

v0.60.1

v0.60.0

v0.59.13

v0.59.12

v0.59.11

v0.59.10

v0.59.9

v0.59.8

v0.59.7

v0.59.6

v0.59.5

v0.59.4

v0.59.3

v0.59.2

v0.59.1

v0.59.0

v0.58.2

v0.58.1

v0.58.0

v0.57.1

v0.57.0

v0.56.1

v0.56.0

v0.55.1

v0.55.0

v0.54.2

v0.54.1

v0.54.0

v0.53.0

v0.52.2

v0.52.1

v0.52.0

v0.51.2

v0.51.1

v0.51.0

v0.50.3

v0.50.2

v0.50.1

v0.50.0

v0.49.0

v0.48.0-dev2

v0.48.0

v0.47.2

v0.47.1

v0.47.0

v0.46.0

v0.45.3

v0.45.2

v0.45.1

v0.45.0

v0.44.0

v0.43.3

v0.43.2

v0.43.1

v0.43.0

v0.42.0

v0.41.3

v0.41.2

v0.41.1

v0.41.0

v0.40.1

v0.40.0

v0.39.2

v0.39.1

v0.39.0

v0.38.2

v0.38.1

v0.38.0

v0.37.2

v0.37.1

v0.37.0

v0.36.7

v0.36.6

v0.36.5

v0.36.4

v0.36.3

v0.36.2

v0.36.1

v0.36.0

v0.35.2

v0.35.1

v0.35.0

v0.34.1

v0.34.0

v0.33.0

v0.32.0

v0.31.1

v0.31.0

v0.30.3

v0.30.2

v0.30.1

v0.30.0

v0.29.4

v0.29.3

0.29.3

v0.29.2

v0.29.1

v0.29.0

v0.28.9

v0.28.8

v0.28.7

v0.28.6

v0.28.5

v0.28.4

v0.28.3

v0.28.2

v0.28.1

v0.28.0

v0.27.10

v0.27.9

v0.27.8

v0.27.7

v0.27.6

v0.27.5

v0.27.4

v0.27.3

v0.27.2

v0.27.1

v0.27.0

v0.26.7

v0.26.6

v0.26.5

v0.26.4

v0.26.3

v0.26.2

v0.26.1

v0.26.0

v0.25.9

v0.25.8

v0.25.7

v0.25.6

v0.25.5

v0.25.4

v0.25.3

v0.25.2

v0.25.1

v0.25.0

v0.24.4

v0.24.3

v0.24.2

v0.24.1

v0.24.0

v0.23.9

v0.23.8

v0.23.7

v0.23.6

v0.23.5

v0.23.4

v0.23.3

v0.23.2

v0.23.1

v0.23.0

v0.22.7

v0.22.6

v0.22.5

v0.22.4

v0.22.3

v0.22.2

v0.22.1

v0.22.0

v0.21.11

v0.21.10

v0.21.9

v0.21.8

v0.21.7

v0.21.6

v0.21.5

v0.21.4

v0.21.3

v0.21.2

v0.21.1

v0.21.0

v0.20.8

v0.20.7

v0.20.6

v0.20.5

v0.20.4

v0.20.3

v0.20.2

v0.20.1

v0.20.0

v0.19.0

v0.18.1

v0.18.0

v0.17.0

v0.16.0

v0.15.3

v0.15.2

v0.15.1

v0.15.0

v0.14.6

v0.14.5

v0.14.4

v0.14.3

v0.14.2

v0.14.1

v0.14.0

v0.13.0

v0.12.0

v0.11.6

v0.11.5

v0.11.4

v0.11.3

v0.11.2

v0.11.1

v0.11.0

v0.10.10

v0.10.9

v0.10.8

v0.10.7

v0.10.6

v0.10.5

v0.10.4

v0.10.3

v0.10.2

v0.10.1

v0.10.0

v0.9.8

v0.9.7

v0.9.6

v0.9.5

v0.9.4

v0.9.3

v0.9.2

v0.9.1

v0.9.0

v0.8.12

v0.8.11

v0.8.10

v0.8.9

v0.8.8

v0.8.7

v0.8.6

v0.8.5

v0.8.4

v0.8.3

v0.8.2

v0.8.1

v0.8.0

v0.7.1

v0.7.0

v0.6.4

v0.6.3

v0.6.2

v0.6.1

v0.6.0

v0.5.11

v0.5.10

v0.5.1

v0.5.0

v0.4.0

v0.3.5

v0.3.4

v0.3.3

v0.3.2

v0.3.1

v0.3.0

v0.2.3

v0.2.2-beta.1

v0.2.1-beta.5

v0.2.0-beta.5

v0.2.0-beta.4

v0.2.0-beta.3

v0.2.0-beta.2

v0.2.0-beta.1

v0.1.0-beta.3

v0.1.0-beta.2

v0.1.0-beta.1

v0.1.0-rc.2

v0.1.0-rc-1

v0.0.8-hotfix-1

v0.0.8

v0.0.7

v0.0.6

v0.0.5

v0.0.4

v0.0.3

v0.0.2

v0.0.1

v0.0.0

Labels

Clear labels

2021 Q4

2022 Q1

2022 Q1

accessibility

acl

agent

agent

Android

Android

api

authentik

automation

azure

battery-usage

bug

cache

client

client-ui

cloud

cloud-only

cloudflare

community

compatibility

config-idp

config-issue

connection

contribution

coturn

cross-vpn

dashboard

data-usage

distribution

dns

docker

documentation

duplicate

enhancement

enhancement

event-stream

feature-request

freebsd

getting-started

go

good first issue

gui

help wanted

home-assistant

idp

inconsistency

integration

integrations

ios

ipv6

jwt

k8s

keycloak

linux

login

macos

management-service

missing-docs

mobile

moved-internal

needs-review

netbird-ui

networking

new-platform

nginx

notification

okta

openwrt

packaging

peer-management

peer-management

peer-management

performance

postgres

posture-checks

psk

pull-request

Mirrored from GitHub Pull Request

question

refactor

relay

release

rfc

routes

security

security-related

self-hosting

server

signal

sleep-issue

ssh

ssl

status

store

synology

system-compatibility-issue

test-suite

third-party-integration

triage

triage-needed

troubleshooting

UX

waiting-feedback

windows

wontfix

zitadel

No Label feature-request

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

saavagebueno

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SVI/netbird#1027