How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: 32.0.11.1
Is your feature request related to a problem? Please describe.
Since the default guest quota became preset-dependent, new guest accounts no longer get 0 B automatically. The guest_quota config key has a lexicon default that comes from the Quick presets configuration (Administration → Quick presets), where it is shown as "set default disk quota assigned to guest account at its creation". Its value depends on the selected preset: the Default preset uses 0 B, while organization or family presets use a non-zero quota such as 1 GB or 10 GB. So depending on the preset, freshly created guests can silently receive a non-zero quota instead of the classic 0 B.
There is no way in the UI to see this value or to change it. The only way to set it is occ config:app:set guests guest_quota "<size>", which is not discoverable — an admin has no indication that the key exists or that the default is no longer 0 B. I only found out how this quota is set at all by reading the source; it is not mentioned in the README.
Describe the solution you'd like
Add a "Default quota for new guest accounts" field to the Guests admin settings, mirroring the quota field in the Accounts management: show the currently effective value (including the preset-derived default, e.g. "Default (1 GB)") and let the admin override it — presets, Unlimited, or a typed custom size such as "500 MB". And document the setting in the README so it is discoverable without reading the code.
Describe alternatives you've considered
Setting it via occ config:app:set guests guest_quota "<size>". It works, but it is CLI-only and undiscoverable, and it does not address the underlying issue: admins are not aware that the preset now drives a non-zero default.
Additional context
The preset-derived default comes from the guests config lexicon (GUEST_DISK_QUOTA); the value is applied to each guest on creation by GuestManager. Surfacing it in the UI and documenting it in the README closes the gap between the new preset-driven default and what an admin can actually see and control.
How to use GitHub
Feature request
Which Nextcloud Version are you currently using: 32.0.11.1
Is your feature request related to a problem? Please describe.
Since the default guest quota became preset-dependent, new guest accounts no longer get 0 B automatically. The
guest_quotaconfig key has a lexicon default that comes from the Quick presets configuration (Administration → Quick presets), where it is shown as "set default disk quota assigned to guest account at its creation". Its value depends on the selected preset: the Default preset uses0 B, while organization or family presets use a non-zero quota such as1 GBor10 GB. So depending on the preset, freshly created guests can silently receive a non-zero quota instead of the classic0 B.There is no way in the UI to see this value or to change it. The only way to set it is
occ config:app:set guests guest_quota "<size>", which is not discoverable — an admin has no indication that the key exists or that the default is no longer 0 B. I only found out how this quota is set at all by reading the source; it is not mentioned in the README.Describe the solution you'd like
Add a "Default quota for new guest accounts" field to the Guests admin settings, mirroring the quota field in the Accounts management: show the currently effective value (including the preset-derived default, e.g. "Default (1 GB)") and let the admin override it — presets, Unlimited, or a typed custom size such as "500 MB". And document the setting in the README so it is discoverable without reading the code.
Describe alternatives you've considered
Setting it via
occ config:app:set guests guest_quota "<size>". It works, but it is CLI-only and undiscoverable, and it does not address the underlying issue: admins are not aware that the preset now drives a non-zero default.Additional context
The preset-derived default comes from the guests config lexicon (
GUEST_DISK_QUOTA); the value is applied to each guest on creation byGuestManager. Surfacing it in the UI and documenting it in the README closes the gap between the new preset-driven default and what an admin can actually see and control.