From ae05289e8b6f6987f66e386789d67aa80a98e7b7 Mon Sep 17 00:00:00 2001 From: atlas Date: Wed, 12 Aug 2026 18:33:53 +0200 Subject: [PATCH] =?UTF-8?q?docs(3201):=20setup=20guide=20=E2=80=94=20the?= =?UTF-8?q?=20group=20flag=20is=20not=20one-shot=20any=20more?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The step-3 warning said to keep `--group admins` and left the impression that a later re-run would fix a missing one. It would not: `user add` refuses on an existing name, so until `user update` existed the only repair was hand-editing two files as root. mara asked the question the warning should have answered — "will the cmd just add the group or do i get a whole new user?". Deliberately in this PR rather than #3199's: the sentence only becomes true once the verb it names exists. --- docs/setup.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/setup.md b/docs/setup.md index 76235dbd..8e333d5f 100644 --- a/docs/setup.md +++ b/docs/setup.md @@ -54,6 +54,10 @@ surfaces (the swarm UI below) are gated on that group, and an account without it authenticates successfully and is then refused — which reads like a broken login rather than a missing group. +If an account already exists without it, `user add` will refuse rather +than amend — adding the group afterwards is `swarmctl user update mara +--add-group admins`. + Detail, including what the password is and why this stays manual: [`swarm/sso.md`](swarm/sso.md).