The Security Request System (SRS) was identified as a need here at UNI after the implementation of the e-Business system and provides system security, approvals, and automation for UNI systems.

Accessing SRS

To access the SRS system, visit MyUNIverse and find the Security Request System portlet, typically found under the Work @ UNI tab.

Open

Requesting access

Instructions on completing an SRS role request can be found in the Starting an SRS role request article.

Viewing roles

To understand viewing SRS roles for you or someone you supervise, see the Viewing and Revoking Your SRS roles article.

Approving access

All approvals are done via the e-Business workflow approval system used for financials, timecards, PAFs etc.

Role owners/approvers

Each role in the system has a single role owner.  The role owner can view a list of users who have that role and revoke the role as well from the SRS application.

Approval types

There are two types of approvals in the SRS system: management and role owner approvals. These are described below.

Management approval

The system automatically identifies the manager of the assignment tied to the request and they are the first approver.

If the supervisor is lower than a director, the manager will need to approve the role along with their director.  If the initial manager is either a director or higher, only one management approval is needed. For patrons, the approval is sent to the manager and director of the person that originated the request for the patron.

Role Owner approval

Role owners are one or more people identified as responsible for the role being requested.

Some roles require approval by multiple offices, such as Human Resource Services and Business Operations.  In those examples, there are two approval groups tied to the role and one person for EACH group must approve the request.

For example, the role “Bender_Hall Timecard Reviewer” is for University Housing and Dining, so the group “SRS Residence_System_Operations” is responsible for approving requests for that role. The director is in that group and is able to give access to that group to other employees. All employees given approval will receive the notification for the request, but only ONE of must approve (or reject) it.  If approved, the request is removed from the notification list of all approvers and  moves on.

Delegating approvals

Management approval

To delegate management approvals, set a proxy in Oracle eBusiness. You can create a rule for a predetermined date range will send approvals will go to the person you chose as your proxy.

Revoking access

Roles can be revoked. The process can be found in the Manually Revoking SRS Roles article.

Copying access

View the Copy SRS roles article for more information.

Using templates

View the Creating and using SRS Security Templates article for more information.

FAQ

Once approvals are done, when does access get granted?

Most systems grant access the next business day after the last approval is granted unless the Start Date for the roles requested is in the future. There are a few systems that still require manual intervention to process the completed requests, but should be completed the following business day after the Start Date requested.

Can SRS work with other systems?

Absolutely!  If there is interest in the SRS working with other systems, please create a Service Hub request, describing the system and how it may be used with SRS.

How and when does access end?

SRS roles can end in two different ways:

1. The role was revoked by a supervisor or role owner.

2. An employee's job assignment changes. When a job assignment ends, the SRS roles tied to that assignment ends, as well. This is true even if the employee is staying in the same department or if their job is not changing but their assignment changes due to merging departments.

If roles are ended and still needed, they can be re-requested by following the steps in the Starting an SRS role request article.