Launchpoint User Accounts
Several departments and offices require access to the Launchpoint system and in each case the role-based permissions for user accounts will be limited to the least privilege necessary.
Kegley Electric
Kegley Electric administers the Hollins University System Galaxy and Launchpoint cloud instances: https://kegleyelectric.accessonthego.com/ As such, Kegley Electric employees will have the highest level of access to the system and all data contained within.
Information Technology
Information Technology is the primary administrator of the Launchpoint cloud instance and as such has the highest level of access of any Hollins University employees. This level of access is necessary not only for administering the Launchpoint system (managing access groups, etc.) but also for importing and exporting cardholder data that is used by other systems.
Campus Security
Campus Security staff members are primarily responsible for issuing new and replacement ID cards to employees, issuing and replacing student ID cards outside of regular business hours, and managing the access to buildings in the event of an emergency.
Housing & Residence Life (HRL)
HRL staff members are primarily responsible for issuing new ID cards to students and maintaining the correct residence hall address information in the Banner system.
Human Resources (HR)
HR staff members are able to access the Launchpoint system to deactivate employee access and other tasks as required by their office.
Account Creation
All student and employee accounts are synchronized between Active Directory and Launchpoint. This means that every student and employee will be in Launchpoint as soon as their Hollins University account (i.e., Hollins email) is created.
Assigning Access
Access Groups & Access Profiles
Cardholder building access is controlled by access groups and access profiles. An access group is a collection of card controllers and readers based on a physical location or other common characteristics. For instance, the “Dana Science Building” access group gives cardholders access to the majority of doors in the Dana Science Building.
Access profiles are collections of one or more access groups based on the cardholder’s relationship to the university. For example, the “Tinker Resident” access profile gives cardholders access to the “Tinker Hall” access group, and the “Student Access” access group, which includes the buildings that all students can access, like the library and Moody Hall.
Only the Information Technology department and Kegley Electric staff have access to edit access groups and access profiles.
Dynamically Assigned Student Access Profiles
Residential students are dynamically assigned access profiles based on their RH address record in Banner. For example, a student who resides in Tinker Hall will be assigned the Tinker Resident access profile.
Commuter students are dynamically assigned the Non-residential Student access profile based on being a student with no RH address record in Banner.
Access Profile | Access Group 1 | Access Group 2 | Access Group 3 |
Carvin Resident | Carvin House | Student Access | - |
East Resident | East Building | Student Access | - |
Francophone Resident | Francophone House | Student Access | - |
Main Resident | Main Building | Student Access | - |
Malvern Resident | Malvern Hill | Student Access | - |
Randolph Resident | Randolph Hall | Student Access | - |
Rathhaus Resident | Rath Haus | Student Access | - |
Rose Hill Resident | Rose Hill | Student Access | - |
Sandusky Resident | Sandusky | Student Access | - |
Tinker Resident | Tinker House | Student Access | - |
Village A1 Resident | Student Village A1 | Student Access | - |
Village A2 Resident | Student Village A2 | Student Access | - |
Village B1 Resident | Student Village B1 | Student Access | - |
Village B2 Resident | Student Village B2 | Student Access | - |
Village C1 Resident | Student Village C1 | Student Access | - |
Village C2 Resident | Student Village C2 | Student Access | - |
Village D1 Resident | Student Village D1 | Student Access | - |
Village D2 Resident | Student Village D2 | Student Access | - |
Village E1 Resident | Student Village E1 | Student Access | - |
Village E2 Resident | Student Village E2 | Student Access | - |
Village F1 Resident | Student Village F1 | Student Access | - |
Village F2 Resident | Student Village F2 | Student Access | - |
Village G1 Resident | Student Village G1 | Student Access | - |
Village G2 Resident | Student Village G2 | Student Access | - |
Village H1 Resident | Student Village H1 | Student Access | - |
Village H2 Resident | Student Village H2 | Student Access | - |
Village I1 Resident | Student Village I1 | Student Access | - |
Village I2 Resident | Student Village I2 | Student Access | - |
West Resident | West Building | Student Access | - |
Non-residential Student | Student Access | - | - |
Dynamically Assigned Employee Access Profiles
Employee access is dynamically assigned based on an employee’s department attribute in Active Directory.
Access Profile | Access Group 1 | Access Group 2 | Access Group 3 |
Maintenance All Access | Employee Access | Employee Master Access | - |
Campus Security Master | Employee Access | Employee Master Access | - |
IT Master | Employee Access | Employee Master Access | - |
Custodial Master | Employee Access | Employee Master Access | - |
HRL Master | Employee Access | Employee Master Access | - |
Executive Master | Employee Access | Employee Master Access | - |
Employee Standard | Employee Access | - | - |
Manually Assigning Access Groups & Access Profiles
Each cardholder can be assigned to four access groups. All four access groups can be manually assigned to cardholders who are not assigned an access profile:
Cardholder record in Launchpoint with no access profile
Access profiles use up three access groups and only the fourth access group can be manually assigned:
Image of cardholder record in Launchpoint with an access profile
Vendor Access
External vendors may need access to buildings during their work on campus. Vendors who frequently visit campus should be issued a vendor-specific badge that vendor employees can temporarily check out from Campus Security. Each individual vendor should have its own access group with access limited to the specific doors required to perform their work on campus. For example, a vending machine vendor might need access to the Dana Science Building, but only the loading dock entrance because that is where they will bring drinks or food into the building.
Vendor Access Groups
Vendor access groups will be created by the Information Technology department based on which doors the vendor needs to access. Vendors must use their own access groups so that those access groups can be disabled at will without affecting the access groups used by students and employees. All vendor access groups will be named in the following format:
Vendor - Vendor Name (e.g., Vendor - Kegley Electric)