There are two ways to share a collection within your Guide, Landing Page, or external site. Below are details to help you decide on the best method.
Collections Published Online
- Marking a Collection as public is ideal if you want non-logged-in users to access or download assets within a Collection. This method offers broader access and simplicity:
- You can share a public link to the Collection with anyone (internal or external) without needing to manage individual permissions.
- If you link out a public Collection in Guides or Landing pages all users with access to the Guide can view the public Collection.
- You can control whether users can download individual assets or the entire Collection.
Note
Use Custom links to create a custom-branded link to the public guide you are sharing.
Embedded Collections
- Embedding a Collection provides more granular control, making it suitable for logged-in users:
- Access is restricted to authenticated users who have Guide or Landing Page access and specific permissions for the Collection.
- You must manually share the Collection with individual users, groups, or permission profiles for them to view it.
- If users have view-only access but downloading is enabled in the Guide or Landing Pages, they can still download the Collection.
Access Restrictions for Collections
- Embedded Collections: Logged-in users can download individual assets.
- Publicly Shared Guides or Landing Pages: Non-authenticated users can only download the entire Collection at once.
Updated