Managing read/write security through access control lists
Read/write security features work with lifecycle and project
security. You can define read and write access to change requests,
tasks, and objects based on the group membership of a user.
Read/write security overview
IBM® Rational® Change ships with read/write security
features that work with lifecycle and project security. Using read/write
security, you can define read and write access to change requests,
tasks, and objects based on the group membership of a user. This topic
contains a detailed overview of the information you need to consider
before you begin defining security rules.
Planning read/write security rules
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.
Change request process and lifecycle security review
Now you have a basic understanding of the capabilities
of the read/write security features used by IBM Rational Change.
Before starting to define read/write security rules, review the CR
Process and lifecycles you are using.
Rules definition
Once you have identified the groups and attributes, map
out a set of rules, or access control lists (ACLs), that correspond
to your security needs. An ACL is a collection of rules that control
read and write permissions. Using ACLs, you can define specific rules
for a group or groups of users.