Secured!
Security is not the most exciting topic in the world. But, it is one of the most important, particularly if you will be collecting important and valuable information on a cloud-based system. All the information found in a PPM (Portfolio and Program Management) system, like P3M Engine, must be secured. Securing that information properly is not as simple as giving someone login credentials and granting them access to their own account. There are many different roles to consider. Business sponsors, stakeholders, program managers, project managers, PMO Leads, business analysts and others all have different responsibilities and want different things from their tools. Each of those roles will be engaged in project work. So, they will be part of one or more project teams. Or, they may have oversight or administrative responsibilities for many or all projects.
In consideration of the special nature of program and project work, P3M Engine incorporates security that supports both the roles and team assignments of each user.
P3M Engine includes role-based security. With role-based security, what screens you see and what features are available on each screen depends on your role. A project manager, a PMO analyst, and a project stakeholder can all see the same screen but will see different features or data on that screen. For example, often, stakeholders can only view information, whereas the PMO analyst and project manager may create and edit also. A PMO Lead or administrator can see configuration screens and setup configurations. Other roles cannot see these screens or the links to these screens.
Role-based security accomplishes this.
·It prevents users from accidentally altering the behavior of the system or creating unwanted outcomes by taking actions for which they have not been trained or for which they do not have responsibility or accountability.
·It optimizes the user experience to be the most efficient and effective by tailoring the experience to each role.
P3M Engine offers team-based security. Users can see only information anchored to the team (program or project) to which they are assigned. For example, suppose Jim is on Team A and Sue is on Team B and they both look at team risks. They will be viewing the same screen, but Jim will only see Team A risks and Sue will only see Team B risks. Carlos, who is assigned to both teams, will see the risks from both Team A and Team B. None of them will see the risks of other teams. Team-based security accomplishes two things.
·It prevents users from seeing information they should not see, for security reasons.
·It keeps their screens from getting too cluttered and helps them find information more quickly and easily. The information they see will always be relevant to the work they are performing.
This approach ensures that each team member sees all information relevant to the team. You do not have to author information to see it. That means if someone else creates a team risk or issue, you will be able to see it.
Some roles, such as administrators, PMO Leads, and PMO Analysts are expected to work across all projects. So, P3M Engine is smart enough to grant them access regardless of team assignments. That way administrators do not need to hassle with innumerable team assignments.
While security is table stakes for all cloud-based systems, not all cloud-based systems incorporate good design. P3M Engine security is designed from the ground up to enable smart project-based work. Good design pays dividends in the future with simpler and safer maintenance.
Work smarter, not harder.
Get more information at https://www.p3mengine.com.










