Skip to main content
Cognee Cloud keeps one answer to “who can reach this memory?” for every dataset, and shows it on the Permissions page. This guide explains the model behind that page. For the endpoints, see Permissions & Access Control.

Who is who

  • Workspace: your organisation. Everyone you invite is a member of it, and every member is in its Organisation team, which nobody can leave or delete.
  • Teams: groups of people that hold datasets together, such as Sales or Engineering. A person can be in several teams.
  • Workspace admin: the person who created the workspace. Only they create and delete teams and name organisation admins.
  • Organisation admins: act on the whole workspace like the workspace admin, apart from teams and admins.
  • Team admins (team leads): add and remove people in the teams they lead, and decide who else gets the datasets their team owns.
  • Members: everyone else. They see their own access and the teams they are in.
  • Agents: members owned by a human. An agent’s access is capped by its owner’s, only its owner changes what it reaches, and it administers nothing. See Agents.
Nobody gives themselves access, adds themselves to a team or makes themselves a team admin. A workspace admin who creates a team is its first member and admin; that is the one exception.

Datasets: owners and owning teams

Every dataset keeps the person who created it as its owner, connector imports included. A dataset an agent creates belongs to the agent’s owner.
  • A dataset is personal while only its owner and the owner’s agents can read it, and shared once anyone else can.
  • A shared dataset can have one owning team: the matrix column it sits in and the Owner shown in a team’s datasets. A dataset gets one only by an explicit action: creating it inside a team, its creator assigning it to a team, or its creator picking one of their own teams. Joining a team shares nothing.
  • Everyone in the owning team can read the dataset, and that read cannot be taken away while the team owns it. The team’s admins decide who else gets it.
Teams hold datasets at one of three levels, the same for every member of the team:

How access is decided

A person reaches a dataset by one or more paths: as its owner, given directly, through a team, or through the whole workspace. Because paths add up, removing one may leave another. Every change on the Permissions page is previewed first: it shows who reaches the data now and after, and who still reaches it another way. Nothing changes until you confirm, and a change made in the matrix offers Undo. Admins can type the change as one sentence in Manage access (“Remove Marketing’s access to Accounting”). Cognee reads it, resolves the names and shows the same preview. Reading a sentence uses workspace credits. Data keeps its origin. Permissions always trace back to the source dataset and its owning team, and anything promoted from another team says where it came from.

Flags and requests

Cognee flags pairs of teams whose access looks wrong, for example Sales reaching board papers. Unusual, have a look is amber; Likely shouldn’t happen is red. A pair Cognee has not checked is marked as such, because no flag does not mean safe. Members ask for data they cannot read in their own words, from a cell of the team matrix, and a workspace admin decides. A waiting request shows under Your requests, where its sender can withdraw it.
Answering requests on the Permissions page, and the members’ Check your access field, are rolling out. Until then, admins answer requests directly.

Memory promotion

Memory moves up in steps: agent → person → team → organisation. What an agent learns in a session is distilled into its owner’s long-term memory (see Session distillation). From there, useful pieces can be promoted to a team and to the organisation. Promoted pieces do not go into the source dataset’s audience. Each team can have one Promoted Memory dataset, owned by that team, that everyone in the team reads. The organisation has its own memory that everyone in the workspace reads. Each promoted piece records the team it came from (Promoted from …), so its origin stays visible. Promotion is never silent. It happens on demand, after someone decides:
  1. A member asks a question that their own memory cannot answer, but another team’s data can.
  2. The source team’s admins and the organisation admins see it under Needs attention at the top of the Permissions page: the question, who asked and how often, and what kind of evidence answers it (never the passages themselves). The person who asked is told nothing while it waits.
  3. Promote to …: Cognee answers the question from the source dataset only, masks recognised personal data and credentials, and adds the answer as one document to the asking team’s Promoted Memory. The team finds it on their next search. This uses workspace credits.
  4. Keep in …: nothing is shared, and the same question from the same person is not asked again.
Sharing strength sets how much new memory moves up automatically versus being asked first, from Restricted (always asked) to Open. See Sharing strength on the Permissions page.

Permissions page

The matrix, requests, sharing and Teams and people, section by section.

Permissions API

Grant dataset access and scope agents from code.