Docs: getting started says what is retried and what waits for the next start
Test / test (pull_request) Successful in 51s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
This commit is contained in:
Bendik Aagaard Lynghaug
2026-09-29 18:03:51 +02:00
co-authored by Claude Opus 5.5
parent 641c5f1bd3
commit 7a50ce77b2
+4 -3
View File
@@ -104,8 +104,10 @@ At start, portal:
questions, with their link. With `RESPONSIBLE_GROUP` they all join questions, with their link. With `RESPONSIBLE_GROUP` they all join
it; someone who already had an account is added without a mail. it; someone who already had an account is added without a mail.
Kanidm may still be starting beside portal, so a failed attempt is Kanidm may still be starting beside portal, so the first person's
tried again, a minute apart. The log says what happened, per person. invite is tried again a minute apart, up to twenty times. A responsible
person who could not be set up is left for the next start. The log says
what happened, per person.
## 5. The rest come in from the desks ## 5. The rest come in from the desks
@@ -113,7 +115,6 @@ From here nobody touches Kanidm:
- **At a desk**, whoever may invite fills in a name and an address. - **At a desk**, whoever may invite fills in a name and an address.
Portal makes the account, adds them to the group, and mails the link. Portal makes the account, adds them to the group, and mails the link.
The invites sent are listed on that desk.
- **A decision can be the invitation.** A state with `grants: group` - **A decision can be the invitation.** A state with `grants: group`
in `aggregates.yaml` puts the person a case is about into that group in `aggregates.yaml` puts the person a case is about into that group
when the case arrives there - an approved committee application that when the case arrives there - an approved committee application that