> ## Documentation Index
> Fetch the complete documentation index at: https://app.keystroke.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Members

> Invite members and manage roles.

Organization members are the people who can access your Keystroke workspace. Their organization role controls what they can do across the organization, while project membership controls which projects they can see and work in.

Use **Settings > Members** to invite teammates, review membership status, change roles, and mark members inactive.

## Members list

The members table shows each member's name, email, role, and last active time. You can search the table and switch between saved views for owners, admins, and builders.

Members can have these statuses:

| Status             | What it means                                |
| ------------------ | -------------------------------------------- |
| **Active**         | The person has joined the organization       |
| **Pending invite** | An invitation has been sent but not accepted |
| **Inactive**       | The person no longer has organization access |

Inactive members stay visible in the list so you can understand past ownership and activity.

## Organization roles

Keystroke has three organization roles:

| Role        | What it can do                                                           |
| ----------- | ------------------------------------------------------------------------ |
| **Owner**   | Full control over organization settings, billing, members, and ownership |
| **Admin**   | Manage organization settings, members, and shared resources              |
| **Builder** | Build and use projects, workflows, agents, and apps                      |

Owners cannot be assigned from the invite or role edit flow. New members can be invited as admins or builders.

Organization roles are separate from project roles. A builder can be added as a project admin on a specific project, and an org admin can see every project in the organization. See [Manage projects](/learn/projects/manage-projects).

## Invite members

Invite members from the web app with **Add members**. You can paste one or more email addresses separated by commas, spaces, or new lines, then choose the role for the invite.

You can also invite members with the CLI:

```bash theme={null}
keystroke organization members invite --email ada@example.com --role builder
keystroke organization members invite --email ada@example.com --email grace@example.com --role admin
```

Who you can invite depends on your role:

| Your role   | Roles you can invite |
| ----------- | -------------------- |
| **Owner**   | Admin, Builder       |
| **Admin**   | Admin, Builder       |
| **Builder** | Builder              |

## Change roles

Owners and admins can change a member's role between admin and builder:

```bash theme={null}
keystroke organization members role <user-id> --role admin
```

The CLI uses user IDs for role changes. Use `keystroke organization members list` to find the member you want to update.

## Remove access

Owners and admins can mark a member inactive from the member actions menu. Inactive members lose organization access but stay visible in the members list.

You can also remove access with the CLI:

```bash theme={null}
keystroke organization members remove <user-id>
```

## Leave an organization

If you no longer need access to an organization, you can leave it from the CLI:

```bash theme={null}
keystroke organization leave --yes
```

Leaving clears the active organization and active project from your local CLI config.

## Next steps

<CardGroup cols={2}>
  <Card title="Organization" href="/learn/settings/organization">
    Manage organization identity and workspace settings.
  </Card>

  <Card title="Manage projects" href="/learn/projects/manage-projects">
    Add members to individual projects and manage project roles.
  </Card>

  <Card title="API keys" href="/learn/settings/api-keys">
    Create and revoke keys for programmatic platform access.
  </Card>

  <Card title="CLI reference" href="/cli#organization-and-access">
    See the organization and access commands.
  </Card>
</CardGroup>
