Skip to main content

Overview

Every piece of content belongs to a workspace, and every workspace belongs to an organisation. The organisation’s kind decides who controls the data: One users row can hold both: memberships of any number of team organisations, and one Personal organisation with any number of private workspaces (bundles). See User lifecycle for the sequence diagrams.

Identity model

Workspace lists show only workspaces whose organisation_id is the current organisation.

Getting a Personal organisation

Inviting an account that already exists only adds the team membership. Nobody can be added to someone else’s Personal organisation, and its workspaces can’t be shared.

What belongs where

Content never changes organisation on its own. session.workspace_id is fixed when a session starts, and switching organisation moves nothing. Moving a session from Personal into a team workspace is an explicit step (#208), not built yet.

Erasure

Every request is made with POST /me/data-requests { organisation_id } and is stored with scope = 'organisation', the Personal organisation included. See Data subject requests for what each step erases. Personal doesn’t count as a membership here. Account-level records (credentials, devices, the pseudonymised users row) and the Personal membership go with the request that leaves the person in no team, so someone in one team deletes everything with one request. A person in no team asks in their Personal organisation. While a request is pending the whole account is frozen (users.frozen_at): OAuth tokens are revoked, API keys deactivated and calendar auto-join paused. Rejecting or cancelling lifts the freeze and restores the keys and auto-join; the person signs in again.

Controller and processor

The privacy policy and trust page must:
  • distinguish the two processing bases;
  • for team data, describe Kair’s obligations as processor under the organisation’s DPA;
  • for Personal data, state Kair’s lawful basis (contract performance / legitimate interest), retention periods and the right to erasure;
  • list Kair as processor for team accounts and as controller for Personal.

Not built yet

  • Moving sessions out of Personal into a team workspace, with the reminder of who will gain access (#208).
  • Notifying platform admins of a request in a Personal organisation: new-request emails go to the organisation’s admins, and a Personal organisation has none.
  • A freeze scoped to one membership. user_organisations.frozen_for_request_id exists, but a pending request freezes the whole account, so the person can’t keep using Personal or other organisations meanwhile.
  • Requests with scope = 'personal': the enum value exists; the worker refuses it, and Personal data goes through a request in the Personal organisation instead.