Capabilities
Define capabilities, add skill requirements (minimum level, mandatory vs nice-to-have), and capability search.
Capabilities are named bundles of skills (and optionally levels) that describe what's needed for a role, project, or goal. Admins define capabilities and their skill requirements so the platform can match people to opportunities and support learning.
What Capabilities Are
A capability is a reusable definition such as "Backend Developer", "Project Lead", or "Data Analysis". Each capability has:
- Name and optional description
- Skill requirements — Which skills are part of this capability and at what level (e.g. "React level 3", "SQL level 2")
Capabilities are used in:
- People Finder — Search by capability to find people who match (by current skill levels)
- Role profiles — Link role descriptions to required capabilities
- Roadmaps and trainings — Align learning to capabilities
- Recruitment or staffing — Match open roles or projects to people
Creating a Capability
- Go to Admin → Capabilities.
- Click Create capability (or Add capability).
- Enter name and optional description.
- Add skill requirements (see below). Save.
Skill Requirements
For each capability you add skill requirements: which skills and at what level.
| Field | Meaning |
|---|---|
| Skill | The skill from your tenant's skill catalog. |
| Minimum level | Required level (e.g. 1–5). People below this level don't fully match the capability. |
| Mandatory vs nice-to-have | Mandatory — Must have this skill at least at the minimum level. Nice-to-have — Prefer it but not required for a "match". |
Example: capability "Frontend Developer" might have:
- React — minimum level 3 — mandatory
- TypeScript — minimum level 2 — mandatory
- CSS — minimum level 2 — nice-to-have
Search and matching logic can use mandatory requirements first, then nice-to-have to rank or filter people.
Editing and Archiving
- Edit — Change name, description, or skill requirements. Updates apply to search and role profiles that reference this capability.
- Archive — Hide the capability from new use (e.g. role profiles, pickers) while keeping it for history and existing references.
Capability Search
Members and managers often search by capability (e.g. "Who has Backend Developer?") rather than by individual skills. The search uses:
- The capability's skill requirements (skills + minimum levels)
- Each person's assessed levels (and optionally verified skills)
Results are ranked by how well the person's skills match the capability (e.g. all mandatory skills at or above level, then nice-to-have).
Tip: Start with a small set of capabilities (e.g. 5–10) that map to your main roles or projects, then add more as you use People Finder and role profiles.