> ## Documentation Index > Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt > Use this file to discover all available pages before exploring further. # Organizations > Organizations are the top-level container in Ravenna that hold workspaces, members, integrations, billing, and shared settings for your company. An organization represents your company in Ravenna. It is the top-level container that holds all of your workspaces, members, integrations, and settings. Every Ravenna user belongs to at least one organization. ## How organizations and workspaces relate Your organization contains one or more workspaces. Each workspace is a separate space for a team or department to manage their own support requests, with independent channels, tickets, forms, and settings. Settings are split between the two levels: * **Organization settings** apply across your entire account, including branding, SSO, notification policy defaults, and member management. * **Workspace settings** are scoped to individual teams, including channels, ticket statuses, SLAs, workflows, and API keys. Learn more about [organization settings](/documentation/platform/organizations/settings) and [workspace settings](/documentation/platform/workspaces/settings). ## Organization roles An organization role is a person's baseline across the entire account. Everyone has exactly one: * **Admins** have full control over organization settings, integrations, and member management. * **Members** reach public workspaces automatically with requester access, which lets them file and track their own tickets. They cannot manage organization-level settings. To work a workspace's queue, a member must be added to that workspace. * **Guests** have no automatic workspace access, even to public workspaces. They reach a workspace only when explicitly added. By default, guests cannot see your organization in their workspace switcher. Admins can enable guest visibility in **Organization Settings > General**, which also lets guests use the Portal. The organization role is only the baseline. What someone can do inside a specific team is decided by their workspace access on top of it. For how organization roles combine with workspace access, and the full capability matrix, see [Roles and access](/documentation/platform/roles-access). ## How people join your organization People are added to your organization automatically. There is no manual "invite to organization" step. Someone becomes an organization member in one of these ways: * **Single sign-on**: the first time a person signs in through your SSO connection, Ravenna creates their organization membership. * **Identity provider or HRIS sync**: people synced from an integration are added automatically. * **Added to a workspace**: when a workspace admin adds someone by email who is not yet in the organization, their organization membership is created at the same time (see [Add someone to a workspace](/documentation/platform/workspaces/overview#add-someone-to-a-workspace)). * **Submitting a request**: when someone new sends a request by email, Slack, or Teams, Ravenna creates them as a guest so the request can be tracked. People whose email matches your company domain join as **Members**. People synced from an integration on a different email domain join as **Guests**. Enable **Guest visibility** in organization settings before guests can sign in. ## Managing organization members Go to organization settings and click the **Members** tab. Click the menu on a member's row and select **Edit** to change their organization role or set a delegate. See [organization roles](/documentation/platform/roles-access#organization-roles) for what each role can do. Select members and use the bulk action bar to remove them from the organization. Changing someone's organization role changes their baseline everywhere: promoting a member to admin grants organization-wide control, and downgrading an admin to guest removes their automatic access to public workspaces. It does not change any explicit workspace memberships they already hold. Removing someone from the organization also removes them from every workspace, because [organization membership is required before workspace membership](/documentation/platform/roles-access). Ravenna prevents removing the last organization admin so administrative access is never lost. ### Set member delegates Assign a delegate to receive a member's ticket assignments and approvals while they are unavailable. * **Manager**: uses the member's direct manager (requires the Okta integration for manager data) * **Specific user**: any organization member * **No delegate**: removes delegation Members can set their own delegates in [user settings](/documentation/platform/my-settings). Admin changes override a member's own setting. ## Access controls Organization admins can configure access in **Organization Settings > General**: * **Workspace creation**: Restrict who can create new workspaces (admins only or all members). * **Guest visibility**: Let organization guests see and sign in to your organization and use the Portal. Off by default. Learn more about [organization settings](/documentation/platform/organizations/settings) and adding people to a team in [Workspaces](/documentation/platform/workspaces/overview#add-someone-to-a-workspace).