Competency

When adopting KCS, think of it like a driver's license. You begin with a learner's permit and gain more privileges as you gain more skills.

When a set of competencies are completed the learner advances to focus on new skills.

Entity

Machine name: knowledge_competency
Type: Content Entity
Canonical: user/{user}/competency

Competencies are boolean fields. Fields can be assigned to roles: admin/structure/knowledge/competency/settings

Field

The entity has a custom field. There is one row per role.

Values:

• role
  • The role machine-name
• correct
  • The correct items for this role
• total
  • Total items for the role
• proposer
  • The user who saved the competency, causing correct to equal total 
• proposed
  • The timestamp when correct equals the total. 
• approver
  • The user who approved the advancement.
• approved 
  • The timestamp when the advancement was approved.

Permissions

Create:

• Create new Competency
  • It may not be necessary; the controller automatically creates the entity if the learner does not have one.

Edit:

• Edit Other Competency
  • Like Edit Any, but excludes own Competency
• Edit Learner Competency
  • If they are the user's coach
• Edit Own Competency
  • Restricted: Competency can change a user's roles.

View:

• View Any Competency
• View Learner Competency
• View Follow Competency
• View own Competency

Delete:

• Administer Competency

Actions

When the competencies for a role are completed one of the following actions are taken:

• Do Nothing
  • Proposed and Approved are set to the current time
  • Proposer and Appover are NULL.
• Automatically advance the user to a new role
  • Proposed and Approved are set to the current time
  • Proposer and Appover are set to the current user.
• With leadership approval, advance the user to the new role
  • Proposed is set to the current time, and the proposer is set to the current time.
  • Approved and Appover are NULL until approved

The new role can either be the same as the competency, complete all the contributor items, and become a contributor or the next role. Complete all the contributor items and become a publisher.

Approval

Form: user/{user}/competency/approve

A form exists for the leader to approve the learner's promotion.

A views field exists for the user entity. If the user is pending leadership approval

Default Roles

There are three knowledge worker roles out of the box. Three is the most common number of roles. The number of roles can be increased or decreased. admin/structure/knowledge/competency/settings/role

Users are limited to one competency role. If a user is assigned multiple competency roles, all roles except the highest are removed during hook_user_presave.

The Coach, leader, and default roles are excluded from competency roles.

Candidate

The candidate is the first and lowest role.

• Edit Own Articles
  • Audience = Internal
• Link articles with Incidents/Cases
• Search Access
• Add Moderation Note
• Content Moderation
  • Work In Progress
  • Not Validated 

Contributor

The contributor is more advanced than the candidate role.

• Edit Any Articles
  • Audience = Internal
• Link articles with Incidents/Cases
• Search Access
• Add Moderation Note
• Content Moderation
  • Work In Progress
  • Not Validated 
  • Validated

Publisher

Publisher in the highest role. Publishers may change the audience to external.

• Edit Any Articles
  • Audience = Any
• Link articles with Incidents/Cases
• Search Access
• Add Moderation Note
• Content Moderation
  • Work In Progress
  • Not Validated 
  • Validated
  • Archived

References

[1] Technique 7.1: KCS Roles and the Licensing Model https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/...

[2] Appendix D: KCS Roles and Competencies https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide/080