The help project contains three types of topics:
My plan was to use dedicated topic-level build tags and dedicated content-level build tags to generate/deliver 2 different outputs (and also support the filter tool): one for our customers (without proprietary and confidential info) and one for our tech support dept. (with everything).
Our software product is cloud-based, so the customer help will be too. Our dev team is using Auth0 (auth0.com) to manage/control customer access to our software, and they (our dev team) asked whether it would be possible for us to generate/deliver/host/maintain only one help output, and then use authentication (Auth0 in this case) to control who can access/view the different types of help content.
Highly doubt that you can bundle it all in 1 help package, but why bother? Drive space is cheap & your Auth0 thingie should just be able to redirect users to whatever version they are allowed to see.
I agree with Jeff. Without Rh Server, which has a cost, you will probably spend more on developing your own authentication than if you just generate two outputs.
Filtering will not work here as you have content that you don't want customers to see. Otherwise that would have been a solution.
See www.grainge.org for free RoboHelp and Authoring information.