Restriction on individual tickets or groups

+1

+1 Segmenting channels and topics is needed, at least for sending public responses.  Primary use case is we don't want all of our agents to have the ability to send out public tweets.  Thanks.

+1

Just confirm that having access segregation paired with groups does not offer the flexibility I'd like to have.

You did change this for views, that now are linkable to multiple groups, similarly you should consider doing that for ticket access too.

Corporate IT for example might easily need to access all tickets but the HR's ones. We cannot setup such a limitation at the moment.

+1 

Due to GDPR rules there are certain tickets (mainly fraud investigations) where we are obliged to restrict ticket access to a select few people. 

As Zendesk still (as the first requests were already done 5 years ago) isn't supporting this currently, while the subject is so big and important (the absolute volume is low, but the financial impact is huge), we diverted for our GDPR team to another inhouse developed tool.

But I hope Zendesk will come with something soon so we can be aligned again as a company. 

+1

We are currently investigating a project where we need to restrict access to a certain type of tickets.

+1 this is currently a dealbreaker for us

+1

+1

I would like to add that we also have a use case for this that would be great to see! In most cases we want our instance to be open, and for specific roles that we don't want to have access to Zendesk, we can do that today! 

But we have 2 groups that sometimes will get tickets that contain sensitive information that we do not want other groups/roles to see - and the solution today is to just delete those tickets. 

We'd like to not have to do that! Since we lose track of that information in Zendesk. We just want to make it so that it can be an open instance EXCEPT for 1 group of tickets only visible to agents in that group. 

Thanks! 

Just to add to this as it seems although things may have changed over the past year, there are still ways (esp by simply using search) that if you know what to look for, you can easily find tickets that do not relate to your Group.

FreshDesk is offering this, so it seems logical that Zendesk offers such an ability. Recent support replies have even hinted at setting up a second instance with data-share, that seems madness to me. The simplest of ticketing systems (say, OTRS) allow this so I'd say it needs to be something that's put into your sprints, if it isn't already!

Voicing on opinion on the subject: This is a basic functionality in many other ticketing systems. This is also part of the problem why many other ticketing systems are hard to use and manage.

Even if there would be a perfect technical solution to hide details from different agents based on this and that we are left with the managing part which gets hairy very fast.

As soon as we start to restrict the whole 360 view of the customer which is the basis of modern multi channel customer service systems and processes and have a situation where we can't trust that all that we see is really all that there is we are sort of "going away" from the whole idea on which for example Zendesk runs on and does a pretty good job.

On technical side then at first glance this feature request for limitins groups out totally seems pretty straight forward but when you start to go into details and start to really look into what to do with the user profile, what to do with reporting, how this affects different apps and channels etc it also get very hairy.

What we have as a Zendesk partner done with customers is we have left these groups out of Zendesk for the time being. Not just because you can't do it easily but also because when you start limiting and managing those limitations many times, not always, but many times even without the technical limitations we have come to the agreement that adding these restrictions would hinder and make difficult all the other work in Zendesk to that point that things work better and more efficiently if we keep the 360 idea of the customer inside Zendesk which everyone can count on.

Saying all this, as a Zendesk Partner we have a lot of customers who are asking for this and a lot of customers where the deal might hang on this kind of a feature so really looking forward if Zendesk finds a way in the end to implement this and other kind of Enterprise restrictions which are found in other systems but do these implementations in the Zendesk way so that it's not a total pain in the **s to both work with and manage :)

+1 to this idea. As we have expanded our usage of Zendesk group management has become more and more of a burden. Like the original post, we want most of our agents to have access to the majority of tickets without needing to add them each time a group is added while having the ability to restrict some users to only specific groups.

Just +1'ing everyone else here.  This would be a helpful feature for us and it would be great to hear an update from the Zendesk team, since it has been a couple of years!

Adding my vote to this too, we need to restrict individual groups/tickets for HR/Payroll coming onboard and a separate instance isn't ideal for our use case. For all other teams/groups already in Zendesk it's not ideal to have them in 30+ groups or to not see all other tickets so we really need an option to restrict just one group rather than all.

Hey, everyone –

I was not aware of this thread until it was pointed out to me today. Great to read all these comments. We are currently working on an enhancement to ticket permissions that should address this point of (very old) feedback. We're making major technical changes to support it, and we're not ready to announce a release date yet, but we do have plans in this area. Thanks everyone for your feedback.

I'm glad to hear this is finally being worked on.  This should have been a fundamental restriction years ago.

I see where you can provide permission by Group.  However, IF the Requester and the Agent are the same, the Requester/Agent can see the entire ticket and private notes. So "grouping" in this instance fails to protect any information in the ticket that the Requester/Agent should not see.

The only way around this is to have a separate instance of Zendesk which becomes difficult to manage. 

This would be useful we are in the same situation

Adding feedback that this is an essential feature for us. Due to GDPR regulations, tickets containing any personal data must be restricted to essential business needs based access. We could accomplish this using a "private group" feature. Thanks for any updates!

Im also adding my vote. Tris is very much needed!

Hi all,

I wanted to provide a quick update that this is currently in progress. On the surface, this may look like a simple enhancement but there's quite a lot of work for us in enabling this. Keep an eye out for more updates in the next few months. 

Happy Holidays!

Could we have an update on this please?

Allowing us to select agents who can access tickets in multiple groups (but not be part of the group) would be a huge, huge benefit. As a new customer to Zendesk I'm disappointed it is not an existing feature.
In our use-case, we have different departments using the same Zendesk instance and each department has multiple groups. The groups from one dept needs to see all their dept tickets but not the tickets of another dept. We are already using Organisations for our customers (we are a multi-org company). We have been able devise a workaround using more groups but it's a complex arrangement and not ideal at all. 

+1 to getting an update.  I see that there was a potential update being teased out on 12/2021.  When might we have the latest status of this request?

Hi all! I just wanted to provide a quick update that the new feature, Private Groups, is currently being tested with a small cohort of customers. There are a few things we need to get done prior to General Availability but this will be available to all in within 3 months or so. Thanks for your patience and continued feedback. 

Hi all,

Quick update, we're still working on this and have run into a few technical difficulties. We're looking at a general availability for all enterprise plans in the next few quarters. Thanks for your patience as we build this out.

Thanks @alina12!  This is preventing us from scaling Zendesk into other departments.  I'm still surprised this has been a feature request for years, and we're still a few quarters away.