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

# Organization

> Build your church, ministry, and service type hierarchy — and define staffing templates.

**Organization** defines your structure: **Church** → **Ministries** → **Service Types**. Service types carry schedule details and **Staffing** templates that power **Roster** and **Rotation Teams**.

<Frame>
  <img src="https://mintcdn.com/adoraplan-b5f8a5a4/Q7eIYf4z4qB2WPTX/images/organization/org-tree.png?fit=max&auto=format&n=Q7eIYf4z4qB2WPTX&q=85&s=3a96d5c59927df17631f3893ebc8f95e" alt="Organization tree with one church and nested ministry and service type nodes" width="1440" height="900" data-path="images/organization/org-tree.png" />
</Frame>

## Quick Start

1. Open **Organization** in the sidebar.
2. Click **Add Church** if you have no churches yet.
3. Under a church, add **Ministries** (Worship, Youth, etc.).
4. Add **Service Types** (e.g. Sunday Morning Worship) with day and time.
5. Edit a service type → **Staffing** tab → define required roles and quantities.

***

## How-to Guide

### Build the tree

<Frame>
  <img src="https://mintcdn.com/adoraplan-b5f8a5a4/oEAoIeMo_RzI8e8d/images/organization/org-tree-expanded.png?fit=max&auto=format&n=oEAoIeMo_RzI8e8d&q=85&s=f96d535ccc3ae6c15a961fcb78f438fd" alt="Fully expanded organization tree showing church, ministries, and service types" width="1440" height="900" data-path="images/organization/org-tree-expanded.png" />
</Frame>

<Steps>
  <Step title="Add a church">
    **Add Church** → name, optional acronym, city, contact fields.
  </Step>

  <Step title="Add ministries">
    Use the tree actions under a church → **Add Ministry**.
  </Step>

  <Step title="Add service types">
    Under a church or ministry → **Add Service Type** → name, schedule day/time, color.
  </Step>

  <Step title="Search">
    Use **Search churches, ministries, services...** to filter a large tree.
  </Step>
</Steps>

### Define staffing requirements

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/adoraplan-b5f8a5a4/images/organization/template-roles.png" alt="Service Type Staffing tab listing team roles with quantity inputs" />
</Frame>

<Steps>
  <Step title="Edit service type">
    Click the pencil icon on a service type → **Staffing** tab.
  </Step>

  <Step title="Add roles">
    Add rows from your **Team Roles** catalog with quantities (e.g. 2× Vocals, 1× Drums).
  </Step>

  <Step title="Use in roster">
    When you **Auto-fill from Template** on a program roster, these slots are created automatically.
  </Step>
</Steps>

### Summary cards and health

The top row shows counts for **Churches**, **Ministries**, **Services**, **Programs**, and **Issues**.

Click **Issues** to expand the health panel — warnings about missing staffing templates, orphaned nodes, or configuration gaps, with links to fix them.

### Tree actions

| Node             | Common actions                                           |
| ---------------- | -------------------------------------------------------- |
| **Church**       | Edit, **View Calendar**, **View Programs**, delete       |
| **Ministry**     | Edit, **View People** (filtered), delete                 |
| **Service Type** | Edit (Details + Staffing), **View All Programs**, delete |

<Note>
  **Account → Organization Settings** (`/account`) is different — it controls tenant name and billing, not the church/ministry tree.
</Note>

***

## Related

<CardGroup cols={2}>
  <Card title="Roster" icon="users" href="/en/adoraplan/roster">
    Staffing driven by service-type templates.
  </Card>

  <Card title="Programs" icon="calendar-check" href="/en/adoraplan/programs">
    Each program picks a service type from this tree.
  </Card>

  <Card title="People" icon="user" href="/en/adoraplan/people-and-team">
    Collaborators linked to ministries.
  </Card>

  <Card title="Calendar" icon="calendar" href="/en/adoraplan/calendar">
    **View Calendar** from a church node.
  </Card>
</CardGroup>