Questions? We are here to help!

Change Private Ticket To Public

Make a Private Ticket Public

Making a ticket public removes its private-ticket restriction. Other staff may then be able to open it according to their ticket-viewing permissions and access scope.

This action does not publish the ticket on the internet or turn it into a public knowledge-base article. It changes ticket visibility within HEDESU’s access rules.

Before changing visibility

Read the ticket description, internal replies and attachments. Make sure the information is appropriate for the wider staff audience that may gain access. Internal replies remain internal replies, but more authorized staff may be able to read them after the ticket becomes public.

A private ticket is not necessarily visible only to its requester. Access can include assigned users or teams and other access allowed by your workspace’s permissions. Do not use the lock icon as a substitute for checking who can access sensitive information.

Change the ticket

  1. Open Inbox and find the ticket using an available view such as Requested, Assigned or All.
  2. Open the ticket. A lock icon identifies a private ticket.
  3. In Ticket Details, open the three-dot actions menu.
  4. If Make Ticket Public is available, select it.
  5. Read the confirmation: “Are you sure you want to make this ticket public? It will be visible to users with access.”
  6. Confirm only after checking that the wider access is appropriate.

After the change, reopen or refresh the ticket and confirm that the private lock indicator is no longer displayed.

If the action is missing

The action is shown only for a private ticket when your account passes the relevant permission check. It will not be offered for a ticket that is already public. If you need a visibility change and do not see the option, contact your workspace administrator or the ticket requester.

If you selected it by mistake

The current ticket menu does not provide a matching Make Ticket Private action. Contact your administrator promptly rather than assuming there is a one-click undo. Avoid adding further sensitive content until the appropriate access has been confirmed.