Recent searches


No recent searches

Restricting agent ticket access by brand (Department Spaces)



image avatar

Kristie Sweeney

Zendesk Documentation Team

Edited Feb 04, 2025


2

23

23 comments

So, what we've been doing is to have Groups that are aligned with Brands, with Triggers assigning tickets in Brand A to Group A, tickets in Brand B to Group B, and so on. Team members have roles that only allow them access to ticket in their own groups. 

 

If I understood the announcement correctly, using Department Spaces i.e. Brand membership would have pretty much the same result as what I've described, wouldn't it? 

2


You say “Do not use this feature if you are currently using Chat, messaging, or Talk.” Can you elaborate on this? Why doesn't it work/shouldn't we use it? Is there some alternative if we're trying to keep certain agents to a certain brand?

0


image avatar

Alina Wright

Zendesk Product Manager

Daniël Nieuwendijk So, what we've been doing is to have Groups that are aligned with Brands, with Triggers assigning tickets in Brand A to Group A, tickets in Brand B to Group B, and so on. Team members have roles that only allow them access to ticket in their own groups. If I understood the announcement correctly, using Department Spaces i.e. Brand membership would have pretty much the same result as what I've described, wouldn't it? :

Alina: Not quite. With Department/Brand Spaces (I'm going to use Brands for ease of use), we're now creating partitions between brands. Ticket access is walled off between those Brands. That means you could use ONE group across all those Brands, have team members belong to a single brand and still only access those tickets within their brands. For example:

 

Alina belongs to Brand A.

Daniel belongs to Brand B.

Alina & Daniel belong to Group ESCLATIONS!

Alina can only see tickets that are assigned to Brand A and Daniel can only see tickets that are assigned to Brand B.

 

As an admin, you now only have to manage one group.

 

You can also imagine many other use cases here. You can use brands are departments (IT, HR, Legal), or perhaps you really don't want agents to see one another's tickets at all, ever. You can separate them that way. Lot's of new use cases to explore now!

 

-----

 

Bill Reed You say “Do not use this feature if you are currently using Chat, messaging, or Talk.” Can you elaborate on this? Why doesn't it work/shouldn't we use it? Is there some alternative if we're trying to keep certain agents to a certain brand?

 

Alina: Those features currently using routing and they are not brand aware in terms of team membership. You really COULD use messaging and omnichannel routing, but you'd have to be very careful and follow this guide and be diligent about checking to make sure your groups and agents are properly configured. The worst that can happen is that some tickets can get stuck in a queue because the ticket gets routed to someone that doesn't belong in a brand. There is no risk of exposing a ticket to someone who shouldn't see it, just a risk of a ticket getting stuck. We're working on making these routing features and department spaces compatible, but in the meantime, we recommend just keeping all your team members across all brands as before. You should see those updates in the next few quarters.

 

1


This looks great, however, we cannot begin the set up process on our enterprise account as there is no option to manage brand membership for any team members. The column doesn't exist when viewing the members, and we cannot manage multiple unless we use the old team members bulk manage page, is there something else we need to enable? We have multiple brands configured and cannot seem to associate individual team members to brands. Alina Wright :)

2


same as the above.  When does this feature rollout?

0


Same as the abovem when does this feature rollout?

 

Kristie Sweeney 

0


not getting any option for Manage Brand Membership

0


image avatar

Kristie Sweeney

Zendesk Documentation Team

Hi Bruno Gabriel James Molina prakash.sati - The rollout has been extended through December 12th. See Announcing Department Spaces for the latest info.

0


Kristie Sweeney, it's not out yet :/

 

Our team needs this function.

0


image avatar

Alina Wright

Zendesk Product Manager

Hi Bruno Gabriel - the roll out has been extended again to ensure it's a good experience for all of our customers. Could you email me directly at my first name, last name @zendesk.com and I can activate for your account?

1


Alina Wright I've sent you the e-mail.

0


Alina Wright:  I could see the option yesterday but not today. till what date it has been extended?

0


It doesn't really work as initially advertised. Lets say I restricted an agent who is working on brand A to brand A, and then when clicking ‘New ticket’, they can still choose to create the ticket as brand B, ‘Brand restriction per agent’ has not been achieved. 

0


Hi,

I have checked  but couldn't find any information in the API about this.  Is there an endpoint to get users' brand affiliations, or is there any intention to provide this information?

0


image avatar

Alina Wright

Zendesk Product Manager

Thomas Johnson - if you don't want an agent to create tickets in other brands, head over to Admin Center > Roles > click into the role you'd like to change > update the permissions to one of the following:

Brands they can assign tickets to

- Only assign tickets to brands they belong to

- Assign tickets to any brand

 

We will be introducing more granular permissions around ticket creation. 


James Peterson - Eastern Logic  - unfortunately that API is not currently available publicly. I'll work with the owning team to see what that would take to make happen. Can you tell me a little about your use case?

1


image avatar

Alina Wright

Zendesk Product Manager

prakash.sati - we will resume roll out next week with an end date of end of February. 

0


Hi Alina Wright,

I work with Zendesk apps, and I'm looking to further extend our data exporting capabilities for users, and data analysis for brands.  So we want to be able to include the brand information when exporting users to provide the stakeholder with clear information about the agents brand memberships.  From the brands perspective, we have worked on several brand 'migration' projects in the past and anticipate will need to do so again in the future, and so we will need to take agent brand memberships into consideration when migrating a workflow out from Brand A into a separate Brand B.
Thank you for your consideration ~

0


Could you please let me know if Zendesk plans to limit access to end-user profiles depending on the brand an agent is linked to in the future? We often receive enquiries about whether this is possible within Zendesk, restricting agent access to specific customer profiles.

1


I don't see mention of reporting/Explore limitations based on Brand assignments. Similar to the new improvements in Roles for scoping Explore data access based on group assignments.

Will agent Brand restrictions also restrict ticket data access in Explore to their assigned brand's tickets?

If Explore won't honor brand restrictions, this should be called out in the Limitations section until addressed. 

3


Does this change impact access to the Help Center articles? Can I restrict a specific set of customers to only a set of articles using the new branding/department spaces feature? 

1


What is the the expected behavior when an Agent is creating a new ticket and Brand spaces is turned on.?

We have found that only Agents associated with the default brand can create a new ticket.  Agents aligned with an alternate brand are unable to create new tickets.  

How do team members associated with a brand that is not a default create a ticket on behalf of a requester?

1


I've already submitted a separate ticket on this, but we're seeing newly added agents having their brand appear blank?? We only have one brand, but they were not assigned to this by default as they have in the past.

 

Also, can there be an easier way to add/remove users from a brand? Why not have a “Brand” menu option to Manage Users in Support? Or in Admin Console to go to Team Members > 3 dots > Brand? Or in the Admin Console for there to be a main menu option for Brand and Brand Membership (add/remove users)?

0


image avatar

Alina Wright

Zendesk Product Manager

Question: I work with Zendesk apps, and I'm looking to further extend our data exporting capabilities for users, and data analysis for brands.  So we want to be able to include the brand information when exporting users to provide the stakeholder with clear information about the agents brand memberships.  From the brands perspective, we have worked on several brand 'migration' projects in the past and anticipate will need to do so again in the future, and so we will need to take agent brand memberships into consideration when migrating a workflow out from Brand A into a separate Brand B.
Thank you for your consideration ~

 

Alina: Just so I'm understanding correctly, you want to ensure we add ‘brand’ to the export when exporting user data? Adding to the feature request list. Thank you!

Question: Could you please let me know if Zendesk plans to limit access to end-user profiles depending on the brand an agent is linked to in the future? We often receive enquiries about whether this is possible within Zendesk, restricting agent access to specific customer profiles.

 

Alina: Yes! I don't have a timeline to share but we are working on this.

Question: I don't see mention of reporting/Explore limitations based on Brand assignments. Similar to the new improvements in Roles for scoping Explore data access based on group assignments.

Will agent Brand restrictions also restrict ticket data access in Explore to their assigned brand's tickets?

If Explore won't honor brand restrictions, this should be called out in the Limitations section until addressed. 

 

Alina: Yes, agent brand restrictions also restrict ticket data access in Explore in the FUTURE. Thanks for calling this out, I added it to the Limitations section.

Question: Does this change impact access to the Help Center articles? Can I restrict a specific set of customers to only a set of articles using the new branding/department spaces feature? 

 

Alina: You can do this today through user segments in Guide. 

 

Question: What is the the expected behavior when an Agent is creating a new ticket and Brand spaces is turned on.?

We have found that only Agents associated with the default brand can create a new ticket.  Agents aligned with an alternate brand are unable to create new tickets.  

How do team members associated with a brand that is not a default create a ticket on behalf of a requester?

 

Alina: Make sure the agents have the right permission to create new tickets on their role settings. They should be able to create new tickets. We did have a bug that we fixed, please try again and let me know if you're still experiencing issues. 

 

Question: I've already submitted a separate ticket on this, but we're seeing newly added agents having their brand appear blank?? We only have one brand, but they were not assigned to this by default as they have in the past.

 

Also, can there be an easier way to add/remove users from a brand? Why not have a “Brand” menu option to Manage Users in Support? Or in Admin Console to go to Team Members > 3 dots > Brand? Or in the Admin Console for there to be a main menu option for Brand and Brand Membership (add/remove users)?

 

Alina: I'm assuming those agents were in a downgraded state at some point when we ran a backfill. You can read more on that here. It won't happen again from here on forward. We're making enhancements on agent brand membership. We're adding an ability to manage the brand from the agent profile.


 

1


Please sign in to leave a comment.