Reader Question: How Do I Restrict Content by Role in the Same Output?
I recently received the following question from a reader:
I just found out that our next-gen cloud-based Help needs to filter content — when our user logs in, she must see only info for the products her company bought AND the role she holds.
In your exploration of dynamic help, have you found any out-of-the-box solutions that include single-sign-on? Author-it Aspect seems close; maybe MindTouch, too. Zendesk filters, but can't do complex content.
If I were to pull this off, I'd also need to solve how to integrate my API references from Sandcastle. But first things first. :-)
I offered to post the question on my site to see how other tech writers might have handled this situation. I think it many cases, it can be tough to draw lines between what content each type of user should see. But if one customer has version A and another has version B, then it would be cool to have your help default to the software the user has.
I bet there are a variety of solutions. The traditional solution is to create different outputs for each role and then connect the help button to the role. But I think you want all content in one output.
In Drupal, you could use the Content Access module to restrict content types or articles based on the user's role. However, it seems like it would be a nightmare to try to sort out all the permissions. Also, I'm not sure how you'd map your customer roles into the Drupal roles. It might be easy, or require some custom development.
I once saw an Author-it Aspect demo of this capability and was impressed, but never moved beyond that.
I bet many content management systems have sophisticated access control mechanisms. It depends how much your company can spend.
You could also have developers in your company build a custom system.
I'd Rather Be Writing Newsletter
Get new posts delivered straight to your inbox.
About Tom Johnson
I'm a technical writer based in the California San Francisco Bay area. In this blog, I write about topics related to technical communication — Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, academics, and more. I'm interested in , API documentation, visual communication, information architecture and findability, and more. If you're a technical writer of any kind (progressional, transitioning, student), be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.