Resource security enables you to restrict a user’s access to resources. Each user can have access to all resources, no resources, or a limited number of resources in the resource hierarchy. To provide access to a limited number of resources, you can designate each user’s root resource by assigning each user to a resource in the resource hierarchy. The position of the assigned resource in the hierarchy determines the user’s resource access. When the user logs in, the resource hierarchy displays only the assigned resource node and its children. Resources outside the user’s root resource are not displayed.
Note: Users with restricted resource access can still view and edit all current project resource assignments if they have the proper project privileges.
You can grant one of the following three types of resource access to each user:
Note: You can assign only one resource node to each user. Multiple resource nodes are not supported.
The following example shows how resource access is determined by the root resource assigned to different users.
Item | Description |
---|---|
| If USER1 has restricted access with root resource SADM assigned, USER1 would see only these resources in the resource dictionary. Includes the following resources: SADM, JSAN, FWIL, RCAR, EJOH, and MLAW. |
| If USER2 has restricted access with root resource SUPP assigned, USER2 would see only these resources in the resource dictionary. Includes the following resources: SUPP and FTAN. |
| If USER3 has no resource access, USER3 would not see any resources in the resource dictionary. |
See the P6 Help for more information on setting up the resource hierarchy.
Tip
All Resource Access is required for certain features in P6 EPPM. For example, you must have All Resource Access in order to import resources into the resource dictionary via Microsoft Excel (.xls) format.
Related Topics |
Legal Notices
Copyright © 1999, 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Thursday, February 04, 2016