> ## 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.
# Parent Agent Flow Builder
> Use the flow view to understand nodes, edges, and execution order
## Flow view
Use **Flow view** as your primary workspace. Most users build, route, and review workflows directly in the flow.
## Node types and meanings
The flow builder visualizes your workflow as nodes:
* **Agent nodes**: sub-agents and their prompts.
* **Tool nodes**: execute-tool actions and their inputs.
* **Trigger nodes**: schedules and webhook entry points.
* **Approval nodes**: manual approvals that pause execution.
* **Error nodes**: explicit error states for routing and notifications.
## Edge meaning and routing
Edges represent routing decisions made by **rules**. When a rule matches on a node, the edge to the selected action becomes the next step.
If a node has multiple rules, edges can represent multiple outcomes. Use rule order to control which condition is evaluated first.
## Inspect and edit a node
Click a node to open its details and current rule configuration.
Update the sub-agent prompt, tool inputs, or trigger settings from the panel.
Open **Rule order** to change evaluation priority for that node.
## Manage tenant configurations
Use the **View Tenant Configurations** button in the flow view to manage how the parent agent is shared across relationships.
Select a parent agent, then choose **View Tenant Configurations**.
In **Existing Configurations**, select **Edit Config** to open the same configuration dialog you use in **Companies**.
You can update visibility switches, review tool status, and save configuration changes.
In **Add to Relationships**, select **Add Agent Name - Action** to attach the parent agent to that relationship.
You only see relationships you own and have permission to update.
Toggle **Show Inactive Relationships** to include inactive relationships in both tabs.
The tenant configuration dialog uses the same permissions and validation rules as the main **Manage Companies** table.
## Edit rules from edges
Edges represent rule outcomes. Clicking a connection opens the rule that created that path so you can edit the condition or action without hunting through the rule list.
Click an edge to open the rule tied to that route.
Edit the rule logic, then save to update the edge behavior.
## Drag edges to re-route
You can rewire a workflow directly in the flow view. When you connect an edge between two nodes, the rule behind that edge is generated for you:
* The **source node** becomes the rule's **condition**. The rule evaluates after that node finishes, so its output is what triggers the next step.
* The **target node** becomes the rule's **action**. Execution flows to that node when the condition matches.
This means you rarely have to write a rule from scratch when you draw an edge — the connection itself defines "after this node, run that node," and you only need to refine the condition or action if you want behavior beyond the default routing.
Drag the edge end from the current node. The node you start from is captured as the rule's condition source.
Release on the target node to update the routing path. The target node is automatically set as the rule's action, so the new edge represents "when the source node completes, run the target node."
Confirm the rule action now points to the new node. Open the edge to fine-tune the condition (for example, only route on a specific output) or change the action type if you need more than a direct hand-off.
Because the source and target are wired in for you, dragging edges is the fastest way to sketch a workflow. Use the rule editor afterwards only when you need conditional branching beyond the default "previous node → next node" pattern.
