Differentiate Community Users as a subset of Help Center/Support users
AnsweredWe would like to differentiate Community members from Support users so that 'joining' the Community is an additional step for a user. I know there are user segments that can be used to hide or display articles and topics, but we want the entire Community hidden unless/until the user elects to 'join' the Community. The support response was that all we can do is restrict access to Articles/Topics (which we knew and tried).
We would like to have an overall restriction (possibly based on user segments) that determines whether the current user can see and access the Community.
-
You may be able to do this today. It would require some development work, but it’s possible. I’m not at a place where I can get specific on the steps here, but I have a few moments to give you a quick run down of what you could do.
- Use CSS to hide the community elements by default.
- Use Javascript to show those elements based on a user tag
- Setup a ticket form to enable to community
- Build a trigger to check a requester custom checkbox (user field) if that form is received (if you don’t have ticket forms, you could build the trigger off of a checkbox or other field on your primary support form. You could also set the trigger to add the tag based on an email to a specific email address). Make sure that the tag that is assigned to your custom user field checkbox is the same as what you have enabled for viewing the community.
This trigger should set the tag that tells the javascript to unhide the community for that person and could potentially make the community fairly immediately available since the update would be automated through the trigger. Hopefully this works. I can try to circle back later with more detailed instructions on what I’m thinking here.
Post is closed for comments.
1 Comments