Ticket Collaborators

Summary
Allow tickets to include additional users as collaborators, beyond the single primary requester currently supported.

Problem
A ticket today can only be tied to one user. In real cases, more than one person has a legitimate stake in the ticket — a student and their librarian, an employee and their manager, a staff member and an admin assistant. With no way to add collaborators, those additional people can't view the ticket, receive updates, or contribute context, and communication has to happen outside the system.

Proposed Solution

Add a "Collaborators" field on tickets that accepts one or more additional users.
Collaborators can view the ticket, receive notifications on updates, and add replies or notes based on their permissions.
Configurable notification preferences so collaborators aren't over-notified.
Collaborators are visible in the ticket header and captured in the audit trail (added by, added when, removed by).

Who Benefits

End users — managers, parents, or supervisors can stay in the loop without opening duplicate tickets.
Support agents — one ticket holds all relevant parties instead of scattered side conversations.
Team leads and auditors — a clear record of who was involved and when.