Terms of Service

CompusPress Hosting Package

Campus Web Services will provide website hosting services to The Client for the Website through our partnership with CampusPress. The partnership with CampusPress encompasses the infrastructure and capacity aspects of providing a website such as storage for files, network connectivity, maintenance of servers, backups and other server related items. 

This hosting environment will provide:

1. Hosting on a WordPress Multisite network
2. Managed TLS certificates to provide https via Let’s Encrypt.
3. Automated nightly backups.
4. 24/7 monitoring provided by CampusPress
5. UA Webauth for Single Sign-on

Website maintenance will be ongoing and will not require any initiation from The Client. CampusPress will provide the following website maintenance services to The Client for the Websites:

1. Managed upgrades of WordPress core, plugins and theme
2. All changes are tested fully in a local testing environment by the technical team.
3. Automated and unit testing in multiple development environments
4. Manual testing by QA team in multiple development environments using all major browsers and operating systems, including mobile devices
5. Full deployment to small subset of live networks and all development/test networks that willingly participate in beta testing program. (Arizona Faculty Sites is not in the beta testing program)
6. Full deployment to all customers during the next Tuesday update window and an update published to our change log alerting customers.
7. Continuous monitoring by technical and support teams.
8. For any significant changes that end users may notice, Campus Web Services will be notified in advance.
9. Basic Security Remediation: In the event of a malicious attack or critical security vulnerability on a site, Campus Web Services will notify The Client and block internet traffic to the site. Campus Web Services will work to resolve the issue in as timely a manner as possible and will keep The Client notified of progress.

CampusPress will provide direct, 24/7 priority email support from support staff. They will work closely with Campus Web Services to understand any policies, guidelines, and network settings to support you in a seamless manner.

Campus Web Services will provide the following launch services for the Websites:

1. Provide the initial Sandbox environment configured on the Arizona Faculty Sites network.
2. Provide a curated theme that follows the University of Arizona brand guidelines.
3. Provide a curated set of plugins to meet common use cases.
4. Configure your site with the site name of your choice following the sites.arizona.edu/ pattern. The default site name will be the NetID of the site owner, but any other site name can be requested with the following exceptions:
   1. It must not already be claimed by another Arizona Faculty Site
   2. It must not be any other valid NetID. To avoid collisions with current or future NetID’s, all site names that don’t use the owners NetID must include a dash “-” somewhere in the name. Here are some examples:
      • sites.arizona.edu/firstname-lastname
      • sites.arizona.edu/name-lab
   3. It must not violate the University of Arizona’s “Acceptable Use of Computers and Networks Policy” which can be found at https://policy.arizona.edu/information-technology/acceptable-use-computers-and-networks-policy

1. Campus Web Services will manage the relationship between the University of Arizona and CampusPress.
2. Campus Web Services will provide a WordPress theme that has been curated to meet the University of Arizona’s brand and accessibility guidelines.
3. Campus Web Services will provide a set of WordPress plugins that have been curated to ensure that security is maintained in accordance with the policies set forth by the Information Security Office (ISO) found at: https://security.arizona.edu/content/policy-and-guidance.  
4. Campus Web Services will notify The Client if any performance issues are identified and provide recommendations to improve performance.
5. Campus Web Services will respond to work requests in a timely manner and address production issues and new work requests in accordance with the terms identified in this agreement.

1. The Client is responsible for making all content updates to their site and making sure that the content remains up to date and relevant.
2. The Client will affirmatively confirm within the first 90 days of each new academic year that they wish to keep the website active. Failing to do so will result in the website being taken offline until The Client contacts Campus Web Services to request that it is reactivated.
3. The Client will not use this website as a Learning Management System (LMS). The following functionality should be done in D2L:
   • Assessments 
   • Storing or distributing grades
   • NetID protected access to course content
4. The Client will notify Campus Web Services immediately if any evidence of a security breach is discovered, such as: hacking, defacement or denial of service attacks.
5. The Client will request work in accordance with the terms identified in this agreement.
6. The Client must ensure that no secure information is added to their site in accordance with the General Terms and Conditions in Appendix A.

1. The Client will complete any necessary User Acceptance Testing requested by Campus Web Services in the case of updates that might affect their workflow or changes to plugins or themes.
2. The Client will ensure that no modifications made will prevent the application of theme or plugin updates.
3. The Client is responsible for any HTML, JavaScript or CSS that they add to their website, as well as any impact that it may have on the functionality or appearance of unexpected or unrelated portions of their website. 
4. In the event that security or maintenance updates cause regressions to the functionality or appearance of the websites that have added custom HTML, JavaScript or CSS, The Client will be responsible for troubleshooting and resolving those issues.

1. Members of the Campus Web Services team will be added as Super Admin users on the WordPress MultiSite network in order to fulfill our obligations and provide the services outlined in this SLA. 
2. Members of the Campus Web Services team will have access to all Websites covered by this agreement.
3. The Client will be granted Administrator access to the Website and will be responsible for adding and removing other users and determining the appropriate roles. A complete description of the various roles can be found at: https://docs.campuspress.com/en/articles/481-user-role-overview
4. The IT Director of the Faculty member’s department or college and their designated representatives may also be granted Administrator access to the Website.

Campus Web Services will conduct a periodic review of the Arizona Faculty Sites platform and remove access for any users that are no longer affiliated with the University of Arizona, or any site owners whose affiliation is no longer Faculty.

Upon request, Campus Web Services can provide a complete backup of the Code, Files and Database of the website to the site owner. We will not provide redirects from Arizona.edu sub-domains to other institutions.

Arizona Faculty Sites are provided as a free service by the University of Arizona to all active Faculty members. 

Campus Web Services and The Client agree to comply with all applicable University of Arizona security standards, guidelines and policies as noted at https://security.arizona.edu/content/policy-and-guidance. As noted above, The Client agrees to contact Campus Web Services immediately if a website security issue is noticed or suspected. Campus Web Services reserves the right to disconnect from the network any website that has been compromised. ISO must be notified by The Client, of any event that has the potential to negatively impact the confidentiality, integrity, or availability of University Data.

UA WebAuth should be used to authenticate all user logins. Campus Web Services has enabled Single Sign On via Shibboleth, and disabled all other means of authenticating users.

Payment Card Transactions are not allowed within Arizona Faculty Sites. Sites that link out to a separate payment gateway may require additional levels of compliance and both Campus Web Services and the University Financial Services Office must be notified.

Personally Identifiable Information (PII) is not allowed on the provided hosting environment. This includes any data that is considered protected under HIPAA or FERPA. Campus Web Services and The Client mutually agree to keep all non-public information and data concerning the other party’s business confidential, including, but not limited to, ideas, products, customers or services. This includes any information or data that is of a personal, proprietary or trade secret nature. Confidential information will remain the property of the disclosing party and the receiving party will not acquire any rights to that information. Both parties agree to adhere to the policies available at https://security.arizona.edu/content/policy-and-guidance 

If The Client requires Campus Web Services resources beyond the services outlined in these terms, there may be an additional charge to be determined at the time of the service request. If the services are extensive or require significant Campus Web Services staff time, then Campus Web Services may require a separate Service Level Agreement or an addendum to this Agreement before rendering services.