mirror of
https://github.com/netbirdio/docs.git
synced 2026-08-26 17:51:27 +02:00
docs(site-to-vpn): clarify when the target peer uses a setup key
Setup keys are for service / appliance peers; user peers (laptops, workstations) enroll through SSO and inherit groups from existing assignments. Reword the target-peer instruction to reflect that distinction.
This commit is contained in:
@@ -64,9 +64,12 @@ auto-assigned group so the peer lands in the right place:
|
||||
- Auto-assigned groups: create and add `site-routing-peers`
|
||||
4. Click **Create** and note the key
|
||||
|
||||
Repeat for the target peer if it isn't already enrolled — place it in a
|
||||
group like `backup-collectors`. The target peer is a regular NetBird peer;
|
||||
nothing special needs to be configured on it for this scenario.
|
||||
The target peer is a regular NetBird peer; nothing special needs to be
|
||||
configured on it for this scenario. If the target peer is a service or
|
||||
appliance (not a user device), create a second setup key for it the same
|
||||
way and add it to a group like `backup-collectors`. User peers — laptops
|
||||
and workstations — enroll through SSO instead and pick up their group via
|
||||
your existing group assignments.
|
||||
|
||||
## Step 2: Deploy the Routing Peer
|
||||
|
||||
|
||||
Reference in New Issue
Block a user