What Is It?
A managed process to grant, modify, or remove access to Colleague (and Colleague Self‑Service, where applicable). ITS partners with functional data owners (e.g., Student/Registrar, HR, Finance) to confirm business need, apply least‑privilege security, and maintain audit readiness. All accounts and usage must comply with LU Acceptable Use and University policy.
Who Is Eligible to Use It?
- Faculty & Staff: Access aligned to job duties (academic, administrative, or advising use cases)
- Student employees/Graduate assistants: By department sponsorship, limited to work duties and with defined end dates
- Contractors/Affiliates: By exception with a sponsoring LU department, time‑bound access, and any required agreements
Standard student users (non‑employees) typically do not receive administrative Colleague permissions.
Where Can I Get It?
Click the "Request Service" button on this page.
How Do I Use It?
1) Choose the request type in TeamDynamix
- New access (first‑time or new role)
- Modification (add/remove modules, forms, or roles)
- Removal/disable (role change, separation, or end of assignment)
2) Provide complete details (this speeds approval)
Include the following in your ticket:
About the person
- Full name, LU email, department, supervisor, and employment type (faculty/staff/student worker/contractor)
- Start date (and end date for student workers/contractors)
About the access
- Request type: New / Modify / Remove
- Business justification: What tasks the user must perform in Colleague
- Functional area(s): Student/Registrar, HR/Payroll, Finance/AR/AP, Financial Aid, Advancement, etc.
- Environment: Production and/or Test (training/sandbox)
- Specific needs (if known): Forms/programs, processes, reporting, or security class/role names
Approvals & training
- Data owner approval (or the functional office contact if you know them)
- Confirmation of any required training/agreements (e.g., FERPA for student data where applicable)
Tip: Least privilege is applied. If you’re unsure of the exact role, describe the daily tasks—ITS and the data owner will map to the minimum security needed.
Notes & Policies
- Use of Colleague must follow LU Acceptable Use and data‑handling standards. Avoid placing PII or sensitive data in tickets; describe needs without sharing protected content.
- LU’s Colleague SaaS model means updates and maintenance are centralized; some changes may require coordination with the vendor’s change windows.