> ## Documentation Index > Fetch the complete documentation index at: https://to11.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Organizations > Create and manage the top-level tenant that owns your members, roles, and API keys. An organization is the top-level tenant in to11. It owns your [workspaces](/docs/platform/workspaces) and [projects](/docs/platform/projects), your [members and invitations](/docs/platform/team), your [roles](/docs/platform/roles-and-permissions), and your [API keys](/docs/platform/api-keys). Everything else lives inside it. ## Creating an organization Your organization is created the first time you sign up, during onboarding. You give it a **name** and a **URL slug** — the slug is the short identifier that appears in dashboard URLs (`/org//…`). The person who creates the organization becomes its **owner**, holding the `org_owner` role, which carries every permission in the organization. Most teams run a single organization. You'd create a second one only to keep entirely separate tenants — for example, isolating one business unit's members, data, and billing from another's. ## Membership and access Who belongs to the organization and what they can do is managed on two pages: * [Team](/docs/platform/team) — invite people, manage the roster, and handle pending invitations. * [Roles & permissions](/docs/platform/roles-and-permissions) — decide what each member is allowed to do. ## Changing or deleting an organization An organization's name and slug are set when it's created. Renaming an organization, or deleting one, isn't a self-service action in the dashboard today. Deleting an organization removes its workspaces, projects, and data, so it's handled deliberately rather than from a button. Need to rename or delete an organization, or separate data into a new one? [Get in touch](/docs/help/support). ## Next steps Group projects within the organization. Invite people to the organization.