Users can view assets in two ways: through a library page in a guideline (the frontend) or by being invited to the library itself (the backend).
Library access vs. guideline access
Guideline access (recommended for viewers): Users browse, search, and download assets in a curated guideline view.
Library access: Users access the backend DAM interface to upload, organize, or manage assets. Inviting someone as a Viewer to a library gives them direct backend access, not the guideline view.
Guideline and library permissions are separate and do not inherit between spaces. Adding or sharing a library in the backend does not automatically add it to your guideline navigation.
How do I share assets through a guideline?
To share assets with viewers, make sure the library is added as a library page, then invite them to the guideline:
Add the library page (if not already added): In your guideline, open the Navigation manager, select + under Global navigation, and add a Library page (see navigation manager).
Open the guideline and select Invite users on the bottom action bar.
Enter their email address or user group.
Select the Viewer role.
Select Invite.
How do I invite someone to a library directly or share a folder?
Only give direct library access to users who need backend access to browse, upload, or manage assets:
Direct library access: Open the library, select Invite, choose Entire library or a specific folder, select their role (Viewer, Editor, or Owner), and select Invite. See inviting team members.
Single folder access: In the invite modal, choose a specific folder instead of the entire library. Users only see that folder in a Shared folders view. See folder-level access in Frontify.
Troubleshooting: Why can’t someone see assets?
Not invited to the space: If they see a 403 error, verify they were invited to the guideline itself, not just added via Usage Overview.
Direct backend link: Viewers sent a backend library link will get an access denied or 403 error. Link them to the guideline library page instead.
Target restrictions: The library page uses targets that exclude the user’s target group.
Missing required metadata: Assets missing required custom metadata will not appear on guideline library pages.
Workflow status or expired lifecycle date: Assets may be hidden from viewers due to workflow status or an expired date.
Incomplete upload: Unprocessed or failed uploads do not display on frontend pages.
Duplicated guideline: Permissions do not transfer when duplicating guidelines; re-invite viewers to the new guideline.
