/members and /access-management routes) opens it on the Members view; /members?tab=groups opens the Teams view.

Teams and people on the Members view: the owner and two pending invitations, each with a role switch
Invite people
The workspace owner and admins see Invite member. Only admins see the Members view; everyone else sees their own teams.- In Teams and people, open Members and click Invite member (or use Invite to workspace in Quick actions).
- Enter one or more email addresses and click Send invite.
- It already has a Cognee account: the person is added straight away (“N existing members added”).
- It has no account yet: an invite email goes out and the person shows as Pending. They join automatically when they sign up with that exact address (“N invite emails sent — they join automatically when they sign up with that email”).
Roles and removal
The Role column shows Owner, Admin or Member. The owner is the person the Permissions page calls the Workspace admin. The owner switches others between Member and Admin. Owners and admins can Remove member; nobody removes the owner or themselves, and only the owner removes an admin. A removed member loses access to every team they are in, and their connected agents stop working. Agent service accounts (emails ending in@cognee.agent) are not listed.
Change the workspace owner
The owner is the account that created the workspace. There is no way to hand ownership to another account in the app. To let another account run the workspace, invite it and have the owner switch it to Admin: an admin invites and removes members. If the owner account itself has to change, ask support through the chat in the app.Switch workspaces
If you belong to more than one workspace, pick another one from the workspace switcher without signing out. The choice is remembered, so it sticks across page loads and every management call (members, billing) targets the active workspace. Your first Personal Workspace is free and cannot be deleted. Each additional workspace you own costs $5/month.When a teammate can’t reach your workspace or data
An invited teammate usually also has a Personal Workspace of their own. Most access problems come from working in that one instead of yours.They were invited but can't get in
They were invited but can't get in
Check their row under Members. Pending means they have not signed up yet: they join only when they sign up with the exact address you invited, so Resend invite if needed. Once they have joined, they pick your workspace from the workspace switcher.
They see 'trouble reaching your workspace' or 'pod unreachable'
They see 'trouble reaching your workspace' or 'pod unreachable'
The card reads We’re having trouble reaching your workspace (or {workspace} didn’t wake up). The app cannot reach the workspace right now, often because it is waking from sleep. Click Try again, or Sign out and back in. See Workspace lifecycle. If it keeps happening for one teammate while the workspace works for you, contact support through the chat in the app.
Their Claude connector or agent returns 404
Their Claude connector or agent returns 404
A connector works in the workspace the Cloud UI opens for them. With none selected, it picks the only workspace they own, which is their Personal Workspace. Have them switch to your workspace in the Cloud UI; a connected client can keep using the previous one for up to 5 minutes. See Which workspace.Dataset names match only datasets they own, so a request that names a shared dataset, or the connector’s own default dataset (
anthropic_claudeai_memory for Claude, claude_code_memory for Claude Code), returns 404 when they do not own it. A recall that names no dataset searches every dataset they can read, shared ones included. Over the API, pass dataset_ids instead of names; see Search & Recall.For teams, team admins and dataset access, see Permissions. For the endpoints behind this page, see Permissions & Access Control.