Composer permissions control which admin groups can view, edit, publish, and delete pages, set at three levels: Global (default rights for a group), Page (overrides for a specific page), and Branch (overrides for an entire branch). Admin level is the highest tier and adds access to the Permissions tab, Domain settings, and Page History Log.
đź’ˇQuick answers
- What are the three levels of Composer permissions? Global (default rights for the whole site), Page (overrides for a specific page), and Branch (overrides for all pages in a branch).
- What is the difference between View & Edit and View, Edit & Publish? View & Edit lets users make and save changes but not publish them; View, Edit & Publish adds the ability to publish and unpublish pages.
- Which permission level is required to delete pages? View, Edit, Publish & Delete, which is the level above standard Publish.
- Where are Global permissions set? In Composer > Permissions tab; choose a permission level for each admin group in each component column.
- How do you override permissions for a specific page? Open the page in Composer, click the Settings gear in the bottom-left corner, select the Permissions tab, and adjust the dropdown for the relevant admin group.
In this article, we’ll describe the process for granting permissions within Composer.
Define Composer rights
Before an admin group can edit pages, ensure that Composer is enabled on the group’s Admin Users settings in the Admin Users module.
Assign admin groups different rights to view, edit, publish, and delete pages in Composer when you set permissions with the following levels within Composer: Global Level, Page Level, and Branch Level.Â
Set Global Level permissions
Global permissions are set per admin user group. These are the default rights that admins in this group have to edit pages on the website.
It's a good idea to only grant Edit-level rights to admin users who are actually responsible for editing site pages. Many admins have other responsibilities that don't impact the front end of the website, and those users don't necessarily need to have page editing privileges.
On the main Composer menu, select Permissions.Â
Choose default levels for each admin group under each column that represents a different component of Composer.
- Not Allowed means the component won't be visible on the main Composer menu. Users won't be allowed to see the configuration of a page; only the public-facing page itself (unless it is access-controlled). Use this setting to hide sensitive information like portal configurations from those with Composer access.
- View means this item can be "seen" but without the Compose toggle and hover menus. Users can only see the component, preview it on mobile or desktop views, and see the publication status.
- View & Edit allows users to make changes, but not to publish those changes. Users can create new pages, banners, and themes. This level allows for the ability to move pages within the site tree, change/remove the page's theme, and roll back the page to the last published version.
- View, Edit & Publish has all of the same permissions as above, with the added ability to publish and unpublish pages. For users with "View, Edit & Publish" settings, only deleting is not an option. In addition, users can create new shared elements at this level.
-
View, Edit, Publish & Delete includes the "delete" option, in addition to all other features of the other levels.
- can view the Page History Log
-
Admin level users cannot change permissions for their own group, but can do all of the above as well as the following additional tasks:
- see and make changes to the Permissions tab on the main Composer menu and on page and banner settings.
- can grant the ability to move pages from branch to branch
- can view the Page History Log
- can view and adjust Domain settings
Set Page Level permissions
You may want to override the default Global permissions for a page or group of pages, to restrict them from general admins, or to allow only certain users to edit them.
To change from the default permissions for a specific page, navigate to that page, select the page, and select the Settings gear from bottom left corner of that page.
Select the Permissions tab on the Page Settings window that pops up.
Find the admin group whose permissions you want to change, and choose the new setting from the dropdown menu.
- Not Allowed means the page won't be visible in Composer. Users won't be allowed to see the configuration of a page; only the public-facing page itself (unless it is access-controlled). Use this setting to hide sensitive information like portal configurations from those with Composer access.
- View means this page can be "seen" but without the Compose toggle and hover menus. Users can only see the page, preview it on mobile or desktop views, and see the publication status.
- View & Edit allows users to make changes on a particular page, but not to publish those changes. Users can create new pages, banners, and themes. This level allows for the ability to move pages within the site tree, change/remove the page's theme, and roll back the page to the last published version.
- View, Edit & Publish has all of the same permissions as above, with the added ability to publish and unpublish pages. For users with "View, Edit & Publish" settings, only deleting is not an option. In addition, users can create new shared elements at this level.
- View, Edit, Publish & Delete includes the "delete" option, in addition to all other features of the other levels.
- Admin-level users can do all of the above and are able to see and make changes to the Permissions tab on the main Composer menu and on page and banner settings. They cannot change permissions for their own group. This level also grants the ability to move pages from branch to branch and view the Page History Log.
Set Branch Level permissions
Permissions can also be applied to an entire branch of the site. Hover over the desired branch and choose the Settings option.
Go to the Permissions tab there, and adjust the levels in the same way as page-level permissions. Permissions set at the branch level will apply to all of the pages in that branch.
Comments
Please Sign in to leave a comment if you don't see the comment box below.