@@ -172,6 +172,21 @@ adjust the space's access rules.
172172- ** Custom groups** : create with `brainkb_create_role("uk_collaborator",
173173 "Community", "UK collaborators")` , assign with ` brainkb_assign_role(email,
174174 "uk_collaborator")`, then grant it capabilities (above) and/or per-space access.
175+ A ** new group starts with no powers** (read only) until you grant capabilities —
176+ creating/assigning it is not enough by itself.
177+
178+ ** Worked example — a group that can ingest, end to end:**
179+ ```
180+ brainkb_create_role("uk_collaborator", "Community", "UK collaborators")
181+ brainkb_grant_role_capability("uk_collaborator", "ingest") # give the group the power
182+ brainkb_assign_role("alice@uk.org", "uk_collaborator") # put a user in it
183+ brainkb_capabilities("alice@uk.org") # verify → includes "ingest"
184+ ```
185+ Global capability (ingest anywhere they have space write) vs per-space: to scope a
186+ group to ONE space instead, skip grant_role_capability and add a space write rule —
187+ ` brainkb_add_access_rule("lab-space","write","global_role","uk_collaborator") ` .
188+
189+ Example prompt: * "Create a group uk_collaborator, let it ingest, and add alice@uk.org to it."*
175190- ** Fine-grained per-space access rules** (space owner/manager): restrict an action
176191 within a space to a role, a member, or a space-role.
177192 - List: ` brainkb_list_access_rules(slug) ` .
0 commit comments