This module has content that everyone can read. Everyone can see these words. Below is a module labeled Private Content that is only visible to users who are logged in. If you are not logged in, you will not see a module below labelled Private Content which is before the Instructions module. Before you login, you must register your name and password. Use the Register link to register your name and password. User the Login link to login with your name and password. Both the Login link and the Register link are in the top right corner of each page. If you do not want to register, use the Demo user with the password demo123.

This example shows visibility for anyone who logs in, but modules and pages can be made visible only to one individual or any grouping of users.

If you are logged in you will see the Private Content module above.

For more information on private content, view

• the Portal Security training video at http://dotnetnuke.com/About/TrainingVideos/tabid/810/Default.aspx  
• The Guided Tour for Securing Modules at http://dotnetnuke.com/guidedtour/ModulesSecure.htm 

Restrict Visibililty to Logged In Users

This visibility of each page and each module is controlled by Settings.

• Pull down the module menu and select Settings.
• In the Permissions section, remove the check box selection for Inherit View permissions from Page.
• Ensure that All Users and Unauthenticated Users are not checked so that these users cannot see the module and its contents.
• Check the Subscribers and Registered Users so that logged in users will be able to see the module content.

The screen will look similar to the following.

Restrict Visibility to Specific Users

To restrict visibility to specific users, you must group these users into a Security Role even if the role only applies to one user. The concept of a Security Role is much the same as a User Group.

• Pull down the Admin menu and select Security Role.
• Click on the Add New Role link.
• Enter a Role Name (eg. Trusted Users) for the users who will be allowed to view the content.
• Click on the Update link to create the Security Role.

Now that the Security Role exists, you need to include specify users as member of the Security Role.

• Pull down the Admin menu and select User Accounts.
  
• Click on the Edit icon associated with the User Account that you wish to include.
• Click on the Manage Roles for this User link.
• Select the new Security Role from the pull-down menu and click on the Add Role menu.

Now that the Security Role exists, you need to restrict the visibily to the specific Security Role.

• Pull down the module menu and select Settings.
• In the Permissions section, remove the check box selection for Inherit View permissions from Page.
• Ensure that specify Security Roles such as All Users and Unauthenticated Users are not checked so that these users cannot see the module and its contents.
• Check the new Security Role so that these logged in users will be able to see the module content.

If you are logged in you will see the Private Content module above.

For more information on private content, view

• the Portal Security training video at http://dotnetnuke.com/About/TrainingVideos/tabid/810/Default.aspx  
• The Guided Tour for Securing Modules at http://dotnetnuke.com/guidedtour/ModulesSecure.htm 

Restrict Visibililty to Logged In Users

This visibility of each page and each module is controlled by Settings.

• Pull down the module menu and select Settings.
• In the Permissions section, remove the check box selection for Inherit View permissions from Page.
• Ensure that All Users and Unauthenticated Users are not checked so that these users cannot see the module and its contents.
• Check the Subscribers and Registered Users so that logged in users will be able to see the module content.

The screen will look similar to the following.

Restrict Visibility to Specific Users

To restrict visibility to specific users, you must group these users into a Security Role even if the role only applies to one user. The concept of a Security Role is much the same as a User Group.

• Pull down the Admin menu and select Security Role.
• Click on the Add New Role link.
• Enter a Role Name (eg. Trusted Users) for the users who will be allowed to view the content.
• Click on the Update link to create the Security Role.

Now that the Security Role exists, you need to include specify users as member of the Security Role.

• Pull down the Admin menu and select User Accounts.
  
• Click on the Edit icon associated with the User Account that you wish to include.
• Click on the Manage Roles for this User link.
• Select the new Security Role from the pull-down menu and click on the Add Role menu.

Now that the Security Role exists, you need to restrict the visibily to the specific Security Role.

• Pull down the module menu and select Settings.
• In the Permissions section, remove the check box selection for Inherit View permissions from Page.
• Ensure that specify Security Roles such as All Users and Unauthenticated Users are not checked so that these users cannot see the module and its contents.
• Check the new Security Role so that these logged in users will be able to see the module content.