Currently our only safeguard to prevent storage mistakes or unnecessary storage is to remove a user from a role with publishing rights. Why can't storage be limited just like the credit budgeting for other actions?
User storage limits are definitely needed. Once a user has publishing rights, they can publish whatever size dataset to a feature service, and the account administrators only realize that someone has published a huge dataset when their storage credit burn jumps up. We had a user publish a huge dataset which almost doubled our storage credit burn in a 24-hour period.
This is needed because while we can limit member's credit usage, the credits consumed by the data they store does not count against that quota as the org is not charged for storage on a per-user basis. The user is also not notified or made aware of the cost when they store data. Having user storage limits (assignable as a user default) would help address this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
