Support Admin

The only issue with this method is it is sort of a black tape approach. It just hides the content from being displayed rather an inhibit the content from being rendered. In other words, you can still see the original content if you inspect the page's HTML (and theoretically searchable).

So do not use this method to hide sensitive or confidential information.

This is great, and I was ready to sign us up for EAP. But I see it is only available to top tier plans. I don't understand why such a very basic feature (transclusion) would only be available at the Enterprise level, a level for which there is no public pricing. And like another poster, I have proposed moving all our KB to Drupal which can support this kind of feature out of the box.

Are there plans to make this available to all plans? 

Coming up on seven years that this request has been open. Again, seems a fairly basic feature.

Because it seems that ZD will never support this extremely simple feature, and if they do, it will only be for Enterpri$$$e customers, I have proposed to my company that we move to having our KB be hosted in Drupal where we have much more control, and can easily support this function plus shared blocks of content.

Hello @...,

No, I did not try the custom field approach because it won't work for assigning a user to a user segment. That assignment is only based on "real" tags (no support for user fields). In other words, this method doesn't accomplish what the title says.

All this method does is to provide a way to initiate a trigger based on a custom user field (sort of the wrong direction ;-) ).

So is there another way to add a user to a user segment via a trigger?

Sorry, but I am not seeing how this adds a tag to the user profile. Are some steps missing?

My use case (as it is for many others) is to trigger off the user tag to assign a user to user segment (which only works off tags, and not any other fields), for example, to control visibility to articles.

How can automatically add a tag to the user profile?

The view condition "Ticket: Requester" seems illogical. If I set this condition, I cannot select any requester who is a user, or what is 99.5% of the situation. I can only select an agent, but I already have the condition assignee for that. Does NOT seem useful at all? What am I missing?

My use case is I want to filter out test cases from user TEST. But cannot do that with the condition which seems like it should.

Is this article still accurate? I don't see anything like this in my instance. Yes I can go to Account and Reports, but I have to create a Report first with limited settings, and then I can export, but only to CSV and XML, no JSON.

We are on Suite Growth, BTW

Just a little late for this topic's 10th anniversary!

How do we test the new workspace if we do NOT have access to the premium sandbox?