-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Org Storage Management V1 #580
Labels
feature design
This issue tracks smaller sub issues that compose a feature
Comments
@Shrinks99 split out storage usage reporting, storage quotas, and configuring/using a custom S3 bucket |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requirements
Custom Storage Buckets
Orgs of a sufficient privlage should be able to set their own S3 storage locations. This will be configured by org admins on the org settings page. Superadmins should be able to control which orgs can do this through the superadmin org settings popup.
Org Storage Limits
Superadmins should be able to set a hard cap on the maximum amount of storage space an org is allowed to use. This should also be set on the superadmin org settings popup.
Once an org has reached its allotted storage maximum any scheduled workflows should not start new crawls. New workflow creation buttons should be disabled with a tooltip explaining why. Existing crawls that have not finished should continue running until they finish (no change here!).
Changes
Tasks
The text was updated successfully, but these errors were encountered: