Skip to main content
New Idea

Better ticket redirection when in restricted groups

Related products:Freshservice
  • January 2, 2026
  • 7 replies
  • 52 views

Medic1334
Top Contributor ⭐
Forum|alt.badge.img+9

Recently dealt with a couple issues from a user who is trying to access a ticket that was routed to a restricted group. This user is an agent.

If the user tries to access the ticket via the email that was sent on creation it (we are using {{ticket.url}} in the email) it routes them to the agent page, then they get a toast notification that they are not allowed to see the ticket and to view it in the support portal.  If the user doesnt notice this popup or interact with it in time they can end up confused/with a poor experience.

From a UX perspective, it would be nice that if the error with visiblity is experienced, it tries to route the user into the support portal to view the ticket and THEN if the user cant access it for some reason, a message is displayed. 

For now, I’m stuck replying to tickets and telling users to view them via the support portal.

How are the rest of you handling this in the meantime? Any other protips? ​@mbutler ​@DanielRuff ​@Daniel Söderlund 

7 replies

DanielRuff
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • January 12, 2026

Hi @Medic1334,

I’ve had a similar experience with this behavior. It would be helpful if a hint appeared indicating that the ticket exists but belongs to a restricted group (also when searching for a ticket as an agent). 

What’s your opinion on manually rebuilding the end-user link instead of using the default URL placeholder?


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

I have rebuilt the link to point the end user portal, if you are an agent and have access to the ticket you will be redirected to the ticket else you will get the end user portal. 

This isn’t just for restricted groups, if the agent do not have access they just get an error saying you don’t have access and you end up in the ticket list view/dashboard. 

But I agree if you as an agent don’t have access in the agent portal but the end user portal you should be redirected to it. 


DanielRuff
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • January 12, 2026

Maybe this is a topic we should raise in the top user community or in the ideas section.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Maybe this is a topic we should raise in the top user community or in the ideas section.

This is an idea ;) 


DanielRuff
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • January 12, 2026

Oh wait that’s already in the ideas section. Damn it. 😅


Medic1334
Top Contributor ⭐
Forum|alt.badge.img+9
  • Author
  • Top Contributor ⭐
  • January 12, 2026

I have rebuilt the link to point the end user portal, if you are an agent and have access to the ticket you will be redirected to the ticket else you will get the end user portal. 

How did you do this?


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

I have rebuilt the link to point the end user portal, if you are an agent and have access to the ticket you will be redirected to the ticket else you will get the end user portal. 

How did you do this?

I used this in e-mail notifications  <domain>/support/tickets/{{ticket.id | split: '-' | last }}
and in WFA I used same is but the placeholder with just the number.