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.
Subject:Re: how to document multiple user roles? From:kcronin -at- daleen -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 3 Oct 2001 15:34:31 -0600
How big a difference is their between A, B, and C users? Is it
hierarchical - are there users with "higher" and "lower" levels of
security? Or are they just DIFFERENT levels, not higher or lower in
respect to each other?
If it's not based on higher/lower permissions, then you should be able to
create some kind of schema for presenting the information, and label it
clearly as such. Maybe something like this might apply:
Stuff that applies to everybody (if this is applicable)
Stuff you only need to worry about if you're an A user
Stuff you only need to worry about if you're a B user
Stuff you only need to worry about if you're a C user
Not knowing when and how these levels are applied, it's tough to approach
this.
If it's a situation where within a given process, there would be a point
where an A user would stop and a B user would keep going, then you can
give tips (or warnings) that clearly mark those boundaries.
But if the permissions are based on higher/lower comparisons, I think it
could get weird for people who do not have a certain level of permission
to be able to read the documentation for processes that somebody else with
a higher level of security can perform. If that's the case, it sounds like
the information should be separated into 3 separate documents.
Sorry - I haven't solved a thing for you, but I'd need to know more about
the situation. And then I'd know too much, and you'd have to kill me. :)
Planning to attend IPCC 01, October 24-27 in Santa Fe? Sign up by
October 3 and get a substantial discount! Program information,
online registration, and more on http://ieeepcs.org/2001/
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
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.
