- Go to the site where you are using the Managed Navigation
- Go to a page that has an item you would like to add to the global navigation
- In my example, I will add the “Documents” document library, so I went to the “Site Content” page
- You will see the “EDIT LINKS” link to the right of your global navigation, click the “EDIT LINKS” link (remember that you need to have full control on this site to see this link)
- You can add that item as a top level navigation item or as a child navigation item of an existing item
- Click the Save button
- Repeat steps 2-5 until you have added all the items you want in your navigation
- Items can be any draggable objects in your SharePoint sites, so this includes Apps (including lists and libraries) and items (this includes list items, documents, and even people)
- For my example, I now opened the Document library and added the “My Awesome Document” under the Documents navigation item


- Now if you go to the Term Store
- Site Actions > Site Settings
- Click Go to top level site settings [Site Collection Administration], if you are not on the root site collection
- Click Term store management [Site Administration]
- Click on a Term Group that you are using for your global navigation (my example in the screen shots below is called “Intranet”)

- As you can see, the navigation items that you have dragged and dropped are now terms under your global navigation Term Set. In addition, you will notice that any pinned terms to the source term that you added now also have pinned sub terms.
- Also notice that in the Term Store you can add more children terms under the navigation terms that were added. However anything beyond three levels will not show up in the global navigation, but can be used if you are intending to use this navigation Term Set for tagging content.
Monthly Archives: March 2013
Configure a site’s Managed Navigation settings
- Go to the site where you would like to use Managed Navigation
- NOTE: if you would like to use Navigation inheritance for children sites, then make sure to perform the configuration on the top site which should have this navigation in your Site Collection (most likely your root site in the collection)
- NOTE: a navigation Term Set can only be configured once to a site, if you would like to reuse your Term Set for navigation on another peer site or another Site Collection, or even another Web Application, then you will need to create another Term Set and pin the first level terms (with children) to your existing Term Set. You can see this in the screen shot below on the Term Set “Supply Chain Navigation”.
- Go to the Navigation configuration screen in Site Settings
- Click Site Actions > Site Settings
- Click Navigation [Look and Feel]
- Click on the Managed Navigation option [Global Navigation section]
- Expand the Term Groups and select the Term Set that you would like to use for your site’s Navigation [Managed Navigation: Term Set section] or click the “Create Term Set” button to create a new Site Collection scoped Navigation Term Set

- Then click the OK button
- Go to your site and observe the Global Navigation

Create the Managed Navigation Term Set
- For single Site Collection Navigation scoped Term Sets, go to the CONFIGURE A SITE’S MANAGED NAVIGATION SETTINGS post
- NOTE: the advantages here over traditional SharePoint Navigation are minimal
- For Global Navigation scoped Term Sets, go to the Term Store
- In on premise Central Admin
- Click Application Management
- Click Manage Service Applications [Service Applications]
- Click Managed Metadata Service
- In Office 365
- Click Admin > SharePoint [SharePoint Admin Center (SPO Admin)]
- Click Term Store
- In Site Collection (on premise or Office 365):
- Click Site Actions > Site Settings
- Click Go to top level site settings [Site Collection Administration], if you are not on the root site collection
- Click Term store management [Site Administration]
- In on premise Central Admin
- Click on a Term Group that you are either a group manager or contributor on or create a new one (my example in the screen shots below is called “Intranet”)
- Create a new Term Set (my example in the screen shots below is called “Global Navigation”)
- Click on the “Intended Use” tab
- Check the “Use this Term Set for Site Navigation” option and click the Save button

- Create a new Term (my example in the screen shot below is called “Home”)
- Click on the “Navigation” tab
- Click the “Simple Link or Header” radio button [Navigation Node Type]
- Enter the URL to the a site you would like to use as a home/landing site and click the Save button
What you need to know about Managed Navigation
In 2013, if you go to Site Actions > Site Settings > Navigation (under the Look and Feel section), you will see the screenshot below. You need to have the “SharePoint Server Publishing Infrastructure” site collection feature activated to see the Navigation option. Any site that belongs to this site collection will now have the capability to use Managed Metadata based navigation, no matter which site template was used (you do not need to have a site created using the publishing site template or even have the “SharePoint Server Publishing” site feature turned on for this to be available.
You will notice the “Managed Navigation” option; this option is new in SharePoint 2013 and can provide you the following benefits.
- Allows you to create navigation menus with 3 tiers (the other options allow you no more than 2 tiers)
- A consistent navigation experience across sites, site collections, and even web applications (within a single tenant)
- Flexibility to make changes to menus across sites without duplication of effort for each site
- Ability to tag content and people with navigation items
- Friendly URLs
- Navigation item Pinning and Reusing
The only disadvantage to using the “Managed Navigation” option is that security trimming of the navigation items will no longer work. Managed Metadata Global Navigation is intended to provide a cross-site collection consistent navigation experience. Since each site collection is its own security perimeter, security trimming navigation items is not possible.


