Page, Folder, and Site Access Settings
The access settings for pages and files, folders, and sites use the same options, with some minor differences between the content types. When dealing with access, think of each site as a large folder that contains all the folders and files within, with the same properties as subfolders.
Remember the principles of inheritance and precedence when configuring access settings. Access settings at the page level override those at the folder level (though if users don't have have access to the folder, they won't be able to open it to see the folders and files within).
To open page or file access settings:
- Navigate to Content > Pages.
- Find the page or file you want to edit.
- Hover over the page or file and select Edit > Access
Open the page or file and select Properties > Access.
- Navigate to Content > Pages.
- Find the folder you want to edit.
- Hover over the folder and select Edit > Access
Open the folder and hover and click its name in the breadcrumb above the page list.
- Navigate to Setup > Sites.
- Hover over the site and select Edit > Site Access.
Settings Reference GuideLink to this section
The following is a list of all available access settings, for all items in the file structure. Depending on the content type and your user level, not every option is available for editing; some settings can only be modified by Level 10 users.
|Folders and Sites||Pages||Binary Files||Level 10 only|
|Access Group||The group with rights to edit the content.||√||√||√||X|
|Approver||Require users to submit content (either the page or any files within the folder or site) to an approver for publication. Choose one user; this is the default approver. Users can choose another user to submit to (unless approver is enforced), but cannot publish on their own.||√||√||√||√|
|Enforce Approver||Select "Yes" so that users can only submit files for publication to the specified approver.||√||√||√||√|
|Bypass Approval||Choose a group that can publish content without needing an approver. Level 10 users bypass approval even if they aren't in the group.||√||√||√||√|
|Template Group||Choose which template group is available for making new content.||√||X||X||X|
|Extensions||File types can either be allowed or disallowed. Enter the extensions that you want to define (e.g. "jpg, png, gif").||√||X||X||√|
|Toolbar||Set a custom toolbar for editing content.||√||√||X||X|
|RSS Feed||Associate an RSS feed with the content. Items created from associated pages are published to that feed.||√||√||X||X|
|URL Type||Define how URLs in the content are rendered (compliant with dependency manager).
|Exclude Search||Hides the content from global search.||√||√||√||X|
|Exclude from Sitemap||Hides the content from being included in the XML sitemap.||√||√||√||√|
|Trigger Web Hooks||Toggle on to send data to the web hook URL whenever a file in the folder is published.
|Directory Variables||In addition to any inherited directory variables, define variables for the folder to control additional settings.||√||X||X||X|
Editable RegionsLink to this section
The source code of pages can be edited to add access settings to the editable regions of the page. Add
group="xxxxxx" in the
<ouc:div> tag, where
xxxxxx is the name of the group you want to have access. This can also be done to TMPL files so all pages created from that template automatically have that access setting.
If a group name is entered that doesn't match an existing group in your account, then the access is automatically restricted to administrators (level 9 and 10 users) only.