Skillties logoSkillties word mark
ExplanationWorks councilEnterprise

Codetermination

WhereSidebar › Works councilRightcodetermination.review

In shortRequests land in the body's app as soon as someone wants to extend a setting or a right that is subject to co-determination. The body reads the reason, asks questions in the conversation and approves or rejects; only with the required number of approvals does the change take effect. Deadlines remind but decide nothing. The body sees rules, roles and names, but no skills and levels.

What the body decides on

Co-determination exists only in Enterprise. An admin sets it up under App settings: Codetermination and defines there which rights, account permissions and rule sets need approval. The app carries the body's name, “Works council” at Nordwind, and shows at the top what it is about: The works council decides on the system — settings and rights in Skillties, not on individual people or one-off cases.

The principle is asymmetric. Extensions wait for approval: a right on a role, a role on a group, more visibility in feedback, a change to co-determination itself or a deletion rule set to request. Restrictions take effect at once: Anything that takes rights away. While a request is running, the affected setting is locked and carries the badge Change requested.

Who may open the app is governed by the rights under Rights: codetermination. Members of the body receive the “Works council” role automatically once their seat is confirmed; it brings codetermination.review and audit.read and cannot be assigned by hand.

The three tabs

The app has the tabs Requests, Members and Agreements. Under Requests sits the section Open with everything still running, and for members with audit.read the section Decided as the history. The number on the tab counts only what waits for you: your vote, your answer or a seat you can confirm. From ten open cases a search field appears.

Paul Weber sees under Requests the open request from Robert Lang: the right to see everyone's skills, for the role “Head of department”, with deadline.

Every row under Open shows the Case in two lines, Right and Role, below it Requested by … and whether someone has approved already. The Body column shows the faces of those who may vote; whoever has approved is highlighted. On the right are Requested on and the Deadline as a number with days left or days overdue. The list sorts first what waits for you, then overdue cases, then the shortest deadline.

Reading, asking, deciding

Clicking a row opens the Comments · Request rail on the right. It shows the requester's reason as a quote and below it the Conversation, a thread for body and requester: Recorded · body and requester. This is where the body asks questions before it decides; posts are tagged Body or Requester, and every post notifies the others.

The opened request: Robert Lang's reason, the conversation and the buttons Reject and Approve for Paul Weber.

In the row, those who may decide see the buttons Reject and Approve. If your vote completes the required number, the button reads Approve — your vote decides; afterwards it says Your vote is in. There is no field for a rejection reason; the conversation is the place for it. What applies then:

DecisionEffect
Approvecounts as one vote; with the required number the change is applied, the request appears under Approved
Rejectone vote is enough; nothing is applied, the request appears under Rejected
Withdrawrequester only; the request appears under Withdrawn, the body is notified

How many votes are needed is shown under Agreements as Votes needed, one by default. Only confirmed members with Can decide may vote; the person a request is about and the requester don't vote. If nobody would be left, the requester may vote after all. If an approval would leave the body without anyone able to decide, it is not applied: Not applied: the body would have been left without anyone able to approve.

Deadlines remind, decide nothing

Every request gets a deadline from the settings, 14 days by default. Three days before, the app reminds every member whose vote is missing, in the bell and by email. When the deadline passes, the request stays open: it neither expires nor counts as approved. The row shows days overdue, the Open section carries the badge … overdue, and the requester gets the notification The deadline passed — no decision was made. With No deadline nothing reminds.

Log and notifications

The Decided section is the log: per case the requester, approved by …, the date under On and the Outcome. A click opens reason and conversation read-only. Deletion rules set to log run at once and appear here like approved requests. There is no export.

EventWho gets the notificationMail
new requesteveryone who can decide, except the requesteryes
partial approvalmembers whose vote is still missingno
decisionrequester and the members involvedyes
post in the conversationmembers and requester, except the authoryes
reminder three days before the deadlinemembers whose vote is missingyes
deadline passedrequesterno

The mail names only the workspace and the sign-in link, never the content, and arrives at most once an hour.

Members and seats

Under Members are the groups Confirm seat and In the body, each person with the Access Can decide or Read only. Anyone who only reads sees requests and can comment but doesn't decide. Whoever switches co-determination on is the first member. Someone with settings.codetermination proposes others via Propose member; the proposal appears under Requests as … for the body with Confirm or decline. A confirmed member confirms the seat with Confirm, or the proposed person declines with Decline proposal. Removing a member or setting them to Read only is itself a request; the last member able to decide cannot be removed.

The Agreements tab at Nordwind: votes needed, time to reply, members and the rights that need approval.

What the body sees and what it doesn't

The Agreements tab shows Nordwind's agreement: Votes needed, Time to reply, Members with the number of those who can decide, the Settings under co-determination, the Rights that need approval and under Who may do what the roles and rights of colleagues, By role or By person. It lists names, roles and rights, but no skills and no levels. Nowhere inside the app are there skills or levels.

Outside the app, the “Member” role applies to body members as well; the “Works council” role takes nothing away. What a body member sees in People therefore follows the rights of the “Member” role, not the membership of the body. More under Who sees what.

Example

Robert Lang wants the role “Head of department” at Nordwind to see the skills of all employees, because shifts are planned across plants. He ticks directory.skillsAll, and because the right needs approval, this becomes a request with his reason. Paul Weber and Sarah Winter get the notification is asking you to decide. Paul opens the request, reads the reason and asks in the Conversation whether the view of levels is included. Robert replies in the thread that only the skills are meant. Paul chooses Approve; since one vote is needed, the change applies at once, the request moves under Decided, and Robert gets the notification approved your request.

Checked with version 0.8.0 · 3 Nov 2026