Storage Volumes and Scope
We have seen that a Storage Class can restrict the Storage Volume scope within its definition. This scope governs the creation (but not the usage) of volumes, here’s the implications:
account
: Owners of an account can create Storage Volumes for their accounts. This excludes the user account.user
: Single users can create Storage Volumes for their user account only. This excludes other accounts.all
: There is no scope restriction.
Why do these settings fail to control the usage scope?
Because Storage Volumes created within a user account are usable from any accounts a user is member
of, this allows by example a user of the account Apple
to use their home directory while running
workflows from the account Apple
.