Rights: collaboration and teams

Collaboration: join discussions

collab.commentPrivate, collab.commentPublic. Every skills profile has a discussion. The owner may always write there. Everyone else needs the right for the kind of profile: private or public.

• Without the right. The person reads the discussion but cannot write. A direct attempt is refused.
• Only works if. The owner has allowed comments on the profile at all. For a private profile the person must be a member of the workspace it lives in. For a public profile the right applies when it is allowed in every workspace of the person.
• Default. Member, People development, Admin, both rights.
• Codetermination. Comments on private profiles recommended, because they are statements about colleagues' work. Comments on public profiles not.

Teams: the app and its management

Before any of these rights does anything, the app must be on: Workspace settings › Teams, switch at the top. That area is opened by whoever holds Open settings · General. If the app is off, the menu entry is missing for everyone; whoever knows the address reads “Teams are switched off”. The menu entry appears as soon as the app is on and the person either holds “See teams” or “Manage all teams”, is in a team, or may create teams.

See teams

teams.view. Opens the overview of all teams and their profiles: name, purpose, members, history. Shows no skills; those come from the sight rights.

• Without the right. The person sees only the teams they are in themselves. Other teams do not exist for them, not even via search.
• Only works if. The app is on. For teams with visibility “Members only”, the person sees the team but not its members; only members and people with “Manage all teams” see those.
• Default. Member, People development, Admin.
• Codetermination. Not recommended.

Manage own teams

teams.manageOwn. Applies only to teams where the person is lead or co-lead: add and remove people, appoint leads, maintain the target, change settings, close the team. It shows nothing additional.

• Without the right. A lead sees their team but cannot change it. A direct attempt says one of the two management rights is needed.
• Only works if. The person has a running role as lead or co-lead in that very team. You become lead by creating a team or by appointment from someone who may manage the team. The right alone makes nobody a lead.
• Default. Admin only. People development has “Manage all teams” instead. A workspace where leads are to run their teams themselves gives this right to a management role or to Member.
• Codetermination. Recommended.

Manage all teams

teams.manage. The same for every team in the workspace, plus creating teams and deleting mistaken entries. Only this right allows creating a team; “Manage own teams” is not enough. Deleting exists only for mistaken entries, since a team is otherwise never deleted but set dormant.

• Without the right. The New team button is missing. Other people's teams are read-only.
• Only works if. The app is on. Which team kinds may be created, line or project, is set in the Teams settings.
• Default. People development and Admin.
• Codetermination. Recommended.

People in teams: sight with the team as reference

These four rights show skills and levels of people through team membership instead of the reporting line. They only work in the Teams app: in the team profile, in the team evaluation and in check-ins from the team. In the People app and in the Skills Hub only the reaches from the People area count. Conversely, in the Teams app only the Everyone level of the reaches counts: whoever wants to see the skills of people outside their team there needs “See the skills of everyone in the workspace”.

See skills and mapping of people in teams they lead

directory.skillsTeamLed, directory.levelsTeamLed. For teams where the person is lead or co-lead, the app shows the members' skill names and, with the second right, the levels and the team median too.

• Without the right. The team profile lists the members without skills; the median stays empty.
• Only works if. The person actually leads the team. For teams where they are only a member, the following two rights apply.
• Default. People development and Admin. Not Member.
• Codetermination. Recommended.

See skills and mapping of people in their own teams

directory.skillsTeamMember, directory.levelsTeamMember. Every team member sees who in the team has which skill. That answers “who do I ask?”. The second right also exposes the levels and with them a ranking among colleagues.

• Without the right. Members see who is in the team, but no skills.
• Only works if. The person has a running membership in the team. As long as Member carries “See the skills of everyone in the workspace”, this right changes nothing, because the wide reach shows everything anyway. It only takes effect once a workspace withdraws the wide reach; then the sight within one's own team remains.
• Default. Skills in own teams: Member, People development, Admin. Mapping in own teams: only People development and Admin. Member deliberately does not have it; a workspace that wants to work that way ticks it on purpose.
• Codetermination. Both recommended.

Overview

Example

Nordwind switches on the Teams app. Tom Brooks leads the Early shift Bremen and holds “Manage own teams” through Head of department: he adds Paul and Sarah and maintains the target. Sarah leads the SAP S/4HANA rollout with Max as co-lead. Sarah is only a member and does not hold “Manage own teams”, so she cannot staff her own project team although she is its lead. Max as co-lead can, because he holds the Head of department role. Robert then gives Member the right “Manage own teams” so that every lead can run their team; creating teams remains with Julia, Anna and Robert through “Manage all teams”. In the Early shift profile Paul sees that Sarah knows SAP, but not at which level, because Member does not carry “See mapping of people in their own teams”.