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:
group: Owners of a group can create Storage Volumes for their groups. This excludes the user’s personal group.user: Single users can create Storage Volumes for themselves.all: There is no scope restriction.
Why do these settings fail to control the usage scope?
Because Storage Volumes created within a user group are usable from any groups a user is member
of, this allows by example a user of the group Apple to use their home directory while running
workflows from the group Apple.