ProjectProfile REST Endpoints
A project profile defines a set of privileges for access to project-specific information. Project profiles are assigned to users based on the OBS hierarchy. To control access to project-specific information, you create project profiles, and then assign specific OBS elements and associated project profiles to individual users. The assigned OBS element determines the EPS and WBS elements for which the user can access project information. The assigned project profile determines the type of access privileges the user has to that project information.
All WBS elements are required to have an assigned responsible OBS. If a user's project profile assignment includes a WBS element's responsible OBS, then the user can access all activities, risks, and issues related to that WBS element. Similarly, all thresholds and project issues also have an assigned responsible OBS. If a user's project profile assignment includes a threshold or issue's responsible OBS, then the user can access that threshold or issue.
A user is not required to have a profile for every project. However, unless a user's global profile is Admin Superuser, that user cannot access a project without a project profile. To allow complete access to a project/OBS assignment, a project profile is included named Project Superuser. You can apply the Project Superuser profile to as many users and for as many projects as you like.
- Create ProjectProfile
- Method: postPath:
/projectProfile - Delete ProjectProfile
- Method: deletePath:
/projectProfile - hasPrivilege
- Method: getPath:
/projectProfile/hasPrivilege - Read ProjectProfile
- Method: getPath:
/projectProfile - Update ProjectProfile
- Method: putPath:
/projectProfile - View ProjectProfile Field Length
- Method: getPath:
/projectProfile/getFieldLength/{fieldName} - View ProjectProfile fields
- Method: getPath:
/projectProfile/fields