Rights: skills and skills profiles

Private and public

A skill or skills profile is either public for the whole platform or private within one workspace. Public content is visible to every Skillties user; private content is seen only by the workspace it lives in. The rights in both areas follow this split: each exists once for private and once for public.

Create private skills and skills profiles

content.createSkillPrivate, content.createProfilePrivate. The person creates content visible only in this workspace: via Create at the top, via a copy of an existing profile, or via the import in the Skills Hub. A copy is a new profile and needs this right. So does a daughter profile in inheritance.

• Without the right. The “private” choice is missing from the dialog. If only one choice remains, the visibility step disappears entirely.
• Only works if. The workspace has a contract. Without a contract there is no private content, and the right is a tick without a surface. A workspace must also be active; in the personal area there is nothing private.
• Default. Member, People development, Admin.
• Codetermination. Not recommended.

Create public skills and skills profiles

content.createSkillPublic, content.createProfilePublic. The person creates content for the whole platform. Whoever may do this also helps maintain the public content the workspace itself owns.

• Without the right. The “public” choice is missing from the dialog.
• Only works if. The person holds the right in every one of their workspaces. Public content belongs to nobody alone, so one workspace allowing it is not enough if another forbids it. Anyone in no workspace may always do it.
• Default. Member, People development, Admin. A workspace that does not want its workforce publishing publicly unticks it on Member.
• Codetermination. Not recommended.

Override private content in the workspace

content.overrideSkillPrivate, content.overrideProfilePrivate. The person edits private skills and profiles of this workspace even when they are neither owner nor moderator: title, description, and for profiles skills, target levels and comment settings. Plus changing the owner and merging content in the Skills Hub. Changes appear in the activity feed under the acting person's name.

• Without the right. Only owners and moderators may edit. The pen is missing; a direct call is refused.
• Only works if. The content lives in this workspace and the workspace has a contract.
• Default. Admin only. People development does not have it.
• Codetermination. Recommended.

Override public content from the workspace

content.overrideSkillPublic, content.overrideProfilePublic. The same for public content that was created from this workspace. Owners and moderators are notified of a change.

• Without the right. Only owners and moderators edit. In the Hub such content reads “Public — read-only”.
• Only works if. The content originates from this workspace. Public content of other workspaces or of people without a workspace stays untouched, whoever holds the right.
• Default. Admin only.
• Codetermination. Recommended.

See public skills and skills profiles in the library

library.skills, library.profiles. The person sees the platform's public content in the Library. Two rights, because a workspace may keep out other people's role descriptions and still use the skills.

• Without the right. The library stays reachable and shows this workspace's content; only the public list is empty, and the type filter is missing. There is no error message.
• Only works if. The person holds the right in every one of their workspaces, as with public creation. Outside every workspace it is always allowed.
• Default. Member and Admin. The People development template does not need it, because Member carries it.
• Codetermination. Not recommended.

Categorise skills & profiles

content.classify. The person sorts skills and profiles into the workspace's categories, such as competence field or job family. That happens in the Skills Hub in the category columns. The assignment belongs to the workspace; public content is not changed by it.

• Without the right. The category columns in the Hub are read-only; the pen is missing.
• Only works if. The person may use the Skills Hub and at least one category exists. Creating categories is a different right: Settings: Skills Hub. Without categories, categorising is a tick without a surface.
• Default. People development and Admin, not Member.
• Codetermination. Not recommended.

Be added as a moderator

content.coOwn. The owner of a skill or profile invites the person as a moderator. Moderators help edit but invite nobody and delete nothing. You maintain your own content without a right.

• Without the right. The person cannot be invited. In the owner's people picker they appear as not allowed; an existing invitation is checked again on acceptance.
• Special. The invited person is checked, not the owner. An owner needs no right to invite; the invitee needs this right in the workspace the content comes from.
• Default. Member, People development, Admin.
• Codetermination. Not recommended.

Overview

Example

Nordwind wants new skills to arise only inside the workspace and nobody in the workforce to create public content. Robert unticks “Create public skills” and “Create public skills profiles” on Member. Sarah Winter creates the skill “SAP S/4HANA materials management” and sees no choice in the dialog any more; it is private automatically. When Sarah later wants to extend the description of the private profile “Production shift lead”, she cannot: the owner is Max. Max invites her as a moderator, which works because Sarah as a member holds “Be added as a moderator”. Julia from People development sorts both items into the competence field “Production” in the Skills Hub; she can, because she may use the Hub and Robert created the category under Skills Hub. Julia still may not change the profile, since at Nordwind only Robert holds overriding.