Content Comparison

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 video 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 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 my user has access to. I select “quality=jpeg small” and “quality=jpeg big” and download:

...

• Like the users, all groups you add will receive their own individual share.

• Users in groups in groups (and users in groups in groups in groups ad infinitum) will all receive the same rights to the collection and its sub - collections.

• You can group share to a group (or group in group) that the owner is already a part of.

• New users added to the group after the share has been made, will instantly get access to the collection - , though they just will not get the initial sharing email and notification, so the [Message] will not be visible to them.

• Same as for [Users] you cannot share a collection with the same group twice. Again, if you add multiple groups when sharing, and e.g. one already has received the collection share, the UI will show an error, but all valid groups will have it shared with them.

...

You can update all shares. The things elements you can edit on existing shares, are exactly the same as when you created the share the first time.

Upon pressing “Update”‘Update’, the recipients will instantly have their rights changed. No notifications nor or emails will be sent.

Resend invite

Resending the invite will only send them a new mail, not a notification.

...

To change the message of the “Resend invite“ ‘Resend invite’ function, you will have to first go edit the message from the “Edit share“‘Edit share’.

Disabling sharing externally [Link, Email]

Higher - level users (e.g. admins) have the option to disable external sharing in General → General settings → Collections. On In here you have the toggle “Enable ‘Enable external collection sharing“ sharing’ which, if disabled, will remove the [link] and [email] sharing tabs from all users.

...

Please be aware that, regardless of whether you share with e.g. View rights first, and Admin rights later - or - Admin rights first, and then View rights later - the result will be the same; the highest access will be applied. (Admin in this example).

Sharing a collection with the same user multiple times

We have the following unique scenarios:

1. User View + User View = View

2. User View + User Edit = Edit

3. User View + User Admin = Admin

4. User Edit + User Edit = Edit

5. User Edit + User Admin = Admin

6. User Admin + User Admin = Admin

As [User] and [Group] are fundamentally are 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:

1. Link View + User View = View

2. Link View + User Edit = Edit

3. Link View + User Admin = Admin

As [Group] uses the exact same logic as [User], only one is needed to validate this. Hence, only sharing [Group] as View is sufficient

1. Group View = 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

1. Email = View

Sharing a collection with the same user multiple times - both as

...

child and as

...

parent

The above scenarios were all were for one collection shared in multiple ways. You also have the option to share collections as a part of other collections.

Please note that Edit is not added here, as it will function the same as View + Admin.

So, let’s for example say that For example, we have two collections: Root - collection and Sub - collection, where Sub - collection is a child of Root - collection.

Sharing 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 said 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:

1. User parent View + User child View =

   1. View on the parent

   2. View on the child

2. User parent Admin + User child View =

   1. Admin on the parent

   2. Admin on the child

3. User parent View + User child Admin =

   1. View on the parent

   2. Admin on the child

Fields in use as of 5.6.2

...