MSAMM
Back to course

Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 2 · Security and Data Access

The PPM security shape

Lesson 13 of 198 · 2 min

If you have taken any of the other three courses in this family, start here: this is a fourth security shape. It leans on business unit data access like Financials. It adds project-level access. And it introduces an object learners consistently misunderstand. The function security chain is the same as everywhere — user, role, duty, privilege. That part transfers. Three data dimensions stack in PPM. Business unit — which business units' project data you can work with. Familiar from Financials. Project unit — the PPM-specific operating entity, covered properly in Module 3. Project membership — whether you are on the project team, and in what project role. Why the third one exists. Project data is naturally scoped by project. A project manager should manage THEIR projects, not every project in the business unit. Team membership is how that is expressed — and it is the dimension that has no equivalent

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 2 · Security and Data Access

  1. 1The PPM security shape
  2. 2Project role versus job roleFree preview
  3. 3The roles a PPM project needs
  4. 4Provisioning users
  5. 5Business unit data access
  6. 6Project unit and project-level access
  7. 7Segregation of duties in project accounting
  8. 8What breaks
  9. 9Lab: build the access matrix, then build to it
The PPM security shape — Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue — MSAMM