Feature Request: Per-User Storage Quotas

[devkit415]

Users can mark recordings as “never delete,” under "Tags & Folders", "Create/Edit Tag", "Retention & Auto-Deletion", "Protect from Auto-Deletion (Infinite Retention)", which bypasses the global retention policy.

Without a storage limit, a user could accumulate recordings indefinitely and eventually consume all available disk space.

The existing token and transcription budgets already provide a model for per-user resource limits under "Edit User", "Monthly Token Budget", "Monthly Transcription Budget (minutes)", but I miss an equivalent limit for storage.

Requested Feature

Add an optional total storage quota for each user, measured in megabytes.

When a user uploads a recording, the system should check whether the upload would exceed their quota. If it would, the upload should be rejected with a clear message showing their current usage, remaining storage, and quota.

Recordings marked for permanent retention should still count toward the quota. Users without a configured quota should remain unrestricted.

Administrators should be able to configure each user’s quota and view their current storage usage. On the other side, users should be able to see their own usage and remaining storage in a suitable location.

Possible Implementation

The following are just implementation ideas. Please choose the approach that best fits the architecture:

• Add an optional storage_quota_mb field to the user model. A null value would mean no limit.
• Include the quota in the relevant admin API responses and requests.
• Add a storage quota field and usage indicator to the admin UI.
• Enforce the quota before saving a new recording, returning an appropriate error if the limit would be exceeded.
• Display storage usage and remaining quota to users.
• Optionally define a DEFAULT_USER_STORAGE_QUOTA_MB environment variable for new users.

Expected Behavior

• Administrators can set, update, or remove a user’s storage quota.
• Uploads that would exceed the quota are rejected.
• Permanent-retention recordings count toward the quota.
• Users without a quota remain unrestricted.
• Administrators and users can view relevant storage usage information.
• Existing retention and automatic-deletion behavior continues to work as before.

[murtaza-nasir]

Thank you for the suggestion. Storage quotas are added in v0.10.13-alpha. An administrator can set a quota for each user in Edit User, with a default for new accounts in System Settings; users without one have no limit. An upload that would exceed the quota is refused with the user's current usage and limit, and each user sees their usage under Account. Recordings protected from auto-deletion count toward the quota. A recording made in the app is never refused once it has started.

[devkit415]

You’re a legend! Thank you for implementing these improvements so quickly! 👍