Skills

Caution

GreenVee uses the word “skill” in two unrelated places. HR Skills (this page) are qualifications attached to Employees and Project Members — they are master data in the People section. Agent Skills are configuration blocks that define what an automation agent can do, and live entirely in the Automation & AI section. The two have no connection.

What is a Skill?

A Skill is a named capability or qualification that an employee can hold and a project role can require. Skills are master data — defined once, reused across all projects.

Examples: “PV system design”, “Welding (MIG)”, “Project management”, “Electrical inspection”.

Fields

Field	What it means
Name	Short label used in lists and filters (e.g. “Roof mounting”)
Description	More detail about what the skill covers
Certification required	Flag — yes or no. Marks whether holding this skill demands a formal certificate
Certification name	If certification is required, the name of that certificate (e.g. “BS7671 18th Edition”)

The certification flag is important for safety-critical or regulated work: it tells planners that assigning someone to a role requiring this skill is not enough — they must hold the named certificate too.

---

Skill Categories

A Skill Category (stored as osp_skill_category) is a hierarchical grouping that organises skills into a browsable tree.

Like Departments, categories are recursive — a category can have child categories:

Technical Skills
  ├── Electrical
  │     ├── PV Design
  │     └── Grid Connection
  └── Structural
        ├── Roof Assessment
        └── Load Calculations
Soft Skills
  └── Project Management

Categories are for navigation and filtering. They do not affect how skills are matched to people or roles.

---

Skills on Employees

Employees and Skills have a many-to-many relationship:

• One employee can have many skills.
• One skill can be held by many employees.

When you view an employee record’s Skills tab, their skill list shows everything they are qualified to do — this is their real, personal capability list. Add or remove skills from this tab; each skill shows how many other employees also hold it, plus its certification details.

---

Skills on Project Members

A Project Member — the record for a role/slot on a project — also carries a list of skills, but these mean something different from an employee’s own skills: they are the skills the role requires, whether or not the role has been filled yet.

Level	What the skill list means	Where it’s set
Employee	Skills this person actually has	Employee’s Skills tab
Project Member	Skills this role/slot on the project requires	The role’s Skills tab in the project structure view

A project member row can exist unfilled (no employee assigned yet) — in that state its skill list is purely a requirement checklist for the role. Once an employee is assigned, the role’s required skills stay the same; they don’t turn into “what the person actually has” — that’s still tracked separately, on the Employee.

Matching required skills to a candidate

In the org structure view (/structure), an unfilled role shows a Resource Matching action: pick a candidate employee and GreenVee shows what percentage of the role’s required skills that employee’s own skill list covers, skill by skill, before you assign them.

For Team Leads

Use the skills catalogue when planning who can take which role. Set required skills on a project member role first, then use resource matching to find the best-covered candidate before assigning them.

---

Summary

Skill Category (hierarchical)
  └── Skill
        ├── held by → Employee (many-to-many, "what they have")
        └── required by → Project Member (many-to-many, "what the role needs")

Skills are master data — defined independently of any project. They attach to employees as actual capabilities (see Employees & Departments) and to Project Member roles as requirements (see Project Members vs Employees).