• Documentation
  InstallationUsing the Kentico interfaceDeveloping websitesConfiguring KenticoManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresCommunity featuresRunning Kentico on Microsoft AzureUsing Amazon web services with KenticoCertified extensionsReferencesRelease notes - Kentico 11
• Tutorial
  Getting started with KenticoUsing the Kentico interfaceSite development overviewPortal Engine developmentMVC development
• API Examples
  Content managementOn-line marketingE-commerceSocial and CommunityDevelopmentConfiguration

Example: Restricting the Products menu

In this example, you will learn how to display the Products section only to members of the Customers and Partners roles. They, you will see how to display the Smartphones category only to members of the Partners role.

Note that this example uses the sample Corporate site for illustration.

Creating sample objects

First, create the objects you will work with in this example:

1. Open the Roles application.
2. Select the Corporate Site from the Sites drop‑down list and create new roles Customers and Partners.
3. Open the Users application and and create a new user Customer1 with the following values:
   • User name: Customer1
   • Full name: Testing Customer
   • Enabled: yes (checked)
   • Privilege level: None
4. Assign the user to the Corporate Site and to the Customers role.
5. Create another user Partner1 with the following values:
   • User name: Partner1
   • Full name: Testing Partner
   • Enabled: yes (checked)
   • Privilege level: None
6. Assign the user to the Corporate Site and to the Partners role.

Assigning page-level permissions

Assign page-level permissions to the created roles:

1. Navigate to Settings -> Security & Membership and set Check page permissions to All pages.

   • This ensures that the security settings assigned in the following steps will be checked for all pages on the website.

2. Open the Pages application and select the root of the content tree.

3. Switch to the Properties -> Security tab.

4. Add the Public anonymous user (public) user and Customers and Partners roles to the list.

5. Grant the Read permissions to the user and roles.

   • Please note that you must click Save after assigning permissions to each user or role.

Hiding selected child pages

Now hide the product categories from public users:

1. In the content tree, navigate to /Products/Smartphones and switch to the Properties -> Security tab.

   • The permissions that you configured for the root of the content tree are inherited by this page.

2. Click the Change permission inheritance link to break the inheritance.

3. In the following dialog, choose Break inheritance and copy parent permissions.

4. Select the Public Anonymous User (public) and deny the Read permission.

5. Repeat the previous steps for the Laptops and Tablets page.

6. Also deny the Smartphones page for the Customers role.

Configuring web parts to check permissions

The permissions are not checked by web parts by default, so we need to configure the web parts so that they check the Read permission of the current user.

1. Choose the root in the content tree and switch to the Design tab.
2. Configure the Top list menu (CSS list menu) web part and select its Check permissions check-box in the System settings. Click OK.
3. Repeat the same for the CSS list menu and Featured products web parts on the /Products page.

Verifying the result

1. Sign out. If you mouse-over the Products menu item as a public user, you will see that the sub-categories representing the restricted sections are no longer displayed.

2. Sign in as user Customer1 (using the mini‑form at the top right of the page).

3. Navigate to Products via the main menu. As you can see, the Smartphones section and Smartphone products are not displayed to this user.

4. Now sign out and sign in again as user Partner1. You will see all categories and products.

You have learned how restrict access to content based on user permissions.