Office of Technology

Portal Asset Policy

This document was created to specify policies regarding myCampus Portal assets. Portal assets include communities and announcements. This document will outline who will have permission to request, create, and distribute these assets and rights associated with each asset respectively.

Creation and distribution of myCampus "myCampusAlerts"

myCampus "myCampusAlerts" appear on the main portal page prior to login as well as landing page of the myCampus Portal immediately after logging in. myCampus "myCampusAlerts" are of a very serious nature and are only utilized in critical situations. myCampus "myCampusAlerts" are to be initiated according to the crisis management plan and administered by the Office of Technology.

Creation and distribution of myCampus "myAlerts"

myCampus "myAlerts" appear on the landing page of the myCampus Portal immediately after logging in and produce a pop-up which requires acknowledgement. myCampus "myAlerts" will produce an email and if the user has entered mobile information into their individual profile, the "myAlerts" will also produce a SMS message. myCampus "myAlerts" are reserved for administrative purposes only. These messages are targeted to individuals and are not sent campus wide. myCampus "myAlerts" are to be approved by the unit head of an administrative office or above prior to distribution. The Office of Technology will help the administrative office on the creation and triggers for "myAlerts". "myAlerts" are administered by the administrative office.

Creation and distribution of myCampus "myAnnouncements"

myCampus "myAnnouncements" appear on the landing page of the myCampus Portal immediately after logging in. myCampus "myAnnouncements" will only be used for essential campus-wide announcements and major service interruptions. myCampus "myAnnouncements" are to be approved by a member of the administrative council and administered by the Office of Technology.

Creation of myCampus "Flyer Communities"

myCampus "Flyer Communities" can be used by colleges, administrative groups, administrative and academic committees, academic groups, student organizations, RHA resident hall groups, and more. "Flyer Communities" provide a vehicle to communicate information pertaining to Lewis University organizations.

  • College "Flyer Communities" are to be approved by a dean or above prior to creation.
  • Administrative group "Flyer Communities" are to be approved by an administrative unit head or above prior to creation.
  • Administrative and academic committee "Flyer Communities" are to be approved by a committee chair or above prior to creation.
  • Academic group "Flyer Communities" are to be approved by the department chair or above prior to creation.
  • Student organization "Flyer Communities" are to be approved by the Dean of Student Services or above prior to creation.
  • RHA Resident Hall Groups "Flyer Communities" are to be approved by the Director of Residence Life or above prior to creation.

The organization or department will create the community with the assistance of the Office of Technology. After creation, the maintenance and administration of the "Flyer Community" is the responsibility of a representative from within the given organization or department. The person approving the creation of the "Flyer Community" (or their delegate) must periodically review the community to ensure content is current and appropriate.