A security profile is a collection of security permissions. There are two types of security profiles: global security profiles and project security profiles. A global security profile determines the user's access to application-wide information. The global security profile provides read-only access to all global data except cost and resource data. Privileges can be added to global security profiles to allow users to add, edit, and delete global data, and view global cost data. A project security profile determines the user's level of access to each project within the enterprise project structure. When you assign a project security profile to a user, you also associate the project security profile with an organizational breakdown structure (OBS) element/responsible manager. When an OBS node is assigned to a user, the default project security profile is automatically assigned. The user's access privileges, as defined in the project security profile, will then apply only to those elements of the enterprise project structure (EPS) that are assigned to the OBS element/responsible manager you selected.
P6 Professional and P6 require that all users have a global security profile. As an administrator, you create global security profiles and assign individual access privileges associated with them. To control access to global information, you create global security profiles, and then assign them to individual users. If you want to give users access to all global information, create a global security profile with all privileges.
You can also choose to assign the Admin Superuser global security profile. Admin Superuser is an application-generated global security profile. You cannot edit the Admin Superuser profile. One user must have the Admin Superuser profile, and you can assign Admin Superuser profiles to as many people as you want, though you should limit the number of users you assign to it. An Admin Superuser can add, edit, and delete information by default, where all other users will have to be assigned the proper privileges to do so. You must be logged in as a user assigned the Admin Superuser profile to assign the Admin Superuser profile to other users.
To allow users to only see certain project information, you can create project security profiles. A project security profile defines a set of privileges for access to project information. You create project security profiles, then assign these profiles and specific OBS elements to users. The assigned OBS element determines the EPS and work breakdown structure (WBS) elements where the user can access project information. The assigned project security profile determines the type of access privileges the user has to that project information.
The application requires that all WBS elements have an assigned responsible OBS. If a user's project security 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, project issues also have an assigned responsible OBS. If a user's project security profile assignment includes an issue's responsible OBS, then the user can access that issue. You can assign a project security profile called Project Superuser, if you want to give a user access to all information belonging to a project. You can assign Project Superuser profiles to as many people as you want. Project Superuser is an application-generated project security profile. You cannot edit the Project Superuser profile. A Project Superuser can add, edit, and delete information by default, where all other users will have to be assigned the proper privileges to do so. You must be logged in as a user assigned the Admin Superuser profile to assign the Project Superuser profile to other users.