Protected content is only visible to a certain set of viewers.
IMPORTANT: Sensitive or Restricted Content
Sites@Duke Pro is not appropriate for sensitive or restricted content. We recommend Duke Box or another Duke-approved collaborative work tool.
Also, see below for a detailed list of what NetID Access specifically does NOT cover.
The Page, Story, News, Blog Post, and Resource content types have the option for NetID Access – which means only users with a Duke NetID can view this restricted content. It also keeps the page out of search engines.
To enable NetID Access on a Page, Story, News, Blog Post, or Resource, select the NetID Access checkbox, and Save.
If you enable NetID Access, the URL will have "/secure" added to it so that the URL pattern will be /secure/[url-alias]. This is required.
Accessing Protected Content
When users click a protected item, they will be required to log in with their Duke NetID and password in order to view the restricted content.
Users who have previously authenticated and have an active Shibboleth session will see the content immediately, without having to log in again.
What NetID Access Does NOT Do
hide Protected Pages from menus
If NetID Access is enabled on a Page, Story, News, Blog Post, or Resource in the menu, that menu item will still appear to all public users. It will not be hidden from certain users.
When users click a protected menu item, they will be required to log in with their Duke NetID and password in order to view the restricted content.
Media files are not eligible for NetID Access protection and can be accessed by all public users, even if you don't link to them. To protect a File, we recommend storing it in Duke Box (or another Duke-approved collaborative work tool) and linking to it.
remove protected content from search results
Protected content still appears in site search results, linked to its corresponding page. When users click on protected content in site search results, designated by the padlock icon, they will be required to log in with their Duke NetID and password in order to view the restricted content.
Restrict content to specific groups
Restricting content access to certain subgroups of Duke users – e.g., Grouper or Group Manager integration – is not yet available in Sites@Duke Pro, though it is on our Roadmap.
Enabling NetID Access will allow anyone with a NetID to access your content – i.e., all Duke users, not just specific subgroups.