A Viewer can access the content after being invited to a page.

An editor can create and edit content. Depending on the account-level setting “Invite and change group permissions,” editors may also be allowed to invite additional editors or provide access to viewers.
If this permission is not granted at the account level, editors will not be able to invite users.
Editors can invite viewers and editors and may also adjust existing user permissions (e.g., upgrade a viewer to editor or downgrade an editor to viewer) within projects, guidelines, and libraries, if enabled.

An owner can edit and delete the complete Style Guide/Project and invite or remove other team members.
Additionally, if the “Invite and change group permissions” setting is restricted to owners, any user who holds owner rights in a project, guideline, or library will still be able to invite users, even if they are otherwise assigned an editor role.

Note: In the Frontify DAM, only owners can edit ‘Library Settings’ and ‘Usage Settings’ and in the Template Library, only owners can upload new templates.

Manages the account and has complete control of configurations and account details. Only admins can access User Management, Targets, and Groups settings. Admins should also take care to review smart groups and organizational configurations to prevent users from unintentionally gaining broader permissions. Verifying these settings can help maintain precise control over access.

Account admins can now control which roles are allowed to invite users through the “Invite and change group permissions” setting located under Account → Required permissions.

If provisioning is enabled at the account level, admins must still approve all invitations, including those initiated by editors.

Note: Being assigned a role at the account level (e.g., viewer, editor, owner) does not automatically grant access to all projects, guidelines, or libraries. Users must be added to each specific space by an owner or editor to access its content. Users who are already in the environment but lack access to a specific project may encounter a 403 error.

Additionally, practical techniques for using the dashboard can help streamline navigation for users. Once invited, users can utilize the dashboard to view all accessible projects and libraries, promoting efficient collaboration.

Using the language switcher, the translator makes your Style Guide multilingual by translating existing text. However, the translator cannot create new content.

With viewer permission within the Workspace, the reviewer can give feedback and comment on project assets.

Account admins can define, in the account settings, who are allowed to create brands, guidelines, projects, and libraries. Account admins can also upgrade hooks based on their roles. To further refine permissions, account admins can invite users to specific projects or libraries and grant them approval rights if needed. Approval rights enable users to download assets and approve requests within a project. This ensures that each user has access relevant to their assigned role.

A new setting — “Invite and change group permissions” — is available under Account → Required permissions. This allows admins to specify which roles (e.g., editors, owners) are allowed to invite users across projects, guidelines, and libraries.

This change improves governance and gives organizations better control over who can invite collaborators without requiring admins to manually review all new invitations.

The Targets feature allows admins to create different access and viewer levels and hide some content from certain viewer groups. A common use case for this is to set up external viewers or high-level public guidelines.

Tip: For controlling access for groups or external viewers, use Targets. For individual users, make sure they are explicitly added to the project or library.