how do I prevent Group sync between Zendesk and Zendesk QA | The place for Zendesk users to come together and share
Skip to main content
Question

how do I prevent Group sync between Zendesk and Zendesk QA

  • May 7, 2026
  • 1 reply
  • 16 views

I have 45 groups and only 3 of those belong in QA (and are already there).  How do I prevent all of this noise from being put in QA?

 

referencing https://support.zendesk.com/hc/en-us/articles/10547258131098-Announcing-Group-sync-between-Zendesk-and-Zendesk-QA 

1 reply

configly
  • May 11, 2026

Hi Eleanor,

You've timed this question well, the sync only rolled out on 12 May, so a lot of people will be looking at the same noise right now.

Two ways to handle it depending on how tidy you want things:

Quick fix: archive the unwanted groups in Zendesk QA. In QA, go to your profile icon, Users, bots, and workspaces, then Groups. Archive everything except the 3 QA groups. Archived groups disappear from dashboard filters and assignments but you can restore any of them later if your QA scope expands. The synced groups stay synced in the background, they're just hidden from the working views.

Cleaner fix: filter at the connection level. In QA, go to Settings > Connections, find your Zendesk connection and edit it. There's an "advanced options" section where you can specify which groups to include or exclude from sync. Put the 3 QA groups in the include list and the other 42 won't sync over at all. This is the better long-term option because new groups created in Zendesk won't auto-appear in QA either.

I'd go with option 2 if your QA scope is stable. Option 1 if you think the list of QA-relevant groups might grow over time and you'd rather see everything synced and just hide what you don't need yet.

One thing to be aware of: synced groups can only be edited or deleted in the main Zendesk Admin Center, not in QA. So if you do archive them in QA and later want to fully remove the noise, you'd need to delete them in Zendesk Support, which obviously affects ticket assignment and views in the main product. Archive is usually safer.