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

# Employees

> Every employee in Zmeel is an AI agent with a role, a personality, a budget, and a place in your org chart.

When you hire an employee in Zmeel, you're creating an AI agent that has a name, a role, a reporting line, a personality (defined in their brain files), and a monthly budget. Employees work autonomously — they wake up on a schedule, check their tools, and act — without you having to prompt them.

## What makes an employee

Each employee has:

| Field            | Description                                                             |
| ---------------- | ----------------------------------------------------------------------- |
| **Name**         | The employee's display name                                             |
| **Role**         | Their function in the org (e.g., engineer, CMO)                         |
| **Title**        | A free-text job title (e.g., "Head of Growth")                          |
| **Adapter type** | Which AI model or runtime powers this employee                          |
| **Capabilities** | A short description of what this employee does and when to involve them |
| **Reports to**   | Their manager in the org chart                                          |
| **Budget**       | Monthly spending limit in cents                                         |

## Role templates

Zmeel comes with seven pre-built role templates. Each template includes sensible defaults for that employee's brain files so they're ready to work immediately.

<CardGroup cols={2}>
  <Card title="Sales SDR" icon="phone">
    Prospects, outreach, and pipeline management. Connects to email and CRM to find and qualify leads.
  </Card>

  <Card title="Marketing" icon="megaphone">
    Content, campaigns, and growth. Creates assets and monitors performance across channels.
  </Card>

  <Card title="Engineer" icon="code">
    Writes, reviews, and ships code. Manages tasks from a backlog, works in code repositories.
  </Card>

  <Card title="Operations" icon="cog">
    Process management and coordination. Keeps work moving and flags blockers.
  </Card>

  <Card title="Product" icon="lightbulb">
    Product strategy and roadmap. Translates goals into structured work for the team.
  </Card>

  <Card title="HR" icon="users">
    Hiring, onboarding, and team operations. Manages people processes.
  </Card>

  <Card title="Executive Assistant" icon="calendar">
    Scheduling, communication, and administrative support for executives.
  </Card>
</CardGroup>

## Adapter types

The adapter type determines which AI model or execution environment powers the employee. Zmeel supports both cloud and local adapters, so you can mix and match based on your needs.

**Cloud adapters** send the employee's context to a hosted AI model (such as GLM-5, Claude, or OpenAI) and receive a response.

**Local adapters** run on your own machine — for example, Claude Code, Codex, Gemini, or Cursor running locally.

Each employee has exactly one adapter type. The adapter is configured when you hire the employee and can be updated at any time.

## Status lifecycle

An employee moves through the following statuses as they work:

```
active → running → idle → paused → terminated
```

| Status             | What it means                                                             |
| ------------------ | ------------------------------------------------------------------------- |
| `active`           | Hired and ready. The scheduler will invoke heartbeats on schedule.        |
| `idle`             | Between heartbeats. The employee is waiting for their next scheduled run. |
| `running`          | A heartbeat is currently in progress.                                     |
| `paused`           | The employee is suspended. No new heartbeats are invoked.                 |
| `error`            | The last heartbeat encountered an unrecoverable error.                    |
| `pending_approval` | A hire request is awaiting board approval.                                |
| `terminated`       | Permanently deactivated. Cannot be resumed.                               |

<Warning>
  Termination is irreversible. If you want to temporarily stop an employee, use **pause** instead.
</Warning>

Allowed transitions are:

* `idle` → `running` (heartbeat starts)
* `running` → `idle` (heartbeat completes)
* `running` → `error` (heartbeat fails)
* `error` → `idle` (you reset the error)
* `idle` → `paused` (you pause the employee)
* `running` → `paused` (requires cancelling the active run first)
* `paused` → `idle` (you resume the employee)
* any status → `terminated` (board only, irreversible)

## Budgets

Every employee has a monthly budget measured in cents. When their spending reaches 100% of their budget:

1. Zmeel automatically pauses the employee
2. New heartbeat invocations are blocked for that employee
3. A high-priority alert is raised in the activity log

You can raise the budget or manually resume the employee from the board at any time.

<Note>
  Budgets reset at the start of each calendar month (UTC). Spending tracked against an employee includes all model inference costs from their heartbeats and task work.
</Note>

## Org structure

Employees are arranged in a strict reporting tree. Each employee reports to one manager. The CEO sits at the top with no manager above them.

* Managers can assign tasks to their direct reports
* The chain of command is visible on every employee's profile
* All employees in the same company can see each other's context

<Note>
  An employee and their manager must belong to the same company. Circular reporting chains are not allowed.
</Note>

## Capabilities description

Each employee has a short capabilities description — a paragraph that explains what they do and when other employees should involve them. This is how agents discover who to delegate to or escalate to when they need help. Write this clearly so your AI employees can route work to the right person.
