How do "basic" permissions work?

There are a number of permissions in Modx which are described as being "basic":

• Basic "create" access on new objects
• Basic permission to "list" any object. List means to get a collection of objects.
• Basic permission to "load" any object, or be able to return it as an instance at all.
• Basic permission to remove any object.
• Basic permission to "view" any object.
• Basic save permission for any object.

What does basic mean? (...and before you laugh, just hear me out: there are 2 possible interpretations):

1: "Basic" could mean "foundational," or "base-level." Similar to: "I have a basic ability to drive (but I am not necessarily qualified to drive a tractor trailer)." Thus, a Modx user having basic "list" permission is not necessarily able to list everything.

2: "Basic" could mean "universal" or "fundamental." Similar to: "The right to vote is a basic human right; when you have it then you can vote in any election." Thus, a Modx user having basic "list" permission will be able to list absolutely anything in Modx that can be listed.

Would someone please shed some light on what "basic" means in regard to Modx permissions?

4 days 19 hours and no reply. Just in case no one else feels like replying, let me post something based on a sub-basic familiarity with the system (a familiarity acquired through the technique of hit and miss): Basic means preconditional, i.e. if you want a user to be able to save something specific, then they also need the basic permission to save as a precondition of that more specific permission.

Yes, the permissions defined in a Context Access ACL policy take precedence over any "object" policies. So they are, as you say, "preconditional."

For example, if you don't have 'save_document' permission, you can't save any document, even if you have 'save' permission for that document in a Resource Group Access ACL policy.

You might be interested in this (warning, it's about 51 minutes long): https://vimeo.com/54360208