Project governance is the method for ensuring a project can resolve issues and remains within its defined delegations of scope and outputs. Typically, governance involves defining the project roles and responsibilities, communication processes, methods, tools and approval requirements.
UniPhi manages project governance through a combination of licence levels and organisation specific roles. There are four licence access levels:
Administrator
Program Manager
Project Manager
Team Member
Discussion on these three party role levels (i.e. subscription, role and access level) needs to be broken down into read, create, update and delete and into module by module review.
Read access is controlled by the system wide subscription a person has.
Program manager subscription level can read data on every project (excluding private projects) in every module in the system regardless of whether they are on the project or not. Project manager subscription level can read data in every module for projects that they have been allocated to. Team member subscription level can read data in the documents, issues, risks and resources module for projects they have been allocated to.
Create and Update is controlled by the access level of a role on a project.
For all subscription levels other than administrator, you can only create/update information if you are on the project. What you can update on a project depends on what access level the role that you are allocated to on the project is. A role with a program manager access level has full functionality across all modules for that project. A role with a Project manager access level has full functionality across all modules except resources which is configurable at the deployment level to be either full access or read only. A role with team member access can only create documents, issues and risks, update their own documents, issues and risks but not their associated ratings or due dates
Special cases
Documents
Documents have their own party role model configurable by the system administrator. The administrator controls read rights to documents via the setting a templates view rights to an access level on the project (e.g. view only by program managers means you need to be in a role with program manager access level to view documents created from the templates). Create and update is set by selecting admin defined roles to be able to edit documents created from the template. This ignores the access level and focuses purely on the role. Sign off is set by selecting admin defined roles and ignores access level.
Risks
Program Manager Subscription can read all risks across the system and create, update and delete all risks on projects their allocated to a role with program manager or project manager access level. If they are allocated to a role with team member access level then for that project they can only create and update their own risks and cannot change ratings or due dates. Project manager subscription can read, create, update and delete all risks on projects their allocated to a role with program manager or project manager access level. If they are allocated to a role with team member access level then for that project they can only create and update their own risks and cannot change ratings or due dates. Team member subscription can read all risks on projects their allocated to and create and update their own risks. They cannot edit due dates or ratings.
Reports
The reports sub nav is configured deployment by deployment at the subscription level e.g. you can have only admin access a reports sub-nav or program manager and above or project manager and above or all.
Comments