As of MM5.6.1, the way that collection-sharing has changed. This document aims to explain how the system actually works, not how it should work.
...
Let’s say that we have three collections: Root collection, Sub collection, and Sub sub collection - where, Sub collection is in Root collection, and Sub sub collection is in Sub collection.
On Root-collection, the metafields A and B have been shared with me.
Hence in collections Root collection, Sub collection, and Sub sub collection I now have access to see + live-export metafields A and B
On Sub collection, the metafields B and C have been shared with me.
Hence in collections Sub collection and Sub sub collection I now have access to see + live-export metafields A + B + C
On Sub sub collection, the metafields C and D have been shared with me.
Hence in Sub sub collection I now have access to see + live-export metafields A + B + C + D
Recap
Root collection grants me access to see + live-export A + B
Sub collection grants me access to see + live-export A + B + C
Sub sub collection grants me access to see + live-export A + B + C + D
...
Now, when I multi-download/live-export Root collection, it'll download all assets in Root collection, Sub collection, and Sub sub collection with the metafields A + B.
Multi-downloading Sub collection will download all assets in Sub collection and Sub sub collection with the metafields A + B + C.
Multi-downloading Sub sub collection will download all assets in Sub sub collection with the metafields A + B + C + D.
...
Let’s say that we have the same three collections again: Root collection, Sub collection, and Sub sub collection - where they’re still the following: Sub collection is in Root collection, and Sub sub collection is in Sub collection.
On Root collection, there is one video asset
On Sub collection, there is one PDF asset
On Sub sub collection, there is one image asset
...
Root collection
When multi-downloading Root collection, I will be presented with the option to choose one or more qualities for “Videos” that my user has access to. I do not have the option to select qualities for either PDFs or Images. I select “quality=mp4_480”, and download:
...
Sub collection
When multi-downloading Sub collection, I will be presented with the option to choose one or more qualities for “PDF” that my user has access to (usually only original for PDF). I do not have the option to select qualities for Images. I select “quality=original” and download:
...
Sub sub collection
When multi-downloading Sub sub collection, I will be presented with the option to choose one or more qualities for “Images” that my user has access to. I select “quality=jpeg small” and “quality=jpeg big” and download:
...
User share v / User share > | View | Edit | Admin |
|---|---|---|---|
View | View | Edit | Admin |
Edit | - | Edit | Admin |
Admin | - | - | Admin |
We have the following unique scenarios:
User View + User View = View
User View + User Edit = Edit
User View + User Admin = Admin
User Edit + User Edit = Edit
User Edit + User Admin = Admin
User Admin + User Admin = Admin
Link share v / User share > | View | Edit | Admin |
|---|---|---|---|
View | View | Edit | Admin |
As [User] and [Group] are fundamentally the same, and [Link] and [Email] are fundamentally the same - thus, we only have to make one comparison. As [Link] and [Email] always will only share as View, we have the following unique scenarios:
Link View + User View = View
Link View + User Edit = Edit
Link View + User Admin = Admin
Group > | View |
|---|
As [Group] uses the exact same logic as [User], only one is needed to validate this. Hence, only sharing [Group] as View is sufficient
Group View = View
Email> | View |
|---|
As [Email] uses the exact same logic as [Link], only one is needed to validate this. Hence, only sharing [Email] as View is sufficient
Email = View
Sharing a collection with the same user multiple times - both as child and as parent
...
User share Child v / User share Parent > | View | Admin |
|---|---|---|
View | View on child View on parent | Admin on child View on parent |
Admin | Admin on child Admin on parent | - |
Please note that Edit is not added here, as it will function the same as View + Admin.
For example, we have two collections: Root collection and Sub collection, where Sub collection is a child of Root collection.
When sharing Root collection as View (Share A), and then sharing Sub collection as Admin (Share B), you will have View rights on Root collection, and Admin rights on Sub collection, regardless of how you access these collections. So, as mentioned earlier, when you have a collection (Sub collection) shared with you, both as the root (Share B) + as the child (Share A), you will have two ways of entering it from the Collections menu. One where you can access it directly (go directly to Sub collection, Share B), and one where you have to go through its parent folder (first Root collection and then Sub collection, Share A).
Regardless of which way you access Sub collection, you will have Admin rights.
The unique scenarios:
User parent View + User child View =
View on the parent
View on the child
User parent Admin + User child View =
Admin on the parent
Admin on the child
User parent View + User child Admin =
View on the parent
Admin on the child
Fields in use as of 5.6.2
...