Spaces: more than one manager #1107

Closed
opened 2026-11-04 03:11:30 +00:00 by Cordy · 5 comments
Owner

Gap (v0.7 feature-gap research, 2026-11-04, decided by Nikola). A space has exactly one owner; members are read + write or read only (docs/handbook/spaces.md "Members and roles" at 0e0885db, VERIFIED). When the owner is away, nobody else in the team can add members or change roles without an administrator.

Competitors. OpenCloud's "Can manage" role for any number of people (space roles); Nextcloud Team folders managed by admins or group managers; Seafile department admins. Sub-folder permissions inside a space (Seafile Pro) are a larger, later step and not part of this issue.

To research and decide when worked on. Role name and rights (members, sharing, quota view, rename, delete space?); the last-manager rule; directory-managed spaces (#1002) and IdP group attributes; owner transfer (#835) and departed owners (#654); the restore checklist; audit verbs; strings.

Refs: scratch/b7e/backlog/gap-v07/research-v07-gaps.md A8.

**Gap (v0.7 feature-gap research, 2026-11-04, decided by Nikola).** A space has exactly one owner; members are read + write or read only (`docs/handbook/spaces.md` "Members and roles" at 0e0885db, VERIFIED). When the owner is away, nobody else in the team can add members or change roles without an administrator. **Competitors.** OpenCloud's "Can manage" role for any number of people ([space roles](https://docs.opencloud.eu/docs/user/roles/space-roles)); Nextcloud Team folders managed by admins or group managers; Seafile department admins. Sub-folder permissions inside a space (Seafile Pro) are a larger, later step and not part of this issue. **To research and decide when worked on.** Role name and rights (members, sharing, quota view, rename, delete space?); the last-manager rule; directory-managed spaces (#1002) and IdP group attributes; owner transfer (#835) and departed owners (#654); the restore checklist; audit verbs; strings. Refs: `scratch/b7e/backlog/gap-v07/research-v07-gaps.md` A8.
Author
Owner

Research done (2026-11-07, at 78c814d7; scratch/b7e/backlog/research-1107.md).

Recommended first version: keep one recorded owner and add a third member role "Read + write + manage" (Box Co-owner, Seafile group admins work this way). Managers add and remove members, change roles (including other managers), set end dates, manage sharing and see or revoke every share in the space, answer join requests, rename and edit the description, deactivate and reactivate, lock and break locks. Owner and admins only: delete or restore the space and "Make owner…". The last-manager rule comes free: the owner cannot be removed or demoted and steps back only by handing over (the old owner stays as a manager in the same save). Notifications that go to the owner today go to the managers too. App-owned spaces first; directory and power-mode spaces later via a "Managers group" binding. All 52 "is owner" checks are classified in the file.

Findings: a linked Cairn group's sync re-adds members as Read + write (would demote a manager); lock-breaking uses a 60 s per-process owner cache; the role-change audit entry has no from= (the restore checklist needs it); member and role refusals have no error codes; German mixes "Eigentümer" and "Inhaber". Decisions for Nikola follow.

**Research done** (2026-11-07, at 78c814d7; `scratch/b7e/backlog/research-1107.md`). Recommended first version: keep one recorded owner and add a third member role "Read + write + manage" (Box Co-owner, Seafile group admins work this way). Managers add and remove members, change roles (including other managers), set end dates, manage sharing and see or revoke every share in the space, answer join requests, rename and edit the description, deactivate and reactivate, lock and break locks. Owner and admins only: delete or restore the space and "Make owner…". The last-manager rule comes free: the owner cannot be removed or demoted and steps back only by handing over (the old owner stays as a manager in the same save). Notifications that go to the owner today go to the managers too. App-owned spaces first; directory and power-mode spaces later via a "Managers group" binding. All 52 "is owner" checks are classified in the file. Findings: a linked Cairn group's sync re-adds members as Read + write (would demote a manager); lock-breaking uses a 60 s per-process owner cache; the role-change audit entry has no `from=` (the restore checklist needs it); member and role refusals have no error codes; German mixes "Eigentümer" and "Inhaber". Decisions for Nikola follow.
Author
Owner

Decisions (Nikola, 2026-11-07):

  • One owner plus any number of managers; new role "Read + write + manage" (DE "Lesen + Schreiben + Verwalten", managers "Verwaltende"; owner is "Eigentümer" everywhere).
  • Managers may do everything the owner does except delete or restore the space and "Make owner…"; quotas stay with admins; managers may make other managers (notified, audited).
  • The owner can't be removed or demoted and steps back only by handing over (old owner stays as manager); hand over and leave are two steps; no automatic promotion when the owner departs (admin assigns, managers listed first).
  • "Only space owners may share" includes managers; notifications to the owner go to managers too.
  • App-owned spaces in v1; directory spaces get a "Managers group" binding after launch.
  • Restore checklist gets a "Space access" row.
  • Fixes in the same batch: group sync must not demote a manager, lock rights re-checked (no 60 s cache), from= on role-change audit entries, error codes for member and role refusals, German owner term unified.
**Decisions (Nikola, 2026-11-07):** - One owner plus any number of managers; new role "Read + write + manage" (DE "Lesen + Schreiben + Verwalten", managers "Verwaltende"; owner is "Eigentümer" everywhere). - Managers may do everything the owner does except delete or restore the space and "Make owner…"; quotas stay with admins; managers may make other managers (notified, audited). - The owner can't be removed or demoted and steps back only by handing over (old owner stays as manager); hand over and leave are two steps; no automatic promotion when the owner departs (admin assigns, managers listed first). - "Only space owners may share" includes managers; notifications to the owner go to managers too. - App-owned spaces in v1; directory spaces get a "Managers group" binding after launch. - Restore checklist gets a "Space access" row. - Fixes in the same batch: group sync must not demote a manager, lock rights re-checked (no 60 s cache), `from=` on role-change audit entries, error codes for member and role refusals, German owner term unified.
Author
Owner

Mockup approved (Nikola, 2026-11-07): 1107-space-managers-mockup.html, frames A-J + dark sample (dark selected rows fixed). Open points as recommended: the owner gets a bell when someone else appoints a manager; "Verwaltende" for groups, "verwaltende Person" in singular sentences; a manager can't remove themselves in v1 (step down first); the restore checklist's "Hand over again" uses a narrow, audited admin route that only re-applies a hand-over the checklist listed; members added after the backup and members past their end date stay out of the "Space access" row (said in the handbook).

**Mockup approved** (Nikola, 2026-11-07): `1107-space-managers-mockup.html`, frames A-J + dark sample (dark selected rows fixed). Open points as recommended: the owner gets a bell when someone else appoints a manager; "Verwaltende" for groups, "verwaltende Person" in singular sentences; a manager can't remove themselves in v1 (step down first); the restore checklist's "Hand over again" uses a narrow, audited admin route that only re-applies a hand-over the checklist listed; members added after the backup and members past their end date stay out of the "Space access" row (said in the handbook).
Author
Owner

Spec decisions (Nikola, 2026-11-07; research research-b3v07-unsettled.md): role stored in the existing role field (manage, no migration; rollback turns managers into Read + write); hand-over is one record write that only goes through if the owner hasn't changed; the members POST answer changes from 204 to 200 with JSON (flagged under "read before upgrading"); spaceOwner kept one release next to the new canBreakLocks; administrators keep removing themselves (member-self applies to others); "Hand over again" on the restore checklist requires a current member; the owner's "made a manager" bell and the preference sentence approved; FR "gestionnaire", IT "gestore". Spec and plan: .superpowers/sdd/2026-11-07-b3v07/spec-1107.md, plan-1107.md. Build starts.

**Spec decisions** (Nikola, 2026-11-07; research `research-b3v07-unsettled.md`): role stored in the existing role field (`manage`, no migration; rollback turns managers into Read + write); hand-over is one record write that only goes through if the owner hasn't changed; the members POST answer changes from 204 to 200 with JSON (flagged under "read before upgrading"); `spaceOwner` kept one release next to the new `canBreakLocks`; administrators keep removing themselves (member-self applies to others); "Hand over again" on the restore checklist requires a current member; the owner's "made a manager" bell and the preference sentence approved; FR "gestionnaire", IT "gestore". Spec and plan: `.superpowers/sdd/2026-11-07-b3v07/spec-1107.md`, `plan-1107.md`. Build starts.
Author
Owner

Shipped in v0.6.403 (PR #1142), live on both dogfoods.

  • App-owned spaces have one owner plus managers. Managers can do everything except delete the space and hand it over; the five repair routes stay administrators only.
  • Members dialog: Can manage, Make owner (compare-and-set hand-over, the old owner stays a manager), Stop managing; no self-removal.
  • Managers count as owners for sharing, locks, bells, Find spaces and Activity; lock powers and delete are decided on a fresh read on every instance.
  • One name rule (NFC + case) throughout the spaces store.
  • Group sync never lowers a manager, and its removals are now audited.
  • Administration › Spaces: Managers column; Assign lists managers first; Departed users names who keeps managing.
  • Restore checklist: Space access row with Remove again, Lower again, Hand over again.
  • Directory spaces and power mode: no managers in v1 (409 space-managers-directory).
  • Read before upgrading: POST …/members answers 200 JSON. Rollback keeps the manage rows (an older version reads them as write).

After-launch items are filed separately.

Shipped in **v0.6.403** (PR #1142), live on both dogfoods. - App-owned spaces have one owner plus managers. Managers can do everything except delete the space and hand it over; the five repair routes stay administrators only. - Members dialog: Can manage, Make owner (compare-and-set hand-over, the old owner stays a manager), Stop managing; no self-removal. - Managers count as owners for sharing, locks, bells, Find spaces and Activity; lock powers and delete are decided on a fresh read on every instance. - One name rule (NFC + case) throughout the spaces store. - Group sync never lowers a manager, and its removals are now audited. - Administration › Spaces: Managers column; Assign lists managers first; Departed users names who keeps managing. - Restore checklist: Space access row with Remove again, Lower again, Hand over again. - Directory spaces and power mode: no managers in v1 (409 `space-managers-directory`). - Read before upgrading: `POST …/members` answers 200 JSON. Rollback keeps the manage rows (an older version reads them as write). After-launch items are filed separately.
Cordy closed this issue 2026-11-07 19:30:20 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1107
No description provided.