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

# Overview

> Understanding organizations in the Thena platform

Organizations are the foundational building blocks of the Thena platform that help you manage your teams, members, and resources. Think of an organization as your company's dedicated workspace where all collaboration, automation, and management takes place.

<Note>Users can be members of multiple organizations simultaneously. This allows individuals to participate in different workspaces while maintaining separate access controls and settings for each organization.</Note>

## What is an organization?

An organization in Thena platform represents a distinct business entity with its own:

* Members and teams
* Resources and configurations
* Customized settings and branding
* Security and access controls

## Creating and joining organizations

### Organization creation

When you create an organization, you automatically become the organization admin. The organization is uniquely identified by a combination of:

* Organization name
* Domain (derived from your email)

<Note>Organization names must be unique within the same domain. For example, if an organization named "Thena" exists under domain "thena.ai", another organization with the same name cannot be created under that domain.</Note>

### Domain-based joining

As an organization admin, you can configure whether users from your domain can automatically join your organization:

<CardGroup cols={2}>
  <Card title="Allow domain joining" icon="users-between-lines">
    Users with matching email domains can automatically join the organization
  </Card>

  <Card title="Restrict domain joining" icon="user-lock">
    Users with matching email domains must be explicitly invited
  </Card>
</CardGroup>

### Example scenario

Here's how the domain-based organization system works:

<Steps>
  <Step title="First org creation">
    <Card>
      <div style={{ display: 'flex', flexDirection: 'column', gap: '8px' }}>
        <div>
          <strong>User:</strong> [alice@acme.com](mailto:alice@acme.com)
        </div>

        <div>
          <strong>Creates:</strong> "Acme Corp"
        </div>

        <div>
          <strong>Domain:</strong> acme.com
        </div>

        <div>
          <strong>Setting:</strong> Allow domain joining
        </div>
      </div>
    </Card>
  </Step>

  <Step title="Second org creation">
    <Card>
      <div style={{ display: 'flex', flexDirection: 'column', gap: '8px' }}>
        <div>
          <strong>User:</strong> [bob@acme.com](mailto:bob@acme.com)
        </div>

        <div>
          <strong>Creates:</strong> "Acme Inc"
        </div>

        <div>
          <strong>Domain:</strong> acme.com
        </div>

        <div>
          <strong>Setting:</strong> Restrict domain joining
        </div>
      </div>
    </Card>
  </Step>

  <Step title="New user signup">
    <Card>
      <div style={{ display: 'flex', flexDirection: 'column', gap: '16px' }}>
        <div>
          <strong>User:</strong> [carol@acme.com](mailto:carol@acme.com) <br /><br />
          <strong>Options available:</strong>
        </div>

        <div>
          • Join "Acme Corp" (available due to domain matching and allowed joining)
        </div>

        <div>
          • Create new org (cannot use names "Acme Inc" or "Acme Corp" with acme.com domain)
        </div>
      </div>
    </Card>
  </Step>
</Steps>

### Key components

When creating an organization, you'll need to set up:

<CardGroup cols={2}>
  <Card title="Organization name" icon="building">
    A unique identifier for your organization (unique within your domain)
  </Card>

  <Card title="Domain settings" icon="globe">
    Configure whether users from your domain can automatically join
  </Card>

  <Card title="Organization icon" icon="image">
    Your organization's branding image (recommended size 512x512px)
  </Card>

  <Card title="Access settings" icon="lock">
    Additional access controls and security settings
  </Card>
</CardGroup>

## Organization settings

### General settings

<AccordionGroup>
  <Accordion title="Basic information" icon="info">
    * Organization name
    * Organization URL (for easy access)
    * Organization icon (branding)
    * Description
  </Accordion>

  <Accordion title="Access control" icon="shield">
    Choose between:

    * **Restricted**: Only invited members can join (recommended for most organizations)
    * **Open**: Anyone with the organization link can join
  </Accordion>

  <Accordion title="Branding" icon="palette">
    Customize your organization's appearance:

    * Organization icon
    * Color scheme
    * Email templates
    * Custom domain settings
  </Accordion>
</AccordionGroup>

### Member management

<CardGroup cols={2}>
  <Card title="Roles" icon="user-gear">
    • <b>Admin:</b> Full organization control<br />
    • <b>Member:</b> Standard access<br />
    • <b>Viewer:</b> Read-only access
  </Card>

  <Card title="Permissions" icon="key">
    • Role-based access control<br />
    • Custom permission sets<br />
    • Resource-level permissions
  </Card>
</CardGroup>

### Team structure

Organizations can have multiple teams for different functions:

<CardGroup cols={2}>
  <Card title="Team hierarchy" icon="sitemap">
    Create parent-child team relationships for better organization
  </Card>

  <Card title="Team settings" icon="sliders">
    Configure team-specific workflows, permissions, and automations
  </Card>
</CardGroup>

## Best practices

### Organization setup

1. **Plan your structure**
   * Define clear team hierarchies
   * Set up logical member groupings
   * Plan permission schemes

2. **Security first**
   * Start with restricted access
   * Implement role-based permissions
   * Regular security audits

3. **Standardize processes**
   * Create consistent naming conventions
   * Document organization policies
   * Establish clear workflows

### Member onboarding

1. **Clear roles**
   * Define role responsibilities
   * Set up proper permissions
   * Document access levels

2. **Structured process**
   * Create onboarding checklists
   * Provide necessary training
   * Set up mentorship pairs

## Related resources

<CardGroup cols={2}>
  <Card title="Team management" icon="users" href="/platform/core-concepts/teams/overview">
    Learn how to effectively manage teams within your organization
  </Card>

  <Card title="Member roles" icon="user-gear" href="/platform/core-concepts/users/roles">
    Understand different member roles and their permissions
  </Card>

  <Card title="Security settings" icon="shield" href="/platform/core-concepts/auth/overview">
    Configure organization security and access controls
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/platform/core-concepts/workflows/overview">
    Set up automated workflows for your organization
  </Card>
</CardGroup>