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

# Platform Overview

> Key concepts and how Maadify workflows run

## Key concepts

* **Tenant (company)**: the organization where agents run and tools are available.
* **Connector**: stores application authentication and exposes tools.
* **Tool**: an action an agent can take in a connected application.
* **Parent agent**: the orchestrator that runs on chat or triggers.
* **Sub-agent**: a specialized worker with prompts, tools, and memory.
* **Prompt template**: a reusable prompt with variables and guardrails.
* **Trigger**: a schedule or webhook that starts a workflow.
* **Rule**: conditional logic that decides what runs next.
* **Approval**: a user gate that must be approved before action.
* **Index data store**: internal knowledge that agents can query.
* **Notifications**: alerts about errors, approvals, and outcomes.

<Frame>
  <img src="https://mintcdn.com/maadify/X4aEKWAIWIr8YAhZ/images/parent-agents/parent-agent-flow-nodes.png?fit=max&auto=format&n=X4aEKWAIWIr8YAhZ&q=85&s=75f90f02521c6cbf0eebb6f54a554350" alt="Diagram showing connectors feeding tools into parent agents and sub-agents with triggers, rules, and approvals" width="1887" height="971" data-path="images/parent-agents/parent-agent-flow-nodes.png" />
</Frame>

## How users interact with agents

Chat is the main way users test agents and use them after setup. It gives users one place to ask questions, route work to parent agents, search internal data, and review workflow execution.

Users can interact with agents in three ways:

* **Choose a default agent** when every message should go to one parent agent.
* **Use Select Agent** when Maadify should choose the best parent agent based on the question and each agent description.
* **Configure commands** when users need quick access to specific agents from the command box.

Chat can also run **Universal Search** across selected index data stores. This helps users ask questions about internal information without choosing a workflow first.

When a parent agent runs from chat, users can inspect the workflow in real time. Each step shows the agent response, tool call, or tool execution with the input and output. Responses can include sources from retrieved data, generated CSV output, or live action context such as a virtual browser session.

<Card title="Chat with agents" icon="messages-square" href="https://app.maadify.com/chat">
  Learn how chat routing, Select Agent, commands, workflow steps, and sources work.
</Card>

## How a workflow runs

<Steps>
  <Step title="Connect your tools">
    You connect applications and make tools available to your tenant.
  </Step>

  <Step title="Define agents and prompts">
    You create parent agents and sub-agents with prompt templates and memory context.
  </Step>

  <Step title="Add triggers and rules">
    You specify when agents run and what logic controls the next step.
  </Step>

  <Step title="Review and approve actions">
    Approvals and notifications keep humans in the loop before actions run.
  </Step>
</Steps>

## Where to go next

<CardGroup cols={2}>
  <Card title="Connectors" icon="plug" href="/connectors">
    Configure authentication, tools, and defaults.
  </Card>

  <Card title="Parent agents" icon="bot-message-square" href="/agents/parent-agents">
    Build orchestrators with rules, approvals, and triggers.
  </Card>

  <Card title="Chat with agents" icon="messages-square" href="https://app.maadify.com/chat">
    Test agents, route questions, and inspect workflow steps.
  </Card>

  <Card title="Agent activity" icon="activity" href="/agents/agent-activity">
    Investigate runs, tools, and context.
  </Card>

  <Card title="Index data store" icon="database" href="/index-data-store">
    Provide internal data as a tool for agents.
  </Card>
</CardGroup>