We have the exact same issue, needing to create increasing multiples of user segments which has been getting out of hand.

Maybe there's more to it, but the ability to have a Guide article visible to multiple user segments seems a simple fix to this issue, which everyone in this thread appears to fully agree to.

We use Zendesk internally and are migrating from Jira/Confluence on a per-team basis, promising employees that Zendesk is the future, but don't have an answer for restricting access per article/section to users/groups, which they are used to being able to do. Instead, for each user/group requested, we have to create multiple user segments, try to explain why an article they post has to be visible to a very specific one of many user segments, and encourage employees to avoid granular access as they have been used to. We've tried mapping out user segments per team, role, region, and also found that a sync from Okta deletes custom user tags, which broke our original workaround setup.

To allow Guide articles to be visible to multiple user segments would be (I assume) a relatively easy win, that would fix a frustrating issue and help many existing and new Zendesk customers.

Do the Product team have an update since the reply two years ago? Please let me (or any of the others in this thread) know anything more that can be done to bump this request as it'll be hugely appreciated.

Thanks in advance!