Frequently Asked Questions
*The new security application project is still in the early stages. Due to this, the answers below are subject to change as information and requirements are analyzed.
What is the name of the new application?
Access Rights Management application (ARM)
As an end user, will I be able initiate a request for access in the ARM application? If so, what does that routing process look like?
This has been identified as an objective within the project in order to improve the end user experience and process for requesting access. The project team is in the early stages of analyzing this process.
Will there be training for all USC's on how to use the ARM application? If so, will it be mandatory?
Training on how to use the new application is in scope for this project. The project team is looking at options for the method of delivery for the training. It has yet to be determined if it will be mandatory for all USC’s.
Will the new ARM application be structured in a way to assist the USC in selecting the correct access?
Although the design is not yet complete, the goal is to create a user-friendly experience that will provide information about specific access/entitlements and applications that will help guide the USC in the access selection process.
Will USCs be able to determine if pre-requisite training for access has been completed within the ARM app?
The ability to confirm pre-requisite training within the ARM application is functionality that is in scope for the project.
Will the USC have access to profile/entitlement descriptions within the new ARM application?
Profile and entitlement descriptions have been identified as an objective for the project. The team will be analyzing the best method to make these available in the ARM application.
When requesting access, will the USC be able to find enterprise application descriptions within the ARM application?
Enterprise application descriptions have been identified as an objective for the project. The team will be analyzing the best method to make these available in the ARM application.
The current employee transfer process is dependent on completion of tasks by USC from the old department before the new department USC can request access. Will this process change in the new ARM application?
The transfer process has been identified as an objective for the project. Exact details of this functionality within the ARM application are still being fleshed out.
As a USC will I be able to copy a current employee's access to a new employee?
This has been identified as an objective within the project. The project team is exploring options that may be available in the ARM application.
How will the new ARM application change the yearly access review process?
The yearly review process currently is very manual and a tedious process. The objective is to bring the yearly audit functionality into the ARM application to make it a more streamlined and manageable process.
Will the new ARM application allow for searching on Chrome River Access?
Chrome River is in scope of applications to review and hopefully improve viewing access. However, it is a cloud hosted application which means there are challenges to getting this information. The team will be investigating all options available to be able to display access for Chrome River within the ARM application.
Will the new ARM application allow mass changes of the Manager Reviewer when a unit's current Manager Reviewer leaves, retires, etc..?
The project team is looking into options on how to make the transfer of access more user friendly and a better experience, not only in this case, but when anyone transfers to a new position within the University.
What resources are available to determine how to request access to enterprise systems?
The USC Website includes information on how to request access to enterprise systems. The goal in ARM will be to provide one application to request access to enterprise systems.
What resources will be in the new ARM application for translating "job duties" to accesses? As USC, people assume I know exactly which systems a person needs access to based on a list of job duties, when all I have is a brief description of both.
The project is affording the team an opportunity to review descriptions and definitions of applications/systems, what they are used for, and what entitlements will give access to them. The goal is to make these definitions and descriptions available within the ARM application.
*If you have questions related to campus project representation or would like to provide input, please consult the Project Focus Group tab and contact the appropriate individual representative.
Email the project leads with other questions at aitsdlitpc-620leads@uillinois.edu.