Space quota notifications in the bell (admins; warn % + full); owner-set limits declined #801

Closed
opened 2026-09-28 03:57:28 +00:00 by Cordy · 5 comments
Owner

Follow-up to #767, which ships admin-only space caps with no notifications. This issue decides whether space owners should get either of these, and in what form. It needs a decision before any implementation.

What competitors do (researched 2026-09-28)

Product Who sets a space/team-folder cap Notifications
OpenCloud The Space administrator role (an instance-level role, not the space's own manager) via "Edit quota" in the top bar or context menu: preset sizes or a custom value (docs). A Space Manager (member role) manages memberships but not quota. No threshold notifications documented. The desktop client has an open issue asking for a clear "insufficient space quota" error (opencloud-eu/desktop#245).
oCIS Space admins, via a dedicated permission Drive.ReadWriteQuota.Project. The space quota is independent of the user storage quota (spaces docs). None documented.
Nextcloud Team folders Instance admins only. Not built in. Open request for 80/90/95/100 % emails to the folder's "owner" (groupfolders#4346). The maintainer's reply: notify admins only, and the real gap is that the quota isn't shown when navigating the folder (groupfolders#44).
Google shared drives Workspace admins, per org unit. Managers can only free space by moving or deleting. Managers of drives over the limit receive reminder emails listing those drives. When over the limit, nobody can add files or edit existing ones.
Seafile Admins only. Not built in (long-standing forum request).

Takeaways

  • Nobody lets an ordinary space owner raise their own cap. Where delegation exists (OpenCloud, oCIS), it is a separate, admin-granted role or permission.
  • Threshold notifications are the most-requested missing feature across the field. Google is the only one shipping them, and it sends them to the people who can act (managers, who can free space).

Options to decide

  1. Owner-set limits
    • (a) Never; admin only (status quo after #767).
    • (b) Owners may lower the cap below the admin's ceiling, e.g. to keep a team tidy. Never raise it.
    • (c) A delegated "space quota" admin permission, like oCIS Drive.ReadWriteQuota.Project. Only makes sense once Cairn has finer admin roles.
    • Recommendation: (a) now, revisit (c) if/when admin roles are split.
  2. Notifications, using the existing notify pipeline and per-user notification matrix:
    • Recipients: the space owner(s) plus instance admins. Members get nothing beyond the upload error.
    • Thresholds: 90 % and 100 %. Send once per threshold crossing, and re-arm only after usage drops back below it (the groupfolders#4346 anti-spam rule).
    • Channels: in-app bell + email, controllable in the notification-preferences matrix as a new "Space storage" row.
    • Detection: piggyback on the existing space-size sweep, plus the live enforcement cache when a write is refused (the 100 % event fires on the first refused write).
  3. Display for members (the groupfolders#44 lesson): #767b already shows "X of Y" to members; keep that as the baseline.

Deliverable of this issue: a decision comment, then implementation issues cut from it.

Follow-up to #767, which ships **admin-only** space caps with no notifications. This issue decides whether space owners should get either of these, and in what form. It needs a decision before any implementation. ## What competitors do (researched 2026-09-28) | Product | Who sets a space/team-folder cap | Notifications | |---|---|---| | **OpenCloud** | The **Space administrator** role (an instance-level role, not the space's own manager) via "Edit quota" in the top bar or context menu: preset sizes or a custom value ([docs](https://docs.opencloud.eu/docs/user/spaces/space-quota/)). A Space *Manager* (member role) manages memberships but not quota. | No threshold notifications documented. The desktop client has an open issue asking for a clear "insufficient space quota" error ([opencloud-eu/desktop#245](https://github.com/opencloud-eu/desktop/issues/245)). | | **oCIS** | Space admins, via a dedicated permission `Drive.ReadWriteQuota.Project`. The space quota is independent of the user storage quota ([spaces docs](https://owncloud.dev/ocis/storage/spaces/)). | None documented. | | **Nextcloud Team folders** | Instance admins only. | **Not built in.** Open request for 80/90/95/100 % emails to the folder's "owner" ([groupfolders#4346](https://github.com/nextcloud/groupfolders/issues/4346)). The maintainer's reply: notify admins only, and the real gap is that the quota isn't shown when navigating the folder ([groupfolders#44](https://github.com/nextcloud/groupfolders/issues/44)). | | **Google shared drives** | Workspace admins, per org unit. Managers can only free space by moving or deleting. | Managers of drives over the limit receive reminder emails listing those drives. When over the limit, nobody can add files or edit existing ones. | | **Seafile** | Admins only. | Not built in (long-standing forum request). | **Takeaways** - Nobody lets an ordinary space owner *raise* their own cap. Where delegation exists (OpenCloud, oCIS), it is a separate, admin-granted role or permission. - Threshold notifications are the most-requested missing feature across the field. Google is the only one shipping them, and it sends them to the people who can act (managers, who can free space). ## Options to decide 1. **Owner-set limits** - (a) Never; admin only (status quo after #767). - (b) Owners may *lower* the cap below the admin's ceiling, e.g. to keep a team tidy. Never raise it. - (c) A delegated "space quota" admin permission, like oCIS `Drive.ReadWriteQuota.Project`. Only makes sense once Cairn has finer admin roles. - Recommendation: (a) now, revisit (c) if/when admin roles are split. 2. **Notifications**, using the existing notify pipeline and per-user notification matrix: - **Recipients:** the space owner(s) plus instance admins. Members get nothing beyond the upload error. - **Thresholds:** 90 % and 100 %. Send once per threshold crossing, and re-arm only after usage drops back below it (the groupfolders#4346 anti-spam rule). - **Channels:** in-app bell + email, controllable in the notification-preferences matrix as a new "Space storage" row. - **Detection:** piggyback on the existing space-size sweep, plus the live enforcement cache when a write is refused (the 100 % event fires on the first refused write). 3. **Display for members** (the groupfolders#44 lesson): #767b already shows "X of Y" to members; keep that as the baseline. Deliverable of this issue: a decision comment, then implementation issues cut from it.
Author
Owner

Decisions (Nikola, 2026-09-28)

Owner-set limits: no. Instance admins own the infrastructure, know the real disk capacity, and manage the available space. Caps stay admin-only (option a); no delegated role.

Notifications: yes, bell only. There is no mail service; the notification bell already exists.

  • Recipients: instance admins only.
  • Threshold: follows the admin's "Warn people at" percentage (Storage & quotas › Limits), plus full (usage ≥ limit, when uploads are refused). Warn at empty or 0 (#815) means no early warning; "full" still notifies.
  • Preference: a new "Space storage" row in the notification preferences (the #755 mute list), on by default, can be muted.
  • Scope: spaces only; personal storage keeps its existing warning banner.

Implementation shape (for the plan/mockup):

  • The bell feed is derived, not queued. A capped space at or above the threshold yields an item while the condition holds, and it disappears once space is freed or the limit is raised.
  • It needs a small per-space "crossed at" timestamp, so the item has a stable time for the seen/unread watermark and doesn't re-appear as new on every poll.
  • Evaluated from the live quota usage (SpaceUsage), for capped spaces only.

Next: mockup of the bell item + the preference row, before code.

## Decisions (Nikola, 2026-09-28) **Owner-set limits: no.** Instance admins own the infrastructure, know the real disk capacity, and manage the available space. Caps stay admin-only (option a); no delegated role. **Notifications: yes, bell only.** There is no mail service; the notification bell already exists. - **Recipients:** instance **admins only**. - **Threshold:** follows the admin's **"Warn people at"** percentage (Storage & quotas › Limits), plus **full** (usage ≥ limit, when uploads are refused). Warn at empty or 0 (#815) means no early warning; "full" still notifies. - **Preference:** a new "Space storage" row in the notification preferences (the #755 mute list), **on by default**, can be muted. - **Scope:** spaces only; personal storage keeps its existing warning banner. **Implementation shape (for the plan/mockup):** - The bell feed is derived, not queued. A capped space at or above the threshold yields an item while the condition holds, and it disappears once space is freed or the limit is raised. - It needs a small per-space "crossed at" timestamp, so the item has a stable time for the seen/unread watermark and doesn't re-appear as new on every poll. - Evaluated from the live quota usage (`SpaceUsage`), for capped spaces only. Next: mockup of the bell item + the preference row, before code.
Cordy changed title from Space quota: owner-set limits and quota notifications (research + decision) to Space quota notifications in the bell (admins; warn % + full); owner-set limits declined 2026-09-28 17:44:25 +00:00
Author
Owner

Mockup review (2026-09-28), mockup-801-space-notifications.html:

  1. Click target: Administration › Spaces (only admins get these). To make that landing useful, the admin Spaces table gains per-row limit + current usage:

    • the Size column shows "X of Y" with the same 3px meter as the overview (amber from the warn %, red when full);
    • uncapped rows keep the plain size;
    • live usage comes from /spaces quotaUsed.

    Clicking a bell item opens that page, scrolls to the space's row and briefly highlights it. Admins can scan every space's allocation in one place instead of going back and forth with the bell.

  2. Titles: " is almost full" / " is full" approved.

  3. Grey bell icons: the fix (#bellmenu .bico svg{color:inherit}) ships with #801 for all bell items.

Next: an addendum mockup of the admin Spaces table + the landing highlight, before code.

**Mockup review (2026-09-28), `mockup-801-space-notifications.html`:** 1. **Click target:** **Administration › Spaces** (only admins get these). To make that landing useful, the admin Spaces table gains per-row **limit + current usage**: - the Size column shows "X of Y" with the same 3px meter as the overview (amber from the warn %, red when full); - uncapped rows keep the plain size; - live usage comes from `/spaces` `quotaUsed`. Clicking a bell item opens that page, scrolls to the space's row and briefly highlights it. Admins can scan every space's allocation in one place instead of going back and forth with the bell. 2. **Titles:** "<space> is almost full" / "<space> is full" approved. 3. **Grey bell icons:** the fix (`#bellmenu .bico svg{color:inherit}`) ships with #801 for all bell items. Next: an addendum mockup of the admin Spaces table + the landing highlight, before code.
Author
Owner

Addendum mockup greenlit (2026-09-28): mockup-801b-admin-spaces-usage.html.

  • Admin › Spaces: Size → "Storage used"; capped rows show the overview meter; uncapped rows keep the plain size; column 140px, right-aligned; live figures for capped rows.
  • A bell click lands there, scrolls to the row and highlights it briefly.
  • Amber point follows "Warn people at" when set (e.g. 80 % → amber from 80 %), falling back to 90 % when it's empty or 0, everywhere the meter appears. The colour and the notification always agree.

Implementing now.

**Addendum mockup greenlit (2026-09-28):** `mockup-801b-admin-spaces-usage.html`. - Admin › Spaces: Size → "Storage used"; capped rows show the overview meter; uncapped rows keep the plain size; column 140px, right-aligned; live figures for capped rows. - A bell click lands there, scrolls to the row and highlights it briefly. - **Amber point follows "Warn people at"** when set (e.g. 80 % → amber from 80 %), falling back to 90 % when it's empty or 0, everywhere the meter appears. The colour and the notification always agree. Implementing now.
Cordy closed this issue 2026-09-28 18:38:07 +00:00
Author
Owner

Shipped in v0.6.308 (PR #818, CI green; go test ./... passes, web 309/309), with clean boots on both dogfoods. Live check pending a sign-in after the redeploy.

Shipped in **v0.6.308** (PR #818, CI green; `go test ./...` passes, web 309/309), with clean boots on both dogfoods. Live check pending a sign-in after the redeploy.
Author
Owner

Verified live on Bao (v0.6.308) with temporary settings, all restored afterwards:

  • Full: a 3 MiB cap on Fall 3 (≈3.3 MB used).
    • After the 45 s feed cache: space-full Fall 3 3465375/3145728, unread.
    • The real bell shows the red icon and "Fall 3 is full · 3.3 MB of 3 MB · uploads refused ·
  • Click-through: a real click on the item → #admin/spaces, Fall 3 row highlighted and scrolled into view.
    • Header reads "Storage used".
    • Meters on the capped rows: app-owned-space and test 0 B of 3 GB (ok), Fall 3 3.3 MB of 3 MB (over).
  • Almost full: warn 90 % + a 3.5 MiB cap (94 %) → space-warn Fall 3; the overview cell is amber (spq-warn).
  • Amber follows the warn %: at warn 95 % the same 94 % space reads spq-ok. The old fixed 90 % rule would have kept it amber.
  • Preference: "Space storage" is the last row in Account › Preferences › Notifications, on by default, with the agreed description.
  • Cleanup: Fall 3 cap removed; warn back to 0. Per-user, instance, new-space default and the two 3 GiB caps are unchanged.
**Verified live on Bao (v0.6.308)** with temporary settings, all restored afterwards: - **Full:** a 3 MiB cap on Fall 3 (≈3.3 MB used). - After the 45 s feed cache: `space-full Fall 3 3465375/3145728`, unread. - The real bell shows the red icon and "Fall 3 is full · 3.3 MB of 3 MB · uploads refused · <time>". The lock item's icon now shows its tint too (the colour fix). - **Click-through:** a real click on the item → `#admin/spaces`, Fall 3 row highlighted and scrolled into view. - Header reads "Storage used". - Meters on the capped rows: app-owned-space and test `0 B of 3 GB` (ok), Fall 3 `3.3 MB of 3 MB` (over). - **Almost full:** warn 90 % + a 3.5 MiB cap (94 %) → `space-warn Fall 3`; the overview cell is amber (`spq-warn`). - **Amber follows the warn %:** at warn 95 % the same 94 % space reads `spq-ok`. The old fixed 90 % rule would have kept it amber. - **Preference:** "Space storage" is the last row in Account › Preferences › Notifications, on by default, with the agreed description. - **Cleanup:** Fall 3 cap removed; warn back to 0. Per-user, instance, new-space default and the two 3 GiB caps are unchanged.
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#801
No description provided.