Rules of Inheritance
So inheritance work very similarly to the way files and folders work on any normal computer operating system, except with one main difference, access to particular ‘folders’ can be switched on or off at any level to either a group of users or even just one specific user. This way if there are specific pages on a website you do not want one person or a group of people to have access to you can set a rule of inheritance to deny them access. Visa versa, if there is a section on your website that has multiple pages, yet you only want to allow someone permission to edit one of those pages, you can set it so that they can access and edit only that one page from the section. This can apply to both website pages and the assets folder.
Like your computer, you can put a folder within a folder, and place files within those folders. If you delete the top level folder you will also delete all the files within that folder i.e. any action performed on a container (the folder) will also be applied to its content (the files). What you also need to remember is that in NeWT, anything can be a container, not just folders. So for example, you could make a page on your site called ‘Contact Us’, and within that section of the site have separate pages that have individual contact details. All these individual contact pages are contained within the ‘Contact Us’ section.
NeWT works in the same way, any rule you apply to your top level folders will also filter down and apply to everything within that folder. For example, NeWT on the NDM website has this structure to access its web pages:
Start -> Website -> Content
At this point it then splits off into the top level navigation within the blue header of the website:
Home -> Research -> Graduate Studies -> Clinical Care -> Seminars -> International Activity -> About NDM -> NDM Tools
Let’s say I wanted to block a user from accessing Graduate Studies and editing any information, I could set the access level on Graduate Studies to ‘Deny’ and add either the user name of the person I don’t want to allow access to, or the entire group of users that person belongs to. Now let’s say there was one page within Graduate Studies I did want to allow this person access to edit. I would go to that page and click on the Access for that page and set it to ‘Edit’ for that specific user or the group they belong to. This way when they go into Graduate Studies, they will only have the option to edit the one page you have given them access to; they wouldn’t see the other pages in the back end (the editing side of NeWT).