Project Management Cloud Configuration and Setup
What the domain tests
The Configuration and Setup domain checks whether you can configure the shared foundations that every project uses: project business units, project types, project templates, roles and security, action controls, planning and budgeting options, and approval workflows. The exam expects you to know which object controls behavior and which object supplies defaults.
Core rules
- A project business unit is the container for project accounting and project execution. Legal entities own accounting and tax; do not configure project behavior on the legal entity.
- A project type controls behavior: task hierarchy, cost and revenue processing, billing, planning, and which actions are allowed. A project template supplies default values and can reference a project type. Templates do not replace types.
- Project roles and security determine who can see and act on a project. Team members inherit project access through roles.
- Action controls map project statuses to allowed actions. For example, you can prevent cost collection or invoice generation until a budget is baselined.
- Planning and budgeting configuration defines plan types, financial plan types, budget types, and baseline behavior. Approval workflows route through BPM worklist.
Worked example
A construction firm needs capital projects to require a baselined cost budget before suppliers can charge costs. Configure a project type with a three-level task hierarchy, enable cost budgeting, and set action controls so that expenditure entry is blocked until the budget is baselined. Create a template that references the type and defaults the project manager role. Reasoning: the type enforces behavior; the template speeds creation; the action control enforces the gate.
Traps
Do not confuse project type with project template. Do not put project accounting options on the legal entity. Do not assume a status change automatically baselines a budget. Test action controls with a project in each status.