shoddy laser here and in this module would win walked through the site hierarchy, using the diagram that I have to my left to illustrate key concepts that are related to sites and sub sites,
permissions, inheritance and more. So let's take a look at the diagram to my left. What we have at the very top is what we call a top level sight.
So within the top level sight,
you have numerous elements that are unique to the top level sites, such as your users and groups. Your navigation and well is your permissions.
below is the sub site structure.
So within the sub site
by default, inherit the same users and groups the same permissions in the same navigation which exists at the top level sight. So if you have a common navigation structure that you like to have maintained throughout your top level sight on down to your sub site,
then you have by default the ability
to maintain that when you, as a content manager, create a new sub site underneath this particular structure.
using the three rectangles below, there's also additional ah feature than capabilities, which makes management of Sub cites a very powerful concept. What we have here is underneath the sub site structure, you have the ability to create additional sub sites,
so within this scenario
you have the capability to use different templates. So if you wanted to use a different template here
in a different template here in a different template hair, you have the ability to do that using the SharePoint online sites settings interface. So, in terms of permissions, if you want to, let's they have a secure area or secure sub site,
which only specific users
or specific users with access to groups can maintain. Then you can break the inheritance, as I mentioned from top level to sub site from by default, you have the ability to inherit the same permissions level navigation, so one so forth.
But in this example, if you wanted to have
a different navigational structure, or if you had a department, for example, where the there's critical data such as Social Security numbers or ah, various information that is not to be shared with the top level sight or sub sites, or if it's a very different department,
then you have the ability to break inheritance
that once inheritance is broken, it is forever broken, meaning these unique permissions will maintain. I would not be updated as changes occur in the top level or sub site. So if, for example, a new group is created,
a new group called Accountants
is created at the top level.
That group will cascade down to the sub site if permissions are inherited. But for this sub site where permissions are not inherited, that change will not be maintained within this sub site structure.
So it's important to understand that a few key concepts at the top level sight
you have the ability to create additional sub sites. Sub size can be grouped logically based on the purpose of the site and share the same navigation, say, share the same permissions and inherit those permissions. If you have a specific need to break away from
that particular structure and create
a secure area which is used for maybe a privacy or ah, I need to know basis, then you can break the inheritance and create your own custom group. So if you have
Accountants division, which is a custom group
that can be created here
and on Lee be maintained at this particular sub site level, so those changes won't cascade over to the other site now. Another key concept to keep in mind is that within each site you have the ability to choose a
default template that will be used in the management
of that particular site. SharePoint online ships with the number of templates, which are proven to be utilized within different organizations to increase collaboration and productivity. So if you wanted to use a different template for a specific business needs,
SharePoint online provides you the ability to do so at the sub site level or at the top
this is shadow DD laser, and we've just walked through the site hierarchy state soon for more information and more details within the ah