Banner Support for Staff

Banner is the Student Information System (SIS) for Yale University.  Banner supports processes across multiple units within Yale University, including but not limited to: Admissions, Financial Aid, Registrar, Housing, and Student Administrative Services. That is, Banner is not strictly a University Registrar’s Office (URO) system, nor is it administered by the URO.

The Banner Support website provides the University community with a centralized location for Banner information: user access, announcements, FAQs, training guides, and support. This site is intended to be a central resource about Banner at Yale.

 

About Banner Access

University employees seeking access to Banner administrative forms should have their supervisor submit a formal request for access via the form link below. 

Banner users must comply with the Family Educational Rights and Privacy Act (FERPA) of 1974. Before access to Banner is issued, new users are asked to complete a course and agree to the FERPA responsibilities required of employee members handling student information.

Once employees complete the FERPA course, the University Registrar’s Office will grant access if the request is reviewed, deemed appropriate, and approved.

Banner Access FAQs

Banner Access Request form

For questions about access to Banner, write to registrar@yale.edu.

 

About Banner Data Usage

A Banner data request is much different than a Banner access request. The University Registrar’s Office (URO) provides data for the operational needs of the University and to support regulatory compliance. Data is not provided by the URO for research purposes for faculty or students.

Data Usage Request FAQs

Banner Data Usage Request form (Note: the form may take several seconds to load) 

Understanding Data Access Levels

To protect student privacy and uphold data security, access to information from the student information system is granted based on your role and the nature of the data. Below are the three categories of data access:

  • Controlled Access

This is the default level of access. It includes data that you need to do your everyday job based on your role at the University. Based on your role, there will be no need to request special access. Examples include: student names, email addresses, netIDs, enrollment status, fields of study.

  • Limited Access

This data is moderately sensitive. Your role may already entitle you to limited access data, but in some cases you may need to request additional access. You will need to provide an explanation as to why you need it for a legitimate educational or operational reason. Your request will be reviewed before access is granted. Examples include: student course enrollments, student grades, citizenship.

  • Restricted Access

This is highly sensitive data and is only provided in rare cases. Access requires a clear, documented justification and may also require approval from the University’s Data Governance Committee. In most cases:

• Data will be shared in aggregate form (summary), not as detailed individual records.

• Data may only be used for the approved purpose and by the individuals named in the request.

• It must be stored securely, not shared, not reused for other purposes, and destroyed after use.

Additional resources: