Who sees my support ticket?

Saying it on the form is the design decision, and it is the right one.

An internal helpdesk fails when people hesitate before using it. Somebody unsure who will read a request about a health benefit or a difficult situation simply does not file it, and the desk quietly stops reflecting what is actually happening.

So the scope is stated where the doubt occurs, at the moment of writing rather than in a policy page nobody opens.

The scope is the support team, meaning whoever holds the queue. An inbox shows requester, query, category, assignee, status and when it last moved, and that inbox is the surface where a ticket lives.

Assignment narrows it further in practice. A ticket assigned to one person is that person's work, though the queue itself is visible to whoever staffs it.

Attachments travel with the ticket and inherit the same scope. A photograph or document attached to a request is part of the ticket, not a separate thing with separate access.

For feedback about the workplace, the separate feedback channel masks identities by default, so a reviewer only sees a name after choosing to reveal it.

Choose the category that matches the subject rather than the person you hope reads it. The category is what routes the ticket, and a misfiled one waits in the wrong place.