WiscWeb - WordPress UW Theme - Options for Locking Down Content in WiscWeb

This document will explain the different options available for locking down content in your WiscWeb project and what they may mean for your site and its contents.

Please note that locking down a page to a generic password is not an option in WiscWeb.

 Locking Down Your Site Prior to Launch

WiscWeb sites will not be crawled by Google bots unless someone links to the preview URL from another website or outside source. However, it's always possible that this could happen - even if you didn't link to it yourself. If you are concerned that your site content will be seen before it is ready, consider having your site locked down using Force Login

Force Login is a plugin that can be enabled on your WiscWeb project that essentially forces users to have to login with NetID credentials in order to see the pages of your site. Only persons who have a role in the site Dashboard (Administrator, Editor, etc.) will have access to view the pages. 

If you would like to add the Force Login plugin to your project, just send an email to cms-support@doit.wisc.edu. Please include your project URL so that the team knows which site to add it to. 

 Locking Down a Page, Grouping of Pages, or Entire Site to Certain NetIDs

If you are looking to lock down content on your site to a specific group of NetIDs, you will need to use a Manifest Group. For this, please follow our steps for creating a Manifest Group

If you have more than one page to lock down, please create a hub on your site using parent/child relationships. That way, protections can be placed on the parent page and all child pages will inherit the same settings. This also avoids having to place protections on a random selection of pages. 

Once you create your Manifest Group, you will need to send the team the Path Name and provide information on what you'd like locked to this group. If you have not launched your site yet, you can provide this information as part of your Launch Request. If you have already launched your site, just send an email to cms-support@doit.wisc.edu. Please include your project URL, the Manifest Group path name, and the URLs of the page(s) you'd like locked down. 

 Locking Down a Page, Grouping of Pages, or Entire Site to All NetIDs

If you are looking to lock down content on your site to all NetIDs, no Manifest Group is needed. 

If you have more than one page to lock down, please create a hub on your site using parent/child relationships. That way, protections can be placed on the parent page and all child pages will inherit the same settings. This also avoids having to place protections on a random selection of pages. 

If you have not launched your site yet, note in your Launch Request that you'd like the site or certain pages locked to all NetIDs. If you have already launched your site, just send an email to cms-support@doit.wisc.edu. Please include your project URL and the URLs of the page(s) you'd like locked down. 

 Locking Down Documents and Images

It is important to note that files uploaded to your Media Library (images, PDFs, Docs, etc.) will not inherit permission settings through the page they are linked on. Instead, they inherit the path structure of the Media Library. If a user has the URL of a file that was uploaded to the Media Library, they will be able to get to it - even if it sits on a protected page. Therefore, we recommend one of two options for ensuring that these files do not get accessed by users who are not approved to see them:

Uploading Files to UW Box

UW Box allows for robust permission and archival settings. Additionally, files loaded here can easily be shared with users located both on and off campus. To utilize this option, upload the files to Box, set the permissions, and then link to the documents and images from the webpage.

Using Consistent Naming Conventions to Lock Down Groups of Files

If UW Box is not an option for your team, you can request to have your files locked down based on a shared path structure. For this, you will need to decide on a single naming convention for protected files. Here are the steps you should follow if you'd like to use this option:
  1. Decide on the single naming convention for protected files and save out your files locally using this structure. (Example: protected-name1.jpg, protected-name2.jpg, protected-name3.jpg).
  2. Upload the files to your Media Library.
  3. Send an email to WiscWeb Support and request for all files with those naming conventions to be locked down (to either a Manifest Group or all NetIDs). (Example: Please lock down all files that have file names that start with "protected-").

Troubleshooting/Tips

  • Sites and pages locked down will not export data to Google Analytics. The tracking cookie will not be able to capture user interaction with your site because the site is not public. 

  • The default password protection that comes standard with WordPress sites will not work in WiscWeb due to the configuration of our Shibboleth plugin. There is no way to lock down pages to a generic password in WiscWeb. Instead, consider locking down with a Manifest Group or to all NetIDs. 

See Also:




Keywords:lock, protect, privacy, protection, login, access, lock down, netID, manifest group   Doc ID:87104
Owner:Jenna K.Group:WiscWeb CMS
Created:2018-10-24 07:48 CSTUpdated:2018-10-25 19:50 CST
Sites:DoIT Help Desk, WiscWeb CMS
Feedback:  0   0