VOB and view access control

Access controls determine which users can create, read, write, execute, and delete data in VOBs and views. Access control depends on the interaction of users and the groups they belong to, the protections on Rational ClearCase objects, and the credentials of user processes or application programs that access Rational ClearCase data on behalf of users.

• Users and groups
  A user's name and group memberships are the principal credentials evaluated by Rational ClearCase when access is requested.
• Protected objects and protection modes
  Every kind of protected object has one or more protection modes.
• Access control for VOBs and objects they contain
  VOBs are the principal repository for protected objects. Most access control operations apply to VOBs and objects they contain.
• Access control for views and objects they contain
  Views enable user access to VOB data. As with VOBs and objects within VOBs, views participate in access control. In a dynamic view, permissions on elements and versions interact with permissions on views and view-private files or directories to control access to both VOB and view data.
• Rational ClearCase and native file-system permissions
  Rational ClearCase requires specific file-system permissions on storage directories for VOBs and dynamic views. These permissions are established when the directories are created and must not be changed.
• Windows shares for VOB and view storage
  On Windows platforms, VOBs and views that are accessed over the network must be created in a folder that is shared. Windows share permissions control access to shared folders, and must be configured to provide adequate rights to users of VOBs and views.