Creating one help system for user groups with different access rights

[rahuja -at- carekey -dot- com]

Hi, All.

I am creating help using RoboHelp for a web application that, based on
your login, displays different menu options. For example, Company A bought
our product with X features. Company B, on the other hand, bought the
product with Features X and Y. I would prefer to not create a generic help
system that covers ALL features because it might be confusing to those
users who will not have access to nor see those features.

But outside of creating separate help systems for each type of login
group, I don't see how I can address this issue. I called RoboHelp to find
out whether it is possible to create multiple TOCs for the same help
application --  I'm still waiting for the call back. Has anyone else
encountered this? If so, how did you tackle this problem? The product is
customized to some degree for each new client. Creating multiple help
projects for each login group will create a huge update issue as the
number of clients increase because most of the help pages will still apply
to all users.

Thanks in advance for the advice!
~Rasil

Rasil Ahuja
CareKey, Inc.
rahuja -at- carekey -dot- com
617.375.6700 ext. 25


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.

A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.