Module · Team
The right people, on the right project, with the right view.
Assign Lead PM, Lead CM, Cost Coordinator, designers and consultants to a project. Role-aware permissions mean QSes see commercials, designers see designs, clients see what you choose to share — without manual gating.
Why team management goes wrong
Project access is too coarse, or too fiddly, in every other tool.
You either give everyone access to everything (fine until the consultant sees the cost report) or you spend your day adjusting per-folder permissions. There is no middle path in most consultancy stacks.
Everyone-or-no-one access
Most tools have one switch: in the project or not. The result is a designer with cost-report access, or a QS unable to see the project they're leading.
Permissions per folder
The alternative — folder-level access lists — turns project setup into a half-day of permission micromanagement. Nobody scales that.
No record of who is on what
When the senior QS goes on leave, nobody knows which projects they're Lead on. The phone calls start; the projects drift.
What's inside
Project team assignment with sensible defaults.
Named project roles
Lead PM, Lead CM, Cost Coordinator, Lead Designer — explicit project-team roles, separate from workspace user types. One person can hold different roles on different projects.
Role-aware module visibility
Designers see designs, QSes see commercials, CMs see programme + site reports. The defaults are right; per-workspace overrides exist if you need them.
Designer / consultant access
Add external designers and consultants to a project with limited scope — they see what they need without seeing the cost report.
Team change audit
Every team change (added, removed, role swap) is logged. When the dispute asks "who was Lead CM in March?", the answer is one query.
Notifications by role
Variation approvals route to the Lead Cost Manager; site report alerts to the Lead CM. Notifications follow the role assignment, not a per-person ping list.
Workspace-wide team browser
One view across the workspace: who is on what project, in which role, with which capacity. Replaces the "ask the office" capacity check.
Who uses it
Built for the people staffing projects — and the people landing on them.
Directors / Heads of Ops
Workspace-wide view of who is on what. Capacity decisions get made on data, not on remembered conversations.
Project Managers
Assign your team in one screen. Each member sees the right modules with no manual permission setup.
External consultants
Limited-scope project access from a clean profile. No accidental access to cost data; no friction filing your contributions.
See team assignment that respects role + project at once.
A 20-minute walkthrough on a project of your choosing — bring a typical team shape.
Frequently asked questions
How do project roles relate to user types?
User types (Project Manager, Cost Coordinator, etc.) live at the workspace level — they define what a person CAN see by default. Project roles (Lead PM, Lead CM) live at the project level — they define what a person IS on this specific project. The two combine to drive what the user sees.
Can a person be in two project roles?
Yes — a senior PM can be Lead PM on three projects and Project Sponsor on five. The team browser shows their full assignment list.
How granular is the access?
Module-level for now (cost report, variations, programme, designs, etc.). Per-package or per-document gating is on the roadmap for sensitive workflows.
Connects to
Other Projavio modules that work alongside this one.
Project Workspace
The project workspace every internal user lives in. One project record — every other module hangs off it.
Project Onboarding
Capture the project setup once. Drives every downstream module — no separate "setup" workbook.
Risk Register
Project risk register with likelihood × impact scoring, mitigation owners, status, and close-out trail.
Stop running team access on a folder permission spreadsheet.
Role-aware project teams that scale to 60 live projects without permissions chaos.