Feature: discoverable spaces and "request access" (opt-in) #929

Closed
opened 2026-10-15 22:06:23 +00:00 by Cordy · 4 comments
Owner

From the #923 research (2026-10-16, D5).

After #923, people see only the spaces they belong to. Some organisations want a directory of spaces people can ask to join. Microsoft Teams, for example, has discoverable private teams with join requests, and it is off by default.

Sketch:

  • Off by default, behind an admin policy.
  • The space owner opts in per space.
  • A discoverable space shows its name and description only, never its members or files.
  • People can request access; the owner approves or declines, with a bell item and an audit entry.
  • Never for IdP-managed spaces, whose membership lives in the directory.

Process: research first, then a mockup.

From the #923 research (2026-10-16, D5). After #923, people see only the spaces they belong to. Some organisations want a directory of spaces people can ask to join. Microsoft Teams, for example, has discoverable private teams with join requests, and it is off by default. **Sketch:** - Off by default, behind an admin policy. - The space owner opts in per space. - A discoverable space shows its name and description only, never its members or files. - People can request access; the owner approves or declines, with a bell item and an audit entry. - Never for IdP-managed spaces, whose membership lives in the directory. **Process:** research first, then a mockup.
Author
Owner

Research (2026-10-30). The full write-up with sources and VERIFIED, INFERRED and UNVERIFIED markers is in scratch/b7e/backlog/research-929.md.

Market

  • Private spaces are hidden by default everywhere; an admin switch allows discovery, owners opt in per space, people ask and owners decide.
  • Microsoft Teams: private-team discovery is a policy, off by default. Owners approve requests, and joining by code now needs approval too.
  • Slack and Google Groups keep "can be found" and "can join" as separate settings.
  • Dropbox (company-managed groups) and Nextcloud (SCIM-managed teams) do not allow requests for directory-managed groups.
  • No request flow found: OpenCloud/oCIS, Nextcloud Team folders, ownCloud 10, Seafile, Box.

