Cascading and inheritance

Access rules in Igloo communities can be set as Cascading. Cascading rules are passed down from parent pages, spaces, and channels onto anything nested beneath. This allows you to set access rules that will be applied across several levels of architecture, throughout folders and subfolders, and across entire spaces.

It is also possible to set access rules that do not cascade, allowing you to create rules that apply only in one specific area, be it a page, space or even an individual piece of content.

Another effect of cascading rules is that if something is moved in your Site Manager, it will inherit new rules based on its new location.

It is always possible to break the chain of cascading rules at any level, by disabling inheritance.

Sections in this article: 

Use cases

Creating collector pages

It is often useful to have a page that is used exclusively for organizing your site by collecting several spaces or channels underneath it. Often those spaces and channels will all have slightly different Access rules. To make this easier to set up, do not create any cascading rules on that top-level page. Instead, create a broad, non-cascading rule on that page. This will make it easy to create specific rules on all the nested items without having to disable inheritance.

Locking down access in small areas

Often, you will find that there will be small areas in your digital workplace that need tightly restricted access, but are best located in an place that does not. A common example of this is a Human Resources space, where employees need to see things like policies and procedures, but should not be able to see confidential information about other employees. This is a good place to take advantage of disabling inheritance. Just set up the area with the Access Rules that apply through most of it, then in the more private area, disable inheritance and set the more restrictive rules that you need.

Features and functionality

Setting cascading and inheritance in part of setting access rules. Below is a list of related articles:

How to disable inheritance

Disabling inheritance allows you to completely customize the access rules at any level within your digital workplace structure, regardless of rules that have been created above.

  1. Select  Actions and then Access. 
  2. In the Inherited Rules section, select Disable Inheritance. The Disable Inheritance button.
  3. Select Ok. You can now adjust your access rules as needed.

How to restore inheritance

Inheritance can be restored in an area where it has been previously disabled. Restoring inheritance will enable all cascading rules from the level above while keeping any location-specific rules that have been created. Note that if there is a conflict, the more permissive rule will take precedence.

  1. Select  Actions and then Access. 
  2. In the Inherited Rules section, select View Details.

    The View Details button.
  3. Review the rules that will be applied if the inheritance is restored. If they are appropriate, select Restore Inheritance.
    The details of disabled access rules.
  4. Select Ok. You can now adjust your access rules as needed.
    Confirmation pop-up.

Frequently Asked Questions

What rules will there be if I create a new page, space, or channel?

When creating a new page, space, or channel, that item will inherit rules from its parent location. If it is created at the root level, (i.e., it has no parent), the rules that exist for your homepage will be applied.

If inheritance is disabled and I move something, what will happen to its associated rules?

Nothing will change unless you restore inheritance. Content that moves will keep the rules that are already set.

Are Author Rule settings cascading?

Yes, they are. But, they can be adjusted at any level without disabling inheritance, down to the individual channel.

Best practices 

Avoid disabling inheritance

Try to build structures that do not need you to disable inheritance. It is both easier to maintain and more intuitive to navigate a site that has cascading permissions throughout.

Avoid making hidden pockets of access

It is possible to add rules at any point in your structure that would allow people to see areas, without being able to see their parent pages or channels. This can be confusing when trying to navigate a digital workplace. It is best to take advantage of cascading to provide a low level of access through that area, and then open it up more in the specific places people need to work, allowing them to better understand the site’s structure.