Structure WebHelp project that limits access to license program module users

Question

Where can I find information about the best way to structure a WebHelp project that needs to contain Help modules that will be accessible only to users who license the associated application? My project needs to contain core Help for the application and four modules associated with four licensable analysis program modules. I've done some research about merging Help projects, but that doesn't tell me how to set up the project or projects so that the user of program A, for example, can't see the Help for program B.

Captiv8r · Answer

Hi thereIf you created a Merged helpset, you could structure it so that the components that are merged in are placed in different folders. Then password protect those folder or otherwise restrict them so that only validated users could see them. When the master is launched, if it cannot get to one or more child projects, they aren't listed in the Table of Contents and in the Index and Search.I suggested this years ago for a product where I was the tech writer. The owner of the company decided on a different approach. His view?Since they can't do the functions the help is for anyway, what does it hurt to have it available? Further, if they haven't yet purchased a module that they have help for, perhaps by seeing the help, it will help serve as a marketing tool. By seeing what is possible via the help, perhaps they might be encouraged to purchase additional modules.Cheers... Rick Helpful and Handy LinksRoboHelp Wish Form/Bug Reporting FormBegin learning RoboHelp HTML 7, 8 or 9 within the day!Adobe Certified RoboHelp HTML TrainingSorcerStone BlogRoboHelp eBooks

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.