---
title:        "Tips and Tricks: Hiding content in the content tree"
description:  "Kentico CMS 6.0 brings you a great new feature that allows you to only display content to your editors if they have the needed Read permissions. To enable this feature, simply follow these steps."
url:          https://www.jeroenfurst.nl/blog/Tips-and-Tricks-Hiding-content-in-the-content-tree
date:         2012-04-03
category:     Security and permissions
tags:         [Security and permissions]
reading_time: 1
---

# Tips and Tricks: Hiding content in the content tree

> Kentico CMS 6.0 brings you a great new feature that allows you to only display content to your editors if they have the needed Read permissions. To enable this feature, simply follow these steps.

Kentico CMS 6.0 brings you a great new feature that allows you to only display content to your editors if they have the needed **Read** permissions. To enable this feature, simply follow these steps:

## Step 1: Enable the "Check document permissions" setting

Go to Site Manager, Settings, and select your site. In the Content, Content management section find and enable the "Check document permissions settings":
 
 ![doc_permissions_setting.png](~/getContentAsset/0a9f0351-01e2-41d3-93e7-45ab6bb04939/310c1ea5-13ca-4d75-95a0-620f51989b44/95c9e9ea_doc_permissions_setting.png.png)
 
 According to the help, this setting does the following:
 
 *"If enabled, only documents for which the current user has the **Read** permission are displayed in the content tree (in **CMS Desk -> Content**, in document listings and in various dialogs where the content tree is displayed)."*
 
 While this is simply awesome and a must have, please take notice of the following information:
 
 *"In case that a user doesn't have the **Read** permissions for any document at all, a message is displayed instead of the content tree, saying that they are not authorized to modify any document. If a user has the **Read** permission for a child document but not for its parent, the child document is not displayed as well."*
 
 In other words: the user always needs **Read** access to the parent node.

## Step 2: Configure the document permissions

[![permissions.png](~/getattachment/Blog/April-2012/Tips-and-Tricks-Hiding-content-in-the-content-tree/permissions.png.aspx?width=680&height=346)](~/getattachment/Blog/April-2012/Tips-and-Tricks-Hiding-content-in-the-content-tree/permissions.png.aspx)
 
 Notice that I denied Andy read permissions on the Home page.

## Step 3: View the result

![view_admin_vs_andy.png](~/getContentAsset/c57812a1-e766-4e86-b3c1-acd657d1b5cf/310c1ea5-13ca-4d75-95a0-620f51989b44/1305a886_view_admin_vs_andy.png.png)
 *Note: I configured the permissions of multiple documents and denied Andy **Read** permissions for them resulting in the illustration above.*