> ## 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.

# Organization

> Manage your organization and workspace settings.

An organization is your company workspace in Keystroke. It contains your members, projects, platform API keys, billing status, and organization-wide settings.

Use organization settings for workspace identity and access. Use [project settings](/learn/projects/manage-projects) when you want to manage a specific project's members, deployments, credentials, or runtime state.

## What you can manage

Open **Settings > Organization** in the web app to manage the active organization.

| Setting                 | What it controls                                                    |
| ----------------------- | ------------------------------------------------------------------- |
| **Name**                | The display name shown throughout the platform                      |
| **URL**                 | The organization slug used in app URLs, such as `keystroke.ai/acme` |
| **Sidebar logo**        | The logo shown in your organization's sidebar                       |
| **Logo size**           | The rendered height of the custom sidebar logo                      |
| **Delete organization** | Sends a deletion request to the Keystroke team                      |

Changing the organization URL changes the paths teammates use to reach the organization. Update bookmarks or shared links after changing it.

<Note>
  Organization deletion is not instant self-service today. The web app sends a deletion request, and the Keystroke team follows up to confirm details before scheduling deletion.
</Note>

## Update the organization name

You can update the organization name from the web app or the CLI:

```bash theme={null}
keystroke organization update --name "Acme"
```

The CLI updates the active organization. Use `keystroke auth status` to confirm which organization your CLI is targeting, or `keystroke config use org` to switch organizations.

## Organization roles

Organization roles control what a member can do across the workspace:

| 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 and admins can update organization settings. Builders can work in projects they have access to, but cannot change organization-level settings.

See [Members](/learn/settings/members) for inviting teammates and changing roles.

## Settings that are request-gated

Some settings sections in the web app are shown as Enterprise request-gated pages. They include managed services, hosted MCPs, identity and auth, usage limits, permission groups, and audit logs.

Those sections are not self-service settings today. Use the request button in the web app if you want access.

## Next steps

<CardGroup cols={2}>
  <Card title="Members" href="/learn/settings/members">
    Invite teammates and manage organization roles.
  </Card>

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

  <Card title="Billing" href="/learn/settings/billing">
    Review early-access usage and billing status.
  </Card>

  <Card title="Manage projects" href="/learn/projects/manage-projects">
    Manage access and settings for individual projects.
  </Card>
</CardGroup>