TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Shannon, I'm also fairly new to RoboHelp - but I've been using conditional
build tags for the same problem and find it works for me. I write help for
users and support staff and learned how to use the feature from RH's online
help.
I "blank" out what I want to hide from each user by creating and applying
conditional tags for each user, hidden author content and revisions for
testers. Compliled content is managed through setting up conditional
statements, defined in a single source layout for each user, before you
compile your "customized" help file. I find it a very useful feature, but
in a file with over 1000 topics, it makes authoring more complex and very
interesting at times!! You can get strange unexpected results if you forget
to set the appropriate conditions before compiling.
However, you can keep track of what tags are applied to which topics via the
Advanced tab on the topic properties dialog. Select a tag, then click the
properties button for the seleted tag to display a list of all topics that
have the tag applied. Also, from the View menu, select "show conditional
areas" via the Show option. Experiment with setting up a vary of
pre-compile conditions in a single source layout for each user, on a small
test file first.
I also use the tags to mask "original" topics that I am revising, then
produce small review help files by tagging the "old" vs the "new". Once I
get signoff on the revised content, I remove the tag and it becomes part of
the complete help file.
-----Original Message-----
From: smorris -at- moworld -dot- net [mailto:smorris -at- moworld -dot- net]
Sent: Monday, March 31, 2003 10:42 AM
Subject: Creating Online Help with Multiple User Permissions
I am working on a help system for an application where there are 4 levels
of permissions.....
For example:
Basic User (strictly the ability to view content, all users have this
capability)
Content Owner - who can modify only content they own
Data User (there are 2 separate permissions within this section -
X content modifiers and Y content modifiers - they each have specific
content they can modify but won't have access to modify outside of this.
So, X can only see their category and Y their category.
SysAdmin - who is responsible for user maintenance and auditing
I would prefer to create one help file that would contain all of the
necessary information. My question is this: Is there a way to do this? I
am using RoboHelp and I am relatively new user. Any suggestions, insights,
or experience are happily appreciated. I searched the archives but was
only able to find something in Oct 2001 about developing a manual with a
similar scenario.
I receive the digest, if you could reply to: smm -at- usp -dot- org -dot-
Thanks,
Shannon
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/techwr-l
Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....
---
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.