# Users & teams Manage members, change roles, and group people into teams. As an **Org admin** you can see everyone in your organisation, change what each person is allowed to do, and group people into teams. You do this on two settings pages: - **Members** at `/settings/org/users`: every user in your org, with 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 **don't invite users directly**: the Members page has no invite button. New users join your org in one of two ways: - **SSO / identity provider**: a user who signs in with an email on one of your subscription's allowed domains is added automatically. - **Platform admin**: support can attach an existing user to your org. A member who signs in by email link or with a personal mail provider adds a passkey the first time they sign in, and uses it from then on. Company SSO sign-ins are unaffected. PrivateMind sets this for your organisation. > [!NOTE] > If a colleague can't reach the app after signing in, they aren't attached to your org yet. Retrying the sign-in gives the same result, so contact support. ### Account not associated with an organisation If a user's email domain is not an allowed domain on any subscription, PrivateMind **rejects them at sign-in**, even though their SSO sign-in worked. They see *"Your account is not associated with a PrivateMind organization. Please contact your administrator."* PrivateMind has no organisation to put them in, so it stops there. This happens when: - the user signs in from a domain that was never added to your subscription's allowed domains, or - the user is brand new and self-registration from their domain is not set up. **The fix is a change to your subscription's allowed domains.** No settings page has a field for it, so neither you nor the user can make it (see [the SSO note in Org settings](https://docs.privatemind.com/org-settings.html#what-is-not-on-this-page)). If the domain should be allowed, send it to your PrivateMind account team. Once it is mapped, the user's next sign-in adds them as normal. ## Managing members The Members page shows how many users and admins your org has, and a searchable list of members. Select a member to see their name, email, role and join date. ### Edit details **Edit Details** changes a member's first and last name. Email and other identity fields come from the identity provider and can't be edited here. ### Change role **Change Role** assigns one of these roles: | 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 they are platform-wide, so an org admin can't grant them and the dropdown leaves them out. You can only change users **below your own role**, so one `org_admin` can't demote another. When you can't change someone, the detail panel shows a lock icon and says why. > [!WARNING] > Promoting a user to `org_admin` gives them everything described in this section: they can flip feature toggles, read audit logs and manage teams for every member. Treat it like handing over a shared admin password. ## Teams A team is a named group of members inside your org, with its own roles, shared sources and shared conversations. Teams control access and collaboration only. They don't affect billing or rate limits. ### Creating a team On the Teams page, click **Create Team** and enter a name and an optional description. You add members afterwards. Only an `org_admin` can create a team. Regular users can be owners or admins of teams they belong to, but they can't create one. ### Team roles | Team role | What they can do | | ----------- | ------------------------------------------------------------------------------- | | `owner` | Full control: transfer ownership, delete the team | | `admin` | Manage members, roles and sources | | `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` in the org and a `viewer` in one team, or a `user` in the org and the `owner` of a team. ### Adding members In a team's detail view, search for anyone in the org by name or email. The person joins as a `member`, and you can raise their role with the dropdown on their row. You can only assign roles **below your own** team role: owners up to `admin`, admins up to `moderator`, and so on. Platform admins are exempt from this rule. ### Transferring ownership A team has exactly one owner. To hand it over, the current owner picks **Transfer Ownership** in the members tab, selects a member and confirms. The previous owner becomes an `admin`. > [!WARNING] > The previous owner can't undo a transfer. Check you have the right person before you confirm. ### Team secrets A secret is a credential, such as a password or an API token, stored in PrivateMind and attached by name to workspaces and jobs. When your organisation has [Secrets](https://docs.privatemind.com/secrets.html) on, each team's page has a **Secrets** tab: - The team's members see the team's secrets and can attach them to their own workspaces and jobs. - An org admin who is in the team can also attach them to another team member's workspace. - The team's owners and admins, and org admins, add, replace and delete them. - A workspace can hold a team secret only if everyone who can open it is in the team or is an org admin. When you remove someone from a team: - The team's secrets are detached from their own workspaces, unless they're an org admin. - On colleagues' workspaces that hold those secrets, any share that names them is removed. If they can still open such a workspace another way, the secrets are detached from it instead. ### Deleting a team **Delete** in the team card menu removes the team, its member list and everything shared with the team: source grants, source shares, chat invitations made through the team, and the team's secrets. Members keep what they own and anything shared with them another way. You can't undo a deletion. You can't delete a team that guards a connector, which means a connector is restricted to that team. Remove the connector's team restriction first. ## What members see vs. what admins see On the Members page you see every user in the org, whatever teams they're in. A regular user who opens `/settings/org/teams` sees only the teams they belong to. ## Where next - [Org settings](https://docs.privatemind.com/org-settings.html): flip features on and off for everyone in the org - [Audit logs](https://docs.privatemind.com/audit-logs.html): see who added whom and when - [Budgets and limits](https://docs.privatemind.com/budgets-and-limits.html): see per-user token consumption