Project Security Profiles

The project security profile is a subset of the project role, and is the final authority for determining access to projects, activities, and transactions. Project team members with the same project role have the same security profile and access to the same data.

The security profile defines a user's access type—no access, read-only, or read and write permission—to project data. The profile defines access to transactions based on analysis groups. After you define an access type and analysis groups for a project security profile, all users or permission lists that are attached to the profile acquire that access type.

Project security profiles are keyed by tableset ID and can be different for each business unit. For example, a security profile for business unit 1 can grant access to a greater level of data than the same security profile in business unit 2. You can also create different project security profiles for different projects.

This table lists examples of project security profiles and their typical functions:

Project Security Profile	Typical Functions
Project manager, project owner, application administrator	Create projects and activities, budgets, cost analyses, forecasts, and status. The security profile typically provides read/write access to projects and activities for transactions in all analysis groups.
Project accountant	Generates bills, creates assets, and performs other accounting functions. May perform project manager or application administrator functions.
Project team member	Reviews project and activity status and schedules. May require read-only access to specific project components.
Vice president, executive, or high-level manager	Inquiry of overall project status such as total revenue and gross margin.