Setting up Skillties

• Workspaces: definition, types, switchingExplanationA workspace is the shared space of an organisation or team: members, roles, groups, teams and private content. There are two kinds. A domain workspace belongs to an email domain, and anyone with a matching address joins automatically. A manual workspace is created by a person, and only people they invite get in.
• General: name, type, export, Danger ZoneReferenceGeneral holds the workspace's name, image and type, the data export and the Danger Zone for deleting or resetting. The join rule isn't here but under Users › Blocking Workspace Access. General is one of the two areas that can be edited on Free as well.
• The stages of a membershipIn progress
• Invite by emailGuideYou invite by email. The person becomes a member at once and receives an email with a sign-in link, or they are only prepared and receive nothing yet. Invitees become members, never admins. A workspace can send at most 20 invite emails in 24 hours, and every invitation is valid for 28 days.
• Import a list (CSV)GuideWith a CSV file you add many people at once. Only the email address is required. First name, last name, manager and employee ID come along optionally. People are prepared and get no email until you grant them access. There is no upper limit, and the invitation limit doesn't apply here.
• Add people from Entra IDIn progress
• Domain joining and the join ruleIn progress
• Grant accessIn progress
• The user listReferenceThe list under Users shows everyone in the workspace, grouped by stage from Active to Permanently deleted. Each row names source, date and badges; behind ⋯ sit the actions that fit the stage. Filter, sort and search are part of the address, so a filtered list can be shared as a link.
• Workspace memberships and blocking accessIn progress
• When the invitation doesn't arriveIn progress
• The role modelExplanationEveryone holds the Member role, admins also Workspace admin. You build further roles yourself or take the People development template, and give them directly or through groups. The rights of all of a person's roles add up. There are no denials, only permissions, and under Check you see for every person where each right comes from.
• How a right takes effect: plan, switch, rightExplanationA tick in the role editor is a permission, not a guarantee. Whether a person can actually do something is decided by three gates in order: the workspace's plan, the switch of the app in question, and only then the right. On top of that, some rights need something in the data, such as a reporting line or a team membership. This page explains the gates, the locks in the editor and how to find out why a right does nothing for someone. The individual rights follow on the eight pages after this one.
• Rights: people and reachReferenceThe People area in the role editor decides who opens the People app, whose skills and levels someone sees, and who uses and exports the Skills Hub. The sight rights form a matrix with two rows and three reaches; the widest level wins, and “Direct reports” and “Their area” only work with a reporting line under Organisation. The Hub additionally needs “Open People”, its switch and a contract.
• Rights: profile assignmentReferenceSix rights decide who assigns main, secondary and target profiles: three for one's own person, three for others. They sit in the role editor as a second matrix with the rows “Manage your own skills profiles” and “Manage other people's skills profiles” and the columns Main, Secondary, Target. Unlike the reaches, every cell is its own decision; a target profile does not include a main profile. A workspace that wants to manage one profile type centrally unticks exactly that one on Member and gives it to an HR role.
• Rights: skills and skills profilesReferenceThe Skills and Skills profiles areas decide who creates content, who changes other people's content, who sees the public library, who sorts content into the workspace's categories and who may be added as a moderator. Creating exists for private and public separately, overriding likewise. Private content needs a contract; overriding only affects content from this workspace; categorising needs the Skills Hub and at least one category.
• Rights: collaboration and teamsReferenceThree areas of the role editor depend on surfaces a workspace must switch on first. Collaboration governs comments on profiles. Teams governs who sees teams, leads their own teams and manages all teams. People in teams governs who sees the skills and levels of team colleagues, with the team as the reference instead of the reporting line. All team rights only work when the Teams app is switched on; it is off in new workspaces. A team never carries rights.
• Rights: administrationReferenceThe Administration area holds eleven rights, one per settings area. Whoever holds the right sees the area in the settings window and may change everything there; whoever does not, does not see the area. Three exceptions to “one area, one right”: General also opens the Teams settings and deleting the workspace, People also opens Organisation, and Skill Governance opens with the right for inheritance or the one for the Skills Hub. In a workspace without a contract only General and Users can be used, whatever rights a role carries.
• Rights: feedbackReferenceFour rights govern feedback: ask for feedback about yourself, give feedback without being asked, and the manager assessment for direct reports or the whole area. They do not sit in the role editor but are set through the path switches under Feedback, because they belong to the app. All four only work when feedback is switched on, the person takes part through the participating role and, for the manager assessment, a reporting line exists. What feedback asks about, levels or only presence, follows from the level rights of the participating role.
• Rights: codeterminationReferenceThree rights belong to codetermination: open the codetermination app, approve or reject requests, and read the log. All three only work when the contract includes codetermination and it is switched on under Codetermination. Requests are not decided by the right but by the seat on the body: whoever is entered under Codetermination as a member with decision power and has confirmed votes, and receives the Works council role automatically. Admins never have the decision right.
• Rights: own accountReferenceThree rights apply not in the workspace but to the person's account: create a new workspace, use the personal area, and accept invitations from other workspaces. They are evaluated in the workspace that owns the person's e-mail domain, the domain workspace. In a manual workspace the ticks are locked with “Only in a domain workspace” and do nothing. Anyone without a domain workspace, or not a member there, may always do all three.
• Groups as distributorsExplanationA group distributes roles. It carries roles and passes them on to all its members, nothing more. A group without a role is a plain list and gives no rights. Members come by hand or from Entra ID. Who may change a group depends on which rights it carries.
• Organisation: reporting line and fallbackGuideUnder Organisation you set who reports to whom. This decides what managers may see about their people, whom feedback releases apply to and who takes over direct reports when someone leaves. Assignments come by hand or from Entra ID; manual entries always come first. A fallback catches everyone who isn't assigned yet.
• Entra IDExplanationWith Entra ID, your Microsoft directory decides who is in the workspace. You choose Entra groups; Skillties reads their people regularly, adds them, fills in their details and takes them out again when Entra disables or deletes them. Skillties only reads and never changes anything in Entra.
• When a person is missing after the Entra syncIn progress
• Skill Governance: taxonomy and inheritanceIn progress
• App settings: PeopleIn progress
• App settings: TeamsIn progress
• App settings: FeedbackIn progress
• App settings: Skills HubIn progress
• App settings: CodeterminationIn progress
• App settings: Workflow LabIn progress