Access Settings


Two important concepts to keep in mind during the creation of workflows in OU Campus are the ideas of inheritance and precedence.

Inheritance explains how the system functions in terms of access settings being determined by the settings above them. Precedence explains that the settings closer to the content override any settings that may have been set above it.


When you create a new page, directory, etc., it will inherit its access settings from the parent. These settings can then be altered afterwards, if desired. If not specified otherwise, the access settings for the site can be inherited all the way down the chain to individual pages. 

Folder Structure of Inheriting Access Settings

One exception to the rule of inheritance is URL Type, as this takes the setting specified with the site record if not specifically set. On the other hand, several access settings specifically have an option for inheriting the parent settings.

Access Settings

If you want to automatically override inheritance, it can be done by assigning the access setting within a TCF. When a user creates new content with the template using that TCF, then the desired value for the access group can be assigned automatically. Likewise, the TCF can also be designed to allow a user to choose an access group at the time of new content creation.

For more information on creating TCFs, visit the Templating section.

It is important to note how inheritance works with recursive/non-recursive modification. An item inherits its parent access settings when the item is created, or if it is not specified otherwise. However, if an item has a specified access setting (such as an approver), and the parent has its settings changed non-recursively (or the item is moved to a new location and changes its parent), the items' access settings will not change. 

In essence, items inherit access settings from parents as long as they are not configured otherwise. 


Precedence is the system by which access settings for more specific items override those of more general ones. For example, a directory may have an approver assigned to it, but if a page within the directory has a different approver assigned, that setting will take precedence, and the page's approver be enforced.

The closer a setting is to the content, the greater precedence it takes. This is especially important to understand with regard to user settings.

Users are considered to have the least amount of precedence as they are furthest from the content. Therefore, if it is important to have settings based on the user, be sure that the setting is not different anywhere else within the site.

The order of precedence is as follows (in order of lowest to highest):


Additionally, access settings can be assigned to the servers, assets, templates, blogs, and other social media. However, these do not fall into the same hierarchy, as they interact with content in different ways.