> ## Documentation Index > Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt > Use this file to discover all available pages before exploring further. # Manage members > Invite people to your organization, assign roles, group them into teams, and remove access. Add people to your organization, set what they can do, and remove access when they leave. This takes a couple of minutes. You need to be an **owner** or **admin** to manage members. Manage everyone under [**Settings > Members**](https://app.sazabi.com/settings/members). ## Invite a member > [tab] Dashboard > > 1. Go to [**Settings > Members**](https://app.sazabi.com/settings/members) and enter one or more email addresses. > 2. Choose the role to grant — **Admin** or **Member**. You should see the address listed with an **Invited** status once you send the invite. > 3. The invitee receives an email to accept. When they accept, their status changes from **Invited** to active. > [tab] CLI > > Invite and manage members with the CLI (install and authenticate per [`/reference/cli`](https://docs.sazabi.com/reference/cli)). Members are organization-scoped; `--role` accepts `admin` or `member` and defaults to `member`. > > ```bash theme={"system"} > sazabi members invite --email alex@example.com # Invite one person as a member > sazabi members invite --email a@example.com --email b@example.com --role admin # Invite several as admins > sazabi members list # List members > sazabi members list-invitations # List pending invitations > sazabi members revoke-invitation # Revoke a pending invitation > ``` > > Each address is listed with an **Invited** status until the invitee accepts the emailed invite. You assign **Admin** or **Member** on invite. The owner role is not assignable from here. ## Roles Each member holds one role — Owner, Admin, Member, or Viewer. For what each role can do, see [Access control](https://docs.sazabi.com/manage/access-control.md). Change a member's role from the same page, or from the CLI with `sazabi members update-role --role admin` (`--role` accepts `admin` or `member`; see [`/reference/cli`](https://docs.sazabi.com/reference/cli)). You cannot change your own role, and the owner is managed separately. ## Teams Group members into **teams** to assign component ownership and organize your people. Teams are an organization-level grouping; a member can belong to several teams. Manage teams from the members area, and assign a component's owning team from the project **Status** page (see [Service status](https://docs.sazabi.com/triage/status.md)). A team's ownership is live routing state: a notification or task-creation rule can target a team instead of listing components by hand, and reassigning a component's owner changes which team-scoped rules match its next issue with no rule edit (see [Route notifications](https://docs.sazabi.com/triage/notifications.md)). Deleting a team any rule still names is refused until the rule is edited or removed. ## Remove a member Remove a member from the members list, or from the CLI with `sazabi members remove ` (see [`/reference/cli`](https://docs.sazabi.com/reference/cli)). Removal is immediate and revokes their access to the organization and its projects. ## Verify Invite a test address and confirm it lands: 1. Invite an address you control at [**Settings > Members**](https://app.sazabi.com/settings/members). 2. The address appears in the members list with an **Invited** status. 3. Accept the invite from that address's inbox; the member becomes active, usually within a minute. If the invite never arrives, confirm the address is correct and check the recipient's spam folder before re-inviting. ## Further reading > [card] [Access control](https://docs.sazabi.com/manage/access-control.md) > > What each role can do. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.