Roles in GreenVee

GreenVee does not enforce job titles or lock users into rigid roles. Anyone with access can, in principle, view any part of a project they have been given permission to see. In practice, however, people use GreenVee in very recognizable patterns depending on their job.

This page describes the six common personas. Read the section that matches your role to understand which parts of GreenVee are most relevant to you — and read the others to understand what your colleagues are looking at when they ask you questions.

---

Project Manager

Lives in: the work plan (segments, tasks, milestones, gates), the project overview screen, status reports, and the Risks & Chances screen.

Owns: the overall project record (phase, dates, budget goal), the task structure, gate criteria, and project-level risk and chance entries.

Asks:

• Are we on schedule?
• Which tasks are blocked or overdue?
• What risks are open, and do we have actions in place? Are there chances worth pursuing?
• Are the gates ready to pass so we can move to the next phase?
• Is the project tracking to budget?

For Project Managers

Your mental home is the Two Views of a Project — specifically the work plan side. The phase field and gate criteria are your main tools for communicating project health to leadership. See also Risks and Chances — keep both registers current, not just the risk side.

---

Team Lead / Coordinator

Lives in: task lists filtered to their team, planned hours views, and team member booking screens.

Owns: task assignments within their area, planned hour entries, and the coordination between team members.

Asks:

• Who on my team is over-allocated or under-allocated this week?
• Which tasks are due soon and have not been started?
• Is there a booking conflict I need to resolve?
• Have all time entries been submitted for the period?

---

Engineer / Technical Designer

Lives in: the technical structure (node tree, required goods, specifications), the materials section, and procurement.

Owns: the node hierarchy for their area, required goods and their specifications, and technical details on the goods and variants used.

Asks:

• What needs to be installed at each location?
• Do the specifications on this component meet the contract requirements?
• Are all required goods accounted for in the technical structure?
• What materials are still missing or not yet procured?

For Engineers

The technical structure is your primary domain. See Two Views of a Project for why it sits parallel to — not inside — the work plan.

---

Field Worker / Operative

Lives in: their assigned tasks, time entry screens, and task-level material usage records.

Owns: time entries for the hours they work, task status updates, and usage records for materials consumed on the job.

Asks:

• What tasks am I assigned to today?
• How do I log the hours I worked?
• How do I record that we used materials on this job?
• What are the specs for the component I am about to install?

Note

Field workers interact with GreenVee mostly through task-level data. They typically do not create or edit master data, budgets, or risk entries — that work happens above them in the project hierarchy.

---

Finance / Controller

Lives in: the budget screens, cost items, cost occurrences, procurement orders, and portfolio-level financial reports.

Owns: cost item definitions, cost occurrence records, order linkages, and budget vs. actual comparisons.

Asks:

• What is the current committed spend vs. the budget goal?
• Are there cost occurrences that have not been matched to an order?
• Which projects are running over budget?
• What are the approved vs. actual costs across the portfolio?

For Finance

The key money chain in GreenVee runs: Project → Budget → Cost Item → Cost Occurrence → Order. A Cost Occurrence is the record of a specific cost event. If a number looks wrong, trace it back through this chain. See Occurrences for detail.

---

Executive / Portfolio Manager

Lives in: portfolio dashboards, program views, portfolio risk factor assessments, and milestone / gate summaries.

Owns: the portfolio and program structure, Portfolio Risk Factor definitions, and strategic targets.

Asks:

• How is each project tracking against its phase and milestones?
• Which projects carry the highest strategic risk?
• Are our resource and budget commitments balanced across the portfolio?
• Which programs are on track to deliver their combined goals?

For Executives

Two risk concepts exist in GreenVee and they operate at different levels. Project Risks (and their upside counterpart, Chances) are operational — specific things that might go wrong or better than planned on one project, managed by project managers. Portfolio Risk Factors are strategic evaluation criteria scored for each project and reviewed at the portfolio level. These two worlds do not connect directly. See Risks and Chances and Risk and Decisions for the full picture.

---

A note on permissions

Because GreenVee does not enforce these personas as system roles, your actual access depends on how your company administrator has configured permissions. If you cannot see a screen that this page says you should use, check with your admin — you may need to be added to the relevant project or granted a broader access level.