Deadlines at a glance
How the deadlines fit together
Skillties has two kinds of deadlines. One kind protects against the final step: nothing that destroys data or takes away access happens at once; there is always a date up to which the decision can be taken back. The other kind keeps things moving: a request nobody answers should not stay open forever but expire or be chased up. The tables below are sorted by these two kinds. Where a deadline can be set, the default and the place to change it are given; where it is fixed, its origin is named.
Deadlines before the final step
| Deadline | Length | What applies until then | Origin |
|---|---|---|---|
| Retention after deleting a member | 6 months by default, settable from 0 to 24 months | The history stays, an admin can Restore; after that, ratings and received feedback are deleted and the name becomes “Former member” | The workspace's deletion rules, section Retention |
| Grace period of a self-requested account deletion | 14 days | All memberships rest; at sign-in only the lock page with Keep account appears | fixed, account deletion |
| Handing content over to a person | 14 days | The person asked can accept; otherwise the content becomes ownerless | fixed, handover |
| Priority for content without an owner | 14 days | Only those who used or moderated the content on the cut-off date may take it over; after that, anyone | fixed, content without an owner |
| Deleting or resetting a workspace | 14 days | Everything keeps running; any admin with settings.general can Cancel | fixed, Danger Zone |
| Disabling a member | none | Disabled stays disabled until an admin enables or deletes | deletion concept: a pause has no deadline |
Retention is the only one of these deadlines a workspace sets itself. Shortening takes effect at once, also for members already deleted, whose date then moves forward. Extending moves the date as well but can require a codetermination request in Enterprise. Zero months means: deleting a member becomes final with the next nightly run. The rules are described in Deletion rules and retention.
The 14 days are deliberately the same everywhere. Anyone who deletes their account triggers handovers in every workspace, and the successors have exactly as long to accept as the grace period lasts; on day 14 accepted successions are carried out and the rest becomes ownerless, with the priority that also runs for 14 days. The chain is described in Delete your account and Content without an owner.
Deadlines of the Entra sync
| Deadline | Length | What happens | Origin |
|---|---|---|---|
| Account disabled in Entra | at once on the next run | Membership disabled, nothing deleted | fixed, Entra decides |
| Person vanished from the source groups | disabled at once, deleted after 30 days | Then departure with handover under the deletion rules and start of retention | fixed, the same period as Entra's recycle bin |
| Account permanently deleted in Entra | at once | The Skillties account is deleted, without grace period and without email | fixed |
| Interval between runs | 6 hours by default, choice of 1, 6 or 24 hours | At most that long until Skillties notices a change in Entra | Entra ID, Sync tab |
What the three states mean and when the emergency brake stops a run is explained in When Entra ID disables or deletes someone. The 30 days count from the first run that misses the person; if they return before that, the count starts over.
Deadlines that keep things moving
| Deadline | Length | What happens | Origin |
|---|---|---|---|
| Invitation to a workspace | 28 days | After that the invitation counts as expired; a new one can be sent | fixed, invitations |
| Inviting again after a decline | once at once, then a 30-day pause | Anyone who has declined twice gets no new invitation for 30 days | fixed, invitations |
| Duration of a feedback request | 14 days by default, choice of 7, 14 or 30 days | Three days before the end Skillties reminds those who have not answered; then the round closes | the feedback request when it is created |
| Codetermination request | 14 days by default, settable per workspace | Three days before, Skillties reminds those whose vote is missing; after expiry the requesting side is informed, the request stays open | codetermination settings |
| Approved workspace export | 7 days | That long the approved export can be downloaded | fixed, codetermination |
| Read notifications | 90 days | That long they stay in the list under “For you” | fixed |
An expired codetermination request does not change its state: it counts neither as approved nor as rejected but keeps waiting, only with the note that the deadline has passed. That is intended, so that an approval requirement can neither be bypassed by doing nothing nor brought to a standstill by a forgotten inbox. More under Codetermination.
What has no deadline
Some things that sound like a deadline are none. A switch to Free applies at once, without notice and without asking, as When a contract ends: switching to Free describes. Deleting a member by an admin never waits for a request, not even in Enterprise; codetermination knows only disabling and permanently deleting as entries. And deleting a skill or profile nobody uses is final at once: there is no recycle bin for it.
Checked with version 0.8.0 · 3 Nov 2026
