Registrar tool access: New employee onboarding guide (for campus partners)
Purpose
Use this guide when a new employee in your area needs access to Registrar-supported systems.
Submit Two Tickets
Open two Registrar tickets
CLSS / CAT / CIM Access - can ONLY be opened by the new employee’s supervisor
Banner + Other Registrar Tools Access - can be opened by the person overseeing onboarding or the new employee
Keep reading for tips on the needed information for each ticket.
Ticket 1: CLSS / CAT / CIM Access
Request access to: CLSS, CAT, CIM
Required details (choose one option per system):
Specify the role/permissions, OR
Provide the name of a person whose access the new employee should match (recommended)
For CLSS, if the new employee’s permissions don’t match or replace a previous employee, the department should be specified. See a list of department schedulers and their respective departments: https://tulane.app.box.com/folder/214915489291
Example request text:
Please grant [New Employee Name] access to CLSS, CAT, and CIM for [department]
For each system, match access to [Employee Name to Match]
Ticket 2: Banner + Other Registrar Tools Access
Why this must be specific:
Access and roles are distributed across multiple tools. The most efficient request is a tool-by-tool list with role or match-person identified for each.
Include (required):
For every tool requested:
Tool name
Role/permissions OR “match access to: [Name]”
Scope (if approver access), such as department/program responsibility
Tools you may request (include only those needed):
Banner
Degree Works
Advisor tab
Self-Service Reports tab
Grad App Dashboard
Commencement / Degree Certification app
FERPA training coordination (required step)
Grade Change Approver (scope required)
Major/Minor Certification tool (undergrad programs only, scope required)
Example request text:
Please set up access for [New Employee Name] for the following Registrar tools.
For each tool, match access to [Employee Name to Match] unless noted:
Banner: match [Name]
Degree Works: [View-only] or [Petitions]
Advisor tab
Self-Service Reports tab
Grad App Dashboard: match [Name]
Commencement/Degree Certification app
Grade Change Approver: match [Name]
Major/Minor Certification tool: match [Name]
After Ticket 2 is submitted: Required Steps for Banner Access
When the Banner + Tools ticket is received, our office will contact the employee with instructions for:
Completing FERPA training
Initiating the Banner account request
Scheduling Banner training
These steps can occur in different order, but the most efficient sequence is:
FERPA completed
Banner request submitted
Banner training completed
Timeline Expectations
The Banner account and/or Self-Service Reports tab typically become available 2–3 business days after Banner training is completed.
If other tools are needed other than Banner for Ticket 2, the employee can let me know when FERPA training is complete and we can enable those tools within 1-2 business days depending on capacity.
Access to the Self-Service Reports tab requires an additional step. Adding it to the request to the Registrar’s Office enables only the visibility of the tab. For access to the reports within the tab, open a request with BIA.
On this page
Ticket Intake Template
You can paste this into a ticket description.
Ticket 1 Template: CLSS / CAT / CIM
This ticket must be opened by the new employee’s supervisor.
New Employee Name:
Department/Unit:
TUID:
Username:
CLSS
Match access to (name):
CAT
Role/permissions:
Match access to (name):
CIM
Role/permissions:
Match access to (name):
Notes/Comments:
Ticket 2 Template: Banner + Other Registrar Tools
This ticket can be opened by the person overseeing onboarding or the new employee.
New Employee Name:
Department/Unit:
TUID:
Username:
Banner
Match access to (name):
Degree Works
Role/permissions (View-only or Petitions)
Advisor tab
Self-Service Reports tab
Grad App Dashboard
School:
Commencement/Degree Certification app
Grade Change Approver (if needed)
Scope (dept/program/level):
Match access to (name):
Major/Minor Certification tool (if needed)
Scope (dept/program/level):
Match access to (name):
Additional tools not listed (be specific):
Tool name:
Role/permissions:
Match access to (name):
Notes/Comments: