PrivateMind
Get API key

Users & teams

Manage members, change roles, and group people into teams.

As an Org admin you control who is in your organisation and how they are grouped. The two surfaces live side by side in the settings sidebar:

  • Members at /settings/org/users: every user attached to your org, their role, and basic profile.
  • Teams at /settings/org/teams: named groups of members with their own roles, shared sources, and shared conversations.

How users get into the org

Org admins do not invite users directly. There is no "send invite" button on the Members page. New users land in your org through one of two paths:

  • SSO / identity provider: when a user signs in with an email that matches an allowed domain on your subscription, they are provisioned automatically.
  • Platform admin: support can attach an existing user to your org.

Managing members

The Members page shows three counters at the top (total users, admins, and subscribers) and a searchable list below. Selecting a member opens a detail panel on the right with:

  • Name and email
  • Current role (with a coloured badge)
  • Subscriber and subscriber-admin flags
  • Join date

Edit details

The Edit Details action lets you update first and last name. Email and other identity fields are owned by the identity provider and cannot be edited here.

Change role

The Change Role action assigns one of:

Role What they can do
user Chat, manage their own sources and projects, mint personal API keys
org_admin Everything a user can do, plus everything documented in this section

Higher roles exist but are platform-wide and cannot be granted by an org admin. The role dropdown filters them out.

You can only modify users below your own role. The detail panel surfaces a lock icon and an explanatory note when you cannot. For example, another org_admin cannot be demoted by a peer.

Teams

A team is a named bucket of members inside your org. Teams have their own roles, their own shared sources, and their own shared conversations. They are for access and collaboration only. Teams don't affect billing or rate limits.

Creating a team

From the Teams page, Create Team opens a dialog asking for a name and an optional description. The team gets an auto-assigned colour for its avatar; you can pick anyone to add later.

Creating a team requires the org_admin role. Regular users can be team owners or admins for teams they belong to, but they cannot stand up a new team from scratch.

Team roles

Team role What they can do
owner Full control: transfer ownership, delete the team
admin Manage members, roles, sources, and budgets
moderator Manage shared content and conversations
member Use team sources and participate in chats
viewer Read-only access to team resources

Team roles are separate from org roles. A user can be an org_admin on the org and a plain viewer inside a specific team, or a user on the org and owner of their team.

Adding members

Inside a team's detail view, search any user in the org by name or email. Picking a result adds them at the member level. Bump them up afterwards using the per-row role dropdown.

You can only assign roles below your own team role. Owners can promote to admin; admins can promote up to moderator; and so on. Platform admins bypass this rule.

Transferring ownership

A team has exactly one owner. To hand it off, the current owner picks Transfer Ownership in the members tab, selects a member, and confirms. The previous owner is demoted to admin.

Deleting a team

From the team card menu, Deactivate removes the team from active use. Members lose access to the team's shared sources and conversations immediately.

What members see vs. what admins see

When you are looking at the Members page, you see every user in the org regardless of team membership. When a regular user lands at /settings/org/teams they see only the teams they belong to. The page works for them as a viewer, but creating new teams is gated to org admins.

Where next