Skip to main content
Indiana Wesleyan University Support Knowledge Base

Permission Inheritance

Overview

This article explains how permission inheritance works when working with sites within the MyIWU Portal.

Inheritance

By default all objects created within a site "inherit" permissions from the site itself. This means when a user, or group is granted permissions to the site, the same permissions will then apply to all objects contained within the site.

An object can be anything within a site. Most common objects are named in the rectangles in the diagram below which shows how a site with inheritance in place functions when adding permissions

   Inheritance.png

In the image above the arrows represent the flow of the permission added. 

 

Breaking Inheritance

In some instances you may need a user to have a different permissions on various objects through out a site. For example, a user may have read access to your site, but you may need them to submit a survey to a survey list you have setup within your site. If inheritance is left in place the user would only have read access to the survey list, and thus would not be able to submit (Contribute) to your survey list.

How Breaking Inheritance Works

Inheritance can be broken on any object (rectangles in the pictures). Depending at what level you break inheritance affects how the process works. A few examples are shown below. 

Inheritance Broken on a List/Library

Inheritance2.png

Now that inheritance has been broken on our list/library we can now add new permissions to the list/library without effecting the other portions of the site.

Inheritance Broken on an Item Within a List/Library

Inheritance3.png

This scenario would allow you to set unique permissions on a single item or document in a list or library. This is useful if you want a user to have access to view all documents in a library, but only update or upload a new version of a particular document.

  • Was this article helpful?