Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 2 · Security and Data Access
Project unit and project-level access
Lesson 18 of 198 · 12 min
Show project unit access and how it scopes what a user sees. Project units are built in Module 3 — the forward dependency is flagged clearly rather than left to confuse you. Add a user to a project team with a project role, sign in and show the project now visible and manageable, remove them and show it disappear, and show a user with business unit access but NO team membership — and what they can and cannot do. Then the project manager assignment specifically. This lesson is partly forward-referenced, and says so — learners get anxious when a walkthrough depends on something not yet built, and the anxiety costs more than the gap does. TEAM MEMBERSHIP IS DYNAMIC AND SELF-SERVICE IN A WAY SECURITY GRANTS ARE NOT. A project manager adds people to their team. That is a feature, and it is also a control question: who can add…
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.
In this module: Module 2 · Security and Data Access
- 1The PPM security shape
- 2Project role versus job roleFree preview
- 3The roles a PPM project needs
- 4Provisioning users
- 5Business unit data access
- 6Project unit and project-level access
- 7Segregation of duties in project accounting
- 8What breaks
- 9Lab: build the access matrix, then build to it