The access methods for a project are as follows:
Allows users to view a project and its associated lifecycle, view all views in the project, view the packages, package groups, and review requests that are in the project.
View access to an object does not prevent a user from being able to modify objects in the original object. For example, a user with View access to a project can have Update access to states in that project. In this case, the user can modify the state properties, but not the project properties.
Defines who can view and modify the properties of a project and all of the objects (states, processes, packages, package groups, and views) in a project. With Update project access, the user can also set access to states and processes.
This method of access also defines who can create and delete package groups, states, processes, views, and who can delete packages. State and process Update access can also be set at the state level by using the Update Access method. This is useful when you want to allow only specific groups to have access to particular states and processes but not the project.
Defines who can set access for the project. The secure project method does not imply being able to delete or update an object. Users with access to the secure project method must explicitly give themselves access to other methods; they are not automatically available.
Allows users to view a project and its associated lifecycle, view all views in the project, view packages and create, delete, update package groups and review requests that are in the project. To run any process in a project, the user must have Use access at the project level with Execute process access at the process level.
|
Copyright © 2013 CA.
All rights reserved.
|
|