One of the greatest benefits of YaleSites is the ability to control administrative access to your site and determine who can do what (make edits, post content, or build out the site). Anyone with a Yale NetID and password can be given access to a site by the site administrator who can assign roles with various levels of permission.
The following roles are available on your YaleSite. Additional roles may be created but most site administrators find this is not necessary.
To add a Role, click on People > Permissions > Role. Once done you need to assign permissions so indicate the functionality allowed for that Role.
Most likely you (the site administrator) will not be the only person working on your site. As the Administrator, you can add people to your site and assign them a role that allows them to perform specific tasks on your site. To access commands to manage people, click on People in the Administrator’s toolbar.
Anyone with a Yale NetID can be granted access to your site and, as the Administrator, you can easily add them to your site using their NetID.
Important Note: When people are added via CAS, their full name, phone, title, address, and email are pulled from the HR database.
As of June 20, 2014, you can now add multiple NetIDs to make it easier to populate your people listing. If your site was created prior to June 20, 2014 and you would like this feature, please complete the Refresh my site form.
When accounts are created initially, they are assigned an Authenticated User Role. If you have a custom role, you can change it for more than one person in the following way:
If you would like faculty or staff to complete their own profile, you can ask them to login to the site and update their information in the following way*:
* You must have the Yale People Listing Feature enabled and the People Type selected in order for these people to show up in an organized list.
Once you have added a person to your site, you can assign and/or change roles for anyone logged into your site:
There may be times when you want to block someone from your site because they have left the University or are exhibiting behavior that warrants removal (spamming a forum or posting inappropriate comments, for example). You can easily block them by clicking on the Block radio button on their profile page:
Permissions control who does what on your site. Your YaleSite has a predefined set of permissions for all the modules and features available with the basic setup. In addition, each module that is enabled has its own set of default permissions. All permissions can be changed based on your site requirements and who you want to allow to work with the module.
To review and/or change permissions, click on People > Permissions. Permissions are enabled for a role by checking the checkbox below the role.
Below you see an example of the permissions for the Comments module, one of Drupal Core modules. The Permission identifies the tasks that require permissions for that module and the check boxes indicate the Roles that have permission to do the task
In this example:
YaleSites now offers ability for people without a Yale NetID to login to YaleSites with Third Party Systems (Google, Yahoo, Facebook, etc.). Although this feature is available for any YaleSite, it is not installed by default as it requires advanced technical knowledge to configure. If you are interested in this feature, please complete the Request 3rd Party Authentication form.
3rd Party authentication allows people outside of Yale (e.g. faculty or researchers associated with a project without a Yale NetID) to login to your YaleSite through other web services (Facebook, Google, Twitter, etc.). The username and password are passed to and from these services; YaleSites does not store any passwords. Usernames and password credentials are reset using the provider’s system or can create an account if they do not have one.
YaleSites allows 3rd Party Authentication from the following services.
Once 3rd Party Authentication is enabled by the ITS Web Team, direct people to login to your site in the following way:
Once this feature is configured on your site, you can assign Roles and permissions as you would for a person who has logged in with CAS. Please refer to the roles and permissions section of our documentation.