Pitfalls

  • Nextcloud CVE-2021-37630: anyone could join secret circles.
  • GitLab CVE-2021-39884: a side endpoint leaked private group names.
  • 2018: thousands of Google Groups were readable by anyone.
  • Requests that reached nobody (GitLab #213653, Teams forums).
  • OWASP API6: spam through notification flows.

Cairn today

  • Most building blocks exist:
    • the membership rule and the #923 404 gate;
    • per-space settings (spacemeta) and owner-only member edits;
    • audit verbs, computed bells and session-only checks.
  • Missing:
    • the policy switch and a per-space "listed" flag;
    • a request store and a directory endpoint;
    • the UI, bells and audit verbs.
  • Several instances: the notification store rewrites the whole file, so requests must not live there. Bells are computed from the request store, and limits are counted from stored records.

Recommended design

  • Switches: an admin "Space directory" setting plus a per-space "List this space in Find spaces" toggle, both off by default.
  • Which spaces: Cairn-owned spaces only. Never directory spaces, power mode, flat mode, deactivated or deleted spaces, or spaces whose owner left.
  • What is shown: name, subtitle and description only, on separate endpoints keyed by space id. Non-members keep the #923 404 everywhere else.
  • Requesting: an optional short message; no self-join.
  • Deciding: the owner approves with Read preselected, or declines with an optional note.
  • Access and audit: browser session only, and every step is audited.
  • Size and mockup: about 2.5 days backend, 2.5 days UI and half a day of docs; 13 mockup frames.

Open questions, with my recommendations

  1. Cairn-owned spaces only: yes.
  2. Non-members see name, subtitle and description, with a preview in the owner's toggle: yes.
  3. Who browses: everyone signed in by default, or chosen groups: both in v1.
  4. Request only, never self-join: yes.
  5. The owner decides; admins can unlist but not approve: yes.
  6. On approval the owner picks the role, Read preselected: yes.
  7. Limits:
    • one pending request per person and space;
    • per person: 10 pending and 20 per day;
    • 50 pending per space;
    • requests expire after 30 days, and a declined person waits 30 days before asking again;
    • messages up to 300 characters.
  8. Switching off closes pending requests: yes.
  9. Bell only in v1; mail to the owner later (#896 now exists).
  10. Optional decline note, shown to the requester: yes.
  11. Request records deleted 90 days after the decision; the audit log keeps the facts.
  12. Browser session only: yes.
  13. A "Find spaces" button beside "New space": yes.
**Research (2026-10-30).** The full write-up with sources and VERIFIED, INFERRED and UNVERIFIED markers is in `scratch/b7e/backlog/research-929.md`. **Market** - Private spaces are hidden by default everywhere; an admin switch allows discovery, owners opt in per space, people ask and owners decide. - **Microsoft Teams:** private-team discovery is a policy, off by default. Owners approve requests, and joining by code now needs approval too. - **Slack and Google Groups** keep "can be found" and "can join" as separate settings. - **Dropbox** (company-managed groups) and **Nextcloud** (SCIM-managed teams) do not allow requests for directory-managed groups. - **No request flow found:** OpenCloud/oCIS, Nextcloud Team folders, ownCloud 10, Seafile, Box. **Pitfalls** - Nextcloud CVE-2021-37630: anyone could join secret circles. - GitLab CVE-2021-39884: a side endpoint leaked private group names. - 2018: thousands of Google Groups were readable by anyone. - Requests that reached nobody (GitLab #213653, Teams forums). - OWASP API6: spam through notification flows. **Cairn today** - Most building blocks exist: - the membership rule and the #923 404 gate; - per-space settings (`spacemeta`) and owner-only member edits; - audit verbs, computed bells and session-only checks. - Missing: - the policy switch and a per-space "listed" flag; - a request store and a directory endpoint; - the UI, bells and audit verbs. - **Several instances:** the notification store rewrites the whole file, so requests must not live there. Bells are computed from the request store, and limits are counted from stored records. **Recommended design** - **Switches:** an admin "Space directory" setting plus a per-space "List this space in Find spaces" toggle, both off by default. - **Which spaces:** Cairn-owned spaces only. Never directory spaces, power mode, flat mode, deactivated or deleted spaces, or spaces whose owner left. - **What is shown:** name, subtitle and description only, on separate endpoints keyed by space id. Non-members keep the #923 404 everywhere else. - **Requesting:** an optional short message; no self-join. - **Deciding:** the owner approves with Read preselected, or declines with an optional note. - **Access and audit:** browser session only, and every step is audited. - **Size and mockup:** about 2.5 days backend, 2.5 days UI and half a day of docs; 13 mockup frames. **Open questions, with my recommendations** 1. Cairn-owned spaces only: yes. 2. Non-members see name, subtitle and description, with a preview in the owner's toggle: yes. 3. Who browses: everyone signed in by default, or chosen groups: both in v1. 4. Request only, never self-join: yes. 5. The owner decides; admins can unlist but not approve: yes. 6. On approval the owner picks the role, Read preselected: yes. 7. Limits: - one pending request per person and space; - per person: 10 pending and 20 per day; - 50 pending per space; - requests expire after 30 days, and a declined person waits 30 days before asking again; - messages up to 300 characters. 8. Switching off closes pending requests: yes. 9. Bell only in v1; mail to the owner later (#896 now exists). 10. Optional decline note, shown to the requester: yes. 11. Request records deleted 90 days after the decision; the audit log keeps the facts. 12. Browser session only: yes. 13. A "Find spaces" button beside "New space": yes.
Author
Owner

Decision (Nikola, 2026-10-30): all 13 recommendations from the research comment are approved. Next step: a whole-page mockup.

**Decision (Nikola, 2026-10-30):** all 13 recommendations from the research comment are approved. Next step: a whole-page mockup.
Author
Owner

Mockup approved (Nikola, 2026-10-30): 929-find-spaces-mockup.html, with all its strings and open-point recommendations.

  • Turning the policy off unlists every space.
  • The owner's switch lives in Members › Requests; the admin policy in Sharing › Policy.
  • Admins see counts only.
  • Requests move to a new owner, or close and the space is unlisted when the owner leaves with no successor.
  • Adding a requester directly closes the request as approved.
  • Asking again after a withdraw or an expiry is allowed at once and counts toward the daily limit.
  • Search is server-side over name, subtitle and description.
**Mockup approved (Nikola, 2026-10-30):** `929-find-spaces-mockup.html`, with all its strings and open-point recommendations. - Turning the policy off unlists every space. - The owner's switch lives in Members › Requests; the admin policy in Sharing › Policy. - Admins see counts only. - Requests move to a new owner, or close and the space is unlisted when the owner leaves with no successor. - Adding a requester directly closes the request as approved. - Asking again after a withdraw or an expiry is allowed at once and counts toward the daily limit. - Search is server-side over name, subtitle and description.
Cordy closed this issue 2026-10-31 12:09:32 +00:00
Author
Owner

Shipped in v0.6.380 (PR #1062), live on both dogfoods (pods ready, no restarts, no new WARN lines).

  • Off by default. Administrators switch Find spaces on under Administration › Sharing › Policy, for everyone or chosen groups; switching it off asks first, unlists every space and closes every request.
  • Owners list a space and answer requests in Members › Requests: Approve (role, Read only preselected) or Decline (optional note; the person can ask again after a cooldown).
  • People open Spaces › Find spaces, search listed spaces, ask with an optional message (up to 300 characters), and withdraw.
  • Limits per person and per space; requests expire; an hourly sweep on a read-back lease closes requests of spaces that are unlisted, deactivated, deleted or without an owner.
  • Unlisted and ineligible spaces answer the byte-identical #923 404; admins see counts only, never messages.
  • Bells for owners and requesters (preference "Requests to join spaces"); data export table spaces/space-requests; seven admin-tier audit verbs; messages and notes are never logged or audited.
  • Works with #1039: approving someone whose end date passed re-adds them without a date.
  • Docs: CHANGELOG v0.6.380, spaces.md, admin-policy.md, sharing.md, account.md, data protection and export pages, deployment.md, ARCHITECTURE.md.
Shipped in **v0.6.380** (PR #1062), live on both dogfoods (pods ready, no restarts, no new WARN lines). - **Off by default.** Administrators switch Find spaces on under Administration › Sharing › Policy, for everyone or chosen groups; switching it off asks first, unlists every space and closes every request. - **Owners** list a space and answer requests in Members › Requests: Approve (role, Read only preselected) or Decline (optional note; the person can ask again after a cooldown). - **People** open Spaces › Find spaces, search listed spaces, ask with an optional message (up to 300 characters), and withdraw. - Limits per person and per space; requests expire; an hourly sweep on a read-back lease closes requests of spaces that are unlisted, deactivated, deleted or without an owner. - Unlisted and ineligible spaces answer the byte-identical #923 404; admins see counts only, never messages. - Bells for owners and requesters (preference "Requests to join spaces"); data export table `spaces/space-requests`; seven admin-tier audit verbs; messages and notes are never logged or audited. - Works with #1039: approving someone whose end date passed re-adds them without a date. - Docs: CHANGELOG v0.6.380, spaces.md, admin-policy.md, sharing.md, account.md, data protection and export pages, deployment.md, ARCHITECTURE.md.
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#929
No description provided.