You can set up read/write security at many levels. You
can have only a small set of rules, or be restrictive in who has access
to what information. For best results, become familiar with the group
security capabilities by reading the information in this section,
and then define a small set of rules. Then you can understand how
the rules work and test a small set of rules before defining additional
rules.
About this task
If you want to implement read/write security rules, you
have probably already identified some area of your change tracking
system where you need to regulate access. What follows are a few examples
of how you might want to control how information is viewed in IBM® Rational® Change.
- Your company has several product lines, and you want to restrict
problem information for a given product only to employees working
in that product group.
- Your company uses contract workers. The contract workers need
to access Rational Change
to fix problems in CRs assigned to them. However, you do not want
them to be able to view any other CRs.
- Your company needs to control read and write access for tasks.
You want everyone in your product division to be able to view them.
However, you only want the people in the development lab to have write
access to the tasks.
Procedure
To plan read/write security rules:
- Understand how read/write security works in your organization.
- Plan your read/write security and define your groups.
- Define your rules.
- Review your change request process and lifecycle.