Build pages with varying user permissions

Note: This tutorial is specifically for sites where there are pages that are only visible to registered users. For the time being, sites with this functionality require custom setup work from Kasey and Issac. If you would like this feature on your site, please contact us for details.

If you have this set up on your site, be sure to log out of your site (yoursite.com/admin/logout.php) and clear your browser cookies before testing any of these functions.

Permissions

Figure 1

To better understand how this dialog works, an understanding of the different default groups is necessary. As far as the software is concerned, there are four types of users:

  1. Site Administrators (with global access to edit and publish all pages)
  2. Site Contributors (with global access to edit and save drafts of all pages, but not publish)
  3. Registered users (or "Other Users")
  4. Unregistered users (or "Anonymous")

Since Site Administrators and Site Contributors will always have access to all of the pages, they are not shown on the permissions list. By default, all users registered or not can see published content.

 

Restrict access to content pages

If you want to hide a page from unregistered users, select that page in the Site Structure Tree (A.), then select the Permissions tab (B.). Both groups listed can see (but cannot save drafts or or publish) this page. To restrict access to this page to only those users who have registered, unselect the 'anonymous' checkbox. This way, only registered users (other users) may see this page. If an unregistered user tries to see this page, they will see a page that says "access denied," and it will either ask them to log in or register.

Note: The "access denied" page can be edited on a site-by-site basis. If you don't want the public to have the ability to register themselves, we can change the "access denied" page from "register here" to  "contact us for access to this information." At which point, you can create a username and password for them. This is how you can verify identites instead of allowing users to register themselves.

 

Case-study 1: unregistered user experience

An anonymous user stumbles across a resitricted page. This page (url: /srv_error_116) says:

Access denied.

This is a protected page. Please login with the form to the left or register (link) to continue.

If you are registered and logged into another Servee site, you may have to click here to verify your registration for this site (link).

Scenerio 1: John clicks the register link, fills out a brief form with his name and e-mail address, and is granted access to the restricted page that he had previously requested. He is now a registered user.

Scenerio 2: Mary logs in with the form provided on the Access Denied page, and is granted access to the restricted page that she had previously requested.