sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-08-25 01:01:27 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: reorder Assign Peers to Groups videos

Browse Source 
Show the drag-to-group recording right after the text it illustrates,
then the group-from-selection flow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Eduard Gert
2026-08-20 15:54:33 +02:00
parent be5342b71e
commit 43f1092436
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/pages/manage/control-center/draft-mode.mdx
View File

@@ -104,6 +104,11 @@ Right-click a node and choose **Rename**. We rename the server to `staging-01` a
Drag the `staging-01` node onto the `Staging` group. The peer is absorbed into the group and the group's member count goes up. Membership travels with the group's change, so you never manage it separately.
<p>
<Video src="/docs-static/img/manage/control-center/control-center-draft-drag-to-group.mp4"
label="Dragging the staging-01 peer onto the Staging group, which absorbs it and updates its member count"/>
</p>
To group several peers at once, drag a selection across them, then click **Create Group** in the selection menu (or press `G`) and name the group:
<p>
@@ -111,11 +116,6 @@ To group several peers at once, drag a selection across them, then click **Creat
label="Drag-selecting several peers, clicking Create Group in the selection menu, and naming the new group"/>
</p>
<p>
<Video src="/docs-static/img/manage/control-center/control-center-draft-drag-to-group.mp4"
label="Dragging the staging-01 peer onto the Staging group, which absorbs it and updates its member count"/>
</p>
### Connect Nodes to Create Policies
Drag the existing `DevOps` group from the components panel onto the canvas, then drag a connection from `DevOps` to `Staging`. The standard policy editor opens with both sides prefilled. Restrict it to what the team actually needs: TCP port `443` for the web app, not all traffic. The first policy you deploy should already be the least-privilege one.