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

# Organizations

> Manage teams, billing, and credentials at the organization level.

An organization is the top-level container in Guild. It holds your team members, billing settings, and service credentials that are shared across all workspaces.

## Creating an organization

When you sign in to [app.guild.ai](https://app.guild.ai) for the first time, Guild creates a personal organization for you automatically. To create a shared organization for your team:

1. Click your profile in the top-left corner
2. Select **New organization**
3. Give it a name and invite team members

## Organization settings

The standalone **Organization** settings section is not part of the settings sidebar. Navigating to `/settings/organization` or `/organizations/{name}/settings/organization` redirects to the **Profile** settings page. The organization identifier is displayed in the Profile Identity card under **Profile** settings. See [Settings](/platform/settings) for details.

## Members and roles

Organization members can access all workspaces within the organization. Invite members from **Settings > Members** in your organization.

### Accepting an invitation

Guild emails each invited person a verification code. Enter the code to confirm you control the email address and join the organization.

If you are already signed in to Guild and your account email matches the invitation email address, you can accept the invitation with a single click. Guild compares the two addresses case-insensitively, so capitalization does not matter. You do not need to enter a verification code, because a matching account email already proves you control the invited inbox.

#### App-wide invitation prompt

After you sign in and finish onboarding, Guild surfaces any pending organization invitations in an app-wide prompt. Accept or decline each invitation directly from the prompt. If you dismiss the prompt, Guild remembers that choice for the rest of the browser session.

#### Locked-organization gate

If you open an organization's URL (for example, `/organizations/team-name`) while your invitation to that organization is still pending, Guild withholds the organization's content and shows it as locked. Click **View invitation** to review the invitation, then accept it to unlock the organization in place. If you decline, Guild redirects you to the homepage.

## Organization profile

The organization profile includes the organization name, bio, avatar, and social links. Access it from **Settings > Profile** in your organization.

<Note>Only Admin users can edit the organization profile.</Note>

## Audit logs

Audit logs record activity across your organization, including member changes and configuration updates. Access them from **Settings > Audit Logs** in your organization.

<Note>Only Admin users can view audit logs.</Note>

## Credentials

Service credentials (GitHub, Slack, Jira, etc.) are configured at the organization level. When an agent needs access to a service, it uses the credentials connected to the organization.

Go to **Settings > Credentials** to connect services. See [Credentials](/platform/credentials) for details.

## LLM settings

Configure how Guild runs LLM calls for the organization in **Settings > LLM Settings**. Organization admins can use managed Guild tokens or add provider API keys (BYOK) for workspaces owned by the organization.

See [LLM settings](/platform/llm-settings) for details.

## Danger zone

Organization admins can request permanent deletion of the organization from **Settings > Danger Zone**. Submitting the request notifies Guild support, who processes the deletion manually.

<Warning>
  Organization deletion is permanent and cannot be undone. All workspaces, agents, sessions, and data belonging to the organization are removed.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Workspaces" icon="folder" href="/platform/workspaces">
    Create workspaces within your organization.
  </Card>

  <Card title="Credentials" icon="key" href="/platform/credentials">
    Connect third-party services.
  </Card>

  <Card title="LLM settings" icon="sparkles" href="/platform/llm-settings">
    Configure managed LLM access or provider API keys.
  </Card>
</CardGroup>