We want to limit how much storage each PAWS user is effectively using, enforcing our advertised resource allocation.

Each user of PAWS should be limited to (at the time of writing) 5gb of storage. We need a way of identifying

If a valid use case exists for higher storage limits, users are able to reach out / create a phab ticket and we can discuss whether flexibility is warranted.

First:

• Agree on a retention period for files
• Implement a clean up script that removes files or directories based on:
  • Directories of users who have been locked out of PAWS for longer than 30 days
  • Directories of users who haven't made changes / logged in in the past 180 days
  • Directories of users who don't have an account in PAWS / have their SUL account disabled
• Implement a lock out script that prevents writing on directories that surpass 5gb

• Update documentation to reflect file / folder size limits and how we enforce them
• Communicate new enforcement rules through cloud-announce