Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Overview

The Regent Award product supports the review of the eAccess Smart Forms via the Document Requirements tab by staff users with the appropriate permissions for the Default Institution.  Note:  Non-Default Institutions will not have access to the documents tab.

Document Requirements Tab

All required documents that display to the applicant are viewable in Regent Award, regardless of status (e.g. Not Started, Started, etc.). However, applications are not able to be viewed until the application has been ‘Completed’. Once the application is complete, staff users can review the application by downloading the associated attachment on the Document Requirement tab.  

The Regent Award document status (staff view) differs from the Regent Student Portal document status (applicant view). Regent Award utilizes the following three statuses for the eAccess solution: 

Document Requirements statuses

StatusDescription
Needed

Application on the Regent Student Portal is ‘Not Started’, ‘Started’, or ‘Incomplete – Parent Signature Pending’​​.

  • The document status on the Regent Student Portal could be in either a ‘Not Started’, ‘Started’, or ‘Incomplete – Parent Signature Pending’.
Satisfied

Independent Application has been eSigned or either Independent or Dependent Application requires wet-signature; a PDF of the completed application is viewable via Regent.

  • PDF of the completed application is viewable via Regent Award. 
  • The document status on the Regent Student Portal could be in either:
    • Completed on [date]
    • 'Completed on [date]. It is the student’s responsibility to return the form to the school with the student signature (with both the student and parent signature)'. 
Received

Dependent Application has been eSigned by both the student and parent: 

  • PDF of the completed application is viewable via Regent  Award.
  • The document status on the Regent Student Portal could be in either a ‘Completed on [date]or ‘Completed on [date]... 

If a correction is required after an applicant has completed the eAccess Smart Form, a staff user with the appropriate permissions can download a copy of the completed application from Regent Award to have the applicant make any necessary corrections or the staff user may opt to manually add a new document requirement in Regent Award for the applicant to complete again. The new document is visible to the applicant via the Regent Student Portal in the Required Documents grid. Regent Award only auto-populates the initial eAccess Smart Form once per Award Year. 

User Roles and Permissions

Users are assigned permission-based roles which govern access to the Regent Award system and define specific functions.  Here are some typical roles that are created for eAccess Regent Award users:

Role NameDesciption
Admin

Global Administrative Role.

FA AdminThis role allows the user to view the student's account in Regent Award. It is typically used by employees who assist students with technical support questions and status of the application document. This user would also have the ability to manage user accounts.
IT technicianThis role is used by an employee who is responsible for managing user accounts and running processes.    
View Only

This role allows the user to view the student's account in Regent Award. It is typically used by employees who assist students with technical support questions and status of the application document.

A Regent Award user that has the "IT Technician" role would have the capability to do the following:

  • Reset a Regent Award user's password.
  • Create a new user and assign them to a role.
  • Re-assign an existing user to a new role.

Users and Roles can be updated by going to the Administration dropdown in Regent Award

Once a user is selected, a Regent Award user with the appropriate permissions is able to Reset a password, Delete a user, create a user, or add a user to a role.

  • No labels