| View file | ||||
|---|---|---|---|---|
|
...
Collections are individual. This means that every collection created by a specific user will only be visible to this user, unless he/she decides they decide to share it with another user.
Sharing collections
Collections shared with other users are marked with the following symbol:
When you share collections the user shares a collection, the resulting link that the recipient receives will have an access key attached to it. This key is what grants this user access to the collection, meaning that the recipient will not have to log in in order to access the collection.
On systems where In case of systems in which the login method is set to "login required", one has to set the config manager setting "Allow shared collection users to bypass login required screen: to " to true", in order for the recipient to access the collection without having to log in.
When you add, removethe user adds, removes, or update updates assets in a collection you that have been shared, the recipient will be able to see these changes if when they access the collection again. The recipient will not be notified of changes to the collection.
If you choose the user wants to share a collection to e.g. social media, this collection will function in exactly the same way as in case of sharing to with a single person.
If you access the user accesses a collection shared to e.g. social media - you they sometimes will have to be logged out of your their own user profile in order to see learn what external users see. This usually means that you may the user might be able to access assets in a collection that external users cannot sessee. This, however, only happens if one has explicitly removed the access rights for external users to an asset which happens to be in the collection.
Currently, when sharing collections to external sites - one has can choose to enable Server Side Rendering (SSR) which will make collections shared have better looking thumbnails when presented on social media. This, however, has the side effect, i.e. Media Manager in general will become noticeably slower, which is why this option is not enabled by default. To enable it, EnablePrerendering must be set to "true" in the Media Manager's appsettings.json file.
Sorting
It is possible to change the sorting order of the collections' list. The collections can be sorted either by name or by the order in which they were created. It can be done:
- from the drop-down list under the Collections menu - by selecting an option from the list that opens upon hovering over Order:
- in the main window view - by using the button in the upper right corner:
Other information
There are three methods of adding assets to the collection:
...