# Managing members

> Inviting, setting permissions, changing a role, making someone an owner, removing — and how quickly changes take effect.

Everything here is done by the **organisation owner** in [Settings](/en/docs/settings) → organisation → **“Members”**. Other members see the same list without the management buttons.

## Inviting

The form above the list:

1. **Login or email.** An existing user joins the organisation immediately. For an unknown email an account is created, and the person gets an email with a link to set a password; an account that is never signed in to is deleted after 30 days.
2. **Scope** — the whole organisation, a development project, a space or a repository. The list contains only projects, spaces and repositories of **this** organisation.
3. **Role** — Contributor or Maintainer.
4. **“Invite”.**

The member appears in the list with a chip like “Contributor · Project shop”. If several scopes or individual adjustments are needed, continue with the “Permissions” button.

<Callout type="info">
Inviting a member who already belongs to the organisation again does not create a duplicate: their grants are replaced with those given in the form. This is a handy way to “reassign” a person in one action — but individual adjustments are reset.
</Callout>

## Setting permissions

In the member’s row press **“Permissions”**. An editor opens — one card per scope:

- **Scope** — a drop-down list: the organisation, projects, spaces, repositories.
- **Role** — a Contributor / Maintainer switch. Under it is a description of the role.
- **“Advanced”** — expands all permissions by group (“Tasks”, “Review”, “Deep research”, “Ask”, “Project”, “Knowledge base”, “Organisation”), each as a separate switch. A switch set contrary to the role is marked “changed (role: on/off)”; the number of adjustments is visible in the collapsed state too.
- **“Reset to role”** — removes all adjustments in this scope.
- **“Add scope”** — one more card. The **bin** in a card removes the scope (the last one cannot be removed — remove the member instead).
- **“Save permissions”** — writes the whole set at once; **“Cancel”** closes without changes. Two cards for the same scope cannot be saved.

_Illustration: The permissions editor: scope, role and atomic switches behind the “Advanced” button._

After saving, the member’s chip updates: “Maintainer · Project shop”, “Contributor · The whole organisation · 2 changed”.

## Changing the role

In the editor, switch the role and save. **Changing the role is a new starting point:** individual adjustments made for the previous role are reset. If you need “Contributor plus a couple of Maintainer permissions”, keep Contributor and turn on the switches needed under “Advanced”.

## Making someone an owner and removing that

The shield icon in the member’s row: **“Make owner”** gives full permissions, and the grants stop being taken into account (the owner can do everything). **“Remove the owner role”** returns the member to their grants — if they had none, give them some through “Permissions”, otherwise they will see nothing. The last owner cannot be removed or demoted.

## Removing a member

The bin in the member’s row. Removal takes away all grants and access to the organisation’s repositories; at their next request the member sees “Organisation not found”. Their tasks, conversations and research stay in the organisation — they belong to it, not to the member.

## When changes take effect

- **On the server — immediately.** Every action is checked against the current permissions; saved changes apply from the next request.
- **In the member’s interface — within a minute** or on a page reload: the app re-reads permissions periodically and on organisation events. Until then the member may see a button they have already lost; pressing it returns the explanation “Not enough rights: this action is not part of your role in the organisation”.

## Who is who in the list

- A crown and an “Owner” chip — an owner.
- One chip per scope — a member with grants.
- A red “No permissions” chip — the member belongs to the organisation but has no grants: they see nothing. This happens after the owner role is removed or when all scopes have been deleted by hand; give them grants through “Permissions”.

The pipeline’s service accounts are not shown in the list.