Role Profiles

Create role descriptions as knowledge documents, link competencies and responsibilities, and support career paths.

Role profiles are knowledge documents that describe a role in your organization: typical responsibilities, competencies, and how it fits into career paths. Admins create and maintain them so members and managers can discover roles and plan growth.

What Role Profiles Are

A role profile is a document (often rich text or structured content) that includes:

  • Role name and short description (e.g. "Senior Backend Developer", "Project Lead")
  • Responsibilities — What the role typically does
  • Competencies / capabilities — Linked capabilities or skills expected for the role
  • Career path — Optional links to "next" roles (e.g. Backend Developer → Senior Backend Developer) or related roles

Role profiles live in the knowledge base and are used for:

  • Career development — Members see what skills and experience a role requires
  • Learning alignment — Roadmaps and trainings can reference role profiles
  • People Finder — Search and matching can use capability/role context
  • Recruitment and staffing — Clarify expectations for a role

Creating a Role Profile

  1. Go to Admin → Role Profiles (or Knowledge → Role Profiles).
  2. Click Create role profile (or Add role).
  3. Enter name and description (and any required fields).
  4. Add responsibilities — Bullet list or structured sections describing what the role does.
  5. Link competencies — Attach one or more capabilities (or skills) that define what's needed for this role. These link to your capability definitions and skill catalog.
  6. Optional: career path — Link to other role profiles (e.g. "Next step: Senior Developer") or add free text.
  7. Save and publish if your tenant uses draft/published states.

Tip: Reuse the same capabilities you use in People Finder and in trainings so role profiles stay consistent with the rest of the platform.

Linking Competencies and Responsibilities

  • Competencies — Use the Capabilities you defined in Admin → Capabilities. Attaching "Backend Developer" to a role profile means that capability's skill requirements describe what the role needs.
  • Responsibilities — Describe the role in plain language. You can reference skills or capabilities by name so members understand both "what I do" and "what I need to know."

Together, competencies and responsibilities give a clear picture of the role for career conversations and learning plans.

Career Paths

Where supported, you can define career paths by linking role profiles:

  • Next role — e.g. "Junior Developer → Mid Developer → Senior Developer"
  • Related roles — e.g. "Backend Developer" and "DevOps Engineer" as alternatives or lateral moves

This helps members and managers see progression options and align learning to the next role.

Editing and Publishing

  • Edit — Update name, description, responsibilities, or linked capabilities. Changes apply to the knowledge base and any place that displays the role profile.
  • Publish / archive — If your tenant supports it, role profiles can be draft or published. Published profiles are visible in the knowledge base; archived ones are hidden from discovery but may be kept for reference.