, but this code // executes before the first paint, when

ÃÛÌÒapp

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Policies | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Policies

As a user of ÃÛÌÒapp technology resources it is your responsibility to be aware of both ÃÛÌÒapp’s policies on using ÃÛÌÒapp’s information technologies as well as federal, state, and local laws that affect your use of technology. As a Christian university, what might be allowed under the law may not be allowed at ÃÛÌÒapp. These policies provide information on what is expected of you, what your rights are, and how to report violations.

Related ÃÛÌÒapp Information Technology policies:

Further Information:

Use of information technology resources at ÃÛÌÒapp is a privilege, not a right. Violation of any parts of CIT policies will subject the violator to disciplinary action, which may include any of the following: warnings, loss of access, probation, suspension, or legal prosecution.

  • Students
    • A breach of any parts of this policy mary warrant referral to the Senior Judicial Advisor or Judicial Advisor as defined in Appendix G of the Student Handbook: General Disciplinary Process.
  • Staff
    • A breach of any parts of this policy may warrant referral to their immediate supervisor as addressed in the Staff Handbook section on Rules of Conduct and Working Relationships.
  • Faculty
    • A breach of any parts of this policy may warrant referral to the Provost's Office as addressed in section 6.1 of the Faculty Handbook: Procedures for Addressing Allegations of Misconduct
  • Alumni and guests of the university
    • A break of any parts of this policy may warrant termination of access to ÃÛÌÒapp information technology resources or banishment from the university grounds.

As a user of ÃÛÌÒapp information technologies it is your responsibility to report any known or suspected violations of any CIT policy to the VP of People, Strategy & Technology, any IT Director, or an IT Information Security Officer.

Asset
University-owned and provisioned device
University-wide
Any user of ÃÛÌÒapp information technologies
Enfranchised
Anyone who has been given the right to use ÃÛÌÒapp information technology resources
Guideline
Official sanctioned advice from ÃÛÌÒapp Information Technology
Internal
Pertaining to those working within the Information Services Division, including student and contract employees
IT or CIT
ÃÛÌÒapp Information Technology Department
Policy
Statements of behaviors that are expected of all enfranchised users (faculty, staff, students, alumni, guests, etc) of ÃÛÌÒapp information technology resources and the consequences for failing to comply with the stated expectations.

CIT policies are intended to ensure compliance with applicable laws and regulations, to promote operational efficiencies, to enhance the university's mission or to reduce institutional risk.
Policy review
University-wide IT policies will be reviewed annually, or sooner if circumstances warrant, by the Policy Team.
Procedure or Process
Established or preferred method of accomplishing tasks; an internal procedure (or operation procedure) is the correct method of accomplish tasks.
Standard
Level or quality that is required