Restricting tickets visibility to Brand


59 Comentários

  • Comentário oficial
    Alina Wright
    Zendesk Product Manager

    Hello everyone. We are launching the Early Access Program for Brand Based TICKET Access in Q1 of 2024. See below to get signed up for our closed EAP. This EAP is limited to those on Enterprise and above plans. We are only accepting 50 particpants.

    What is the Early Access Program?

    The Early Access Program is designed to provide our customers with early access to new features and improvements. By participating in the EAP, you will have the chance to explore these enhancements ahead of their official release and provide valuable feedback that will help shape the final product.

    What is Brand Based Ticket Access EAP?

    "Brand-based ticket access" in Zendesk allows agents to manage tickets associated only with their assigned brands. This ensures focused support, enhances data privacy, and promotes specialized product knowledge. Agents will now belong to brands and their ticket access will depend on their brand membership. Zendesk Admins will automatically belong to all brands.

    How to Enroll

    Enrolling in the EAP is simple. Just click on the following link: Sign Up for EAP (new!) and follow the instructions to register. Once you've signed up, you'll receive further information on how to access and use the new features. We are planning to launch in Q1 2024 and will follow up prior to any activation. Filling out the Sign Up form does NOT automatically enroll you in the EAP.

    If you have been accepted into the EAP, a few weeks prior to the release of Brand Based Ticket Access EAP, I will email you with instructions, screenshots, and a specific timeline. 

    Expectations of Participants

    As a participant in the EAP, we kindly ask for your active engagement and feedback. This may include participating in surveys, providing feedback on your experience, and reporting any issues you encounter. Your insights and suggestions will be invaluable in helping us refine our products and ensure they meet the needs of all our customers.

  • Estefani, Christian

    I'm glad to see my company's not the only one who needs this function!

    Our Zendesk instance contains a CITD brand and an HR brand, and agents associated with one brand should not have access to the other brand's tickets (due to confidential content).

    We cannot create a separate instance for the other brand because it is difficult to manage our agent license count for two separate brands (unless Zendesk allows free transferring of licenses between instances?).
    This is because the number of agents we have per brand changes quite often, and we cannot estimate how many licenses are needed per brand. (It'd be a waste to have too many excess instance-specific licenses, considering their price.)

    Currently, we are using the workaround of:

    1. Restricting agent access to groups; and
    2. Adding the agents to ALL groups associated with their brand.

    However, this workaround is highly inefficient because:

    1. Agents receive notification emails for tickets they are not currently in charge of (because they're added to the other groups); and
    2. It is quite challenging to assign a ticket to a specific person under a specific group because the agent's name appears under so many groups.

    Take note that our CITD brand alone has over 50 Zendesk groups, and we have many other brands aside from that one that have a lot of groups.

    I hope this suggestion gets approved and then implemented soon!


    Basically, here is my suggested function:

    In role settings, under "What kind of tickets can this agent access?", there should be this option:
    All within this agent's brand(s)

    When that option is chosen, there should be a new setting asking which brands to associate the role with.
    I think this mechanic can be similar to ticket forms:

    Then, agents under that role can only access a ticket if it's assigned under the associated brand.
    (Of course, not counting tickets they're CC'ed to or a requester of.)

  • MTech Systems

    I completely agree.  This needs to happen!  I need all agents to have access to all brands except for just one brand.  That one brand needs to be private for only a select group of folks.

  • Kim Lake

    +1, required - we need an ability to assign brand visibility to agents

  • Ritchie Robertson

    The problem I have is that we require agents to not be able to create tickets for certain brands but still be able to view all tickets within one brand.

  • chris.heap

    +1 for this feature. We have over 5 brands each with a dedicated support team that really have no interaction with tickets relating to other brands. Another related consideration for this is for suspended tickets to be available to each brand, having to grant access to all tickets to be able to manage suspend tickets is not good.

  • Heather Rommel
    Community Moderator
    Zendesk Luminary
    The Product Manager Whisperer - 2021

    I am adding my up vote to this - and commenting because it's that important to me - because I really love that Multibrands is an option but a little disappointed with permissions as a whole.... We would like more granular control over who has access to what. In my opinion, we should have the ability to:

    1. Restrict Agents to access and edit TICKETS only in their given brand(s) via role

    2. Restrict as in #1 above but extend read-only access to TICKETS in other brands

    3. Ability to have Read Only FIELDS in Tickets, Users and Organizations

    4. Ability to restrict TICKETS- both hide a given ticket altogether

    5. Ability to hide certain FIELDS on a ticket based on role

    As Zendesk scales, these kinds of requirements will be necessary as more and more companies leverage Zendesk outside of the "usual" ITIL usage by additional departments and for different processes. 

    Bottom line: Since Zendesk's collection of product offerings are expanding, the permission structure needs to grow with it!

    Please and thank you :)

  • Grzegorz Ksiazek

    Hey Zendesk Support Product Owner,


    What are the plans to implement this?

    Is this even on a roadmap?



  • MTech Systems

    Still important to me and my team!  Restricting one of our brands to be accessible by only one group would make life much better for us.  Thanks. 

  • Sarah Anscombe

    Following - as this would be helpful for us too.


  • Aja Varney
    Zendesk Luminary

    Agreed! +1 for me. 

    We have a large use case with many "brands".... but most agents are tasked with one brand or the other. 
    Would be excellent to be able to restrict user to brand(s) - multi select. 

  • Wesley Bowles

    Adding a +1 here as well. The current solutions laid out here aren't scalable and leave a lot of room for error. Within the "roles" functionality we should be able to identify which brands those roles belong to. 

  • Ron de Vries

    Agreed! + 1

  • Paul Maillard

    Highly needed, especially with the Invoice Team using Zendesk !

    Please, make it happen quickly !!

  • Dawn Anderson

    Agreed, this is needed!


    We have QA agents that need access to some tickets and don't want to give them the permission to view all tickets as it's not appropriate for them to have this access.

    Any movement on this please?

  • Josh

    +1 definitely needed if you're going to support multiple brands.

  • API Integration Account

    +1 Please plan and implement as it will be a very useful user restriction option for multibrand instances with brands being dedicated to separate licenses and/or jurisdictions.

  • Jerry Ishmael

    Would also like to see light agents restricted to Brand and Forms. This would truly provide an enterprise solution for those who require it. 

  • Eski Admin Hesabı

    +1 definitely needed. Please add this feature asap.

  • Alina Wright
    Zendesk Product Manager

    Hey all - thank you so much for your detailed feedback on the separation of brands and ticket visibility.

    As we grow in the enterprise space, we're hearing this feedback more frequently. While this is not on the current 9 month roadmap, it is something we're starting to prioritize and discover. We're exploring all the technical implications of such a big change and the necessary requirements. If you've commented on this thread and would like to add additional nuance to your request or update anything, this is a good time to influence how this might work in the future. Beyond tickets, what other elements should be restricted by brand? 

    Thanks again! 

  • François Bellavance

    "Beyond tickets, what other elements should be restricted by brand?"

    • Forms : Really important!
    • Having admins per brands (Guide, different Chat, different Gather, etc...)
  • Nicole Putman


    I want to add, as we are about to move our HR Team into our main instance from their own do to work overlap and reporting needs, there is another issue that has no resolution:

    If a non-HR Team Agent in Zendesk sends in a ticket to HR Support in this new joint instance environment, because they are on the ticket as the requester, they have access to the ticket. But, worse, as an Agent in Zendesk, they can see the private notes that are being entered by the HR team. This is a big issue, especially in Employee relations situations.


    Laid out:

    • Agent A is in Brand for IT- Cannot see HR Brand tickets
    • Agent A sends a ticket in for a personal issue to HR support

    Issue: As a requester, Agent A can see this new ticket in Zendesk by looking at their requested tickets, including all HR Agent private notes on tickets, even though the ticket is not in their Brand.


    There should be a way to restrict agent access further inside Brand to allow for end-user experience for Agents in Zendesk when sending support requests to other teams.

    It could be an additional field under the Role settings:

    Restricting their access as a requester, removing the ability to see private notes out of Brand unless added as a follower or cc'd.


  • Dana Martell

    +1 to separate ticket access by brand

    For compliance and regulatory reasons it is a necessity to be able to separate access to tickets by brand for each separate company managed in one Zendesk instance. Admins should be able to set agent access to tickets based on role for one, multiple, or all brands. 

  • prakash.sati

    Waiting! as this is a must have feature for Multi-brand setup. 

  • Erkin Yasar

    +1 Any update?

  • François Bellavance

    Any update on this? It was talked in 2018 and we are in 2022.

  • Dave Dyson
    Hi François, the most recent update is from last October, in Alina Wright's official comment here
  • Max McCal
    Zendesk Product Manager

    Hi, all 

    Though we don't yet have a solution in place for this, we are still working towards this goal. We have so many permissions related improvements to make that prioritizing between them is difficult work. This is not something we can promise on any kind of time frame, but it is without a doubt something we plan to deliver.

  • Jay Krishnan (Light)

    This will be quite an important feature if and when it rolls out.

  • Marie Hayes

    another upvote here! This is what we're missing and desperately need.


Por favor, entrar para comentar.

Powered by Zendesk