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

# Agent Folders in DialNexa

> Understand DialNexa agent folders: creating, renaming, deleting, and moving agents into folders. Use folders to organize agents by team, environment, or use case.

Agent folders in DialNexa help teams organize the Agents tab. Folders can be created, selected, renamed, deleted, and used as filters. Agents can be moved into folders from row actions so large workspaces do not turn into a long scroll of mystery callers.

<Tip>
  Folders are boring until the day you have forty agents named "Support Bot". Then folders are civilization.
</Tip>

## What Folders Do

A folder is a label applied to agents for organizational purposes. Selecting a folder in the sidebar filters the agent list to show only agents in that folder. Folders have no effect on call behavior, routing, or agent configuration.

| Folder behavior   | Detail                                                                                                                |
| ----------------- | --------------------------------------------------------------------------------------------------------------------- |
| Filtering         | Selecting a folder shows only agents assigned to it. "All Agents" shows everything.                                   |
| Counts            | Each folder shows the number of agents it contains.                                                                   |
| No nesting        | Folders are a single level. Sub-folders are not supported.                                                            |
| No routing effect | Moving an agent into or out of a folder does not change call behavior, phone number assignment, or published version. |

## Creating a Folder

<Steps>
  <Step title="Open the Agents tab">
    Click **Agents** in the left sidebar.
  </Step>

  <Step title="Click New Folder">
    Find the **New Folder** button in the folder sidebar or the action menu at the top of the Agents list. Click it.
  </Step>

  <Step title="Name the folder">
    Enter a name. Use names that are searchable and self-explanatory to anyone on your team. Click **Create**.
  </Step>
</Steps>

The folder appears in the sidebar immediately. It is empty until you move agents into it.

## Moving Agents into a Folder

<Steps>
  <Step title="Find the agent">
    In the Agents list, locate the agent you want to move. You can be in "All Agents" view or inside a different folder.
  </Step>

  <Step title="Open the row action menu">
    Click the three-dot menu on the agent row (far right of the row).
  </Step>

  <Step title="Select Move to Folder">
    Click **Move to Folder** and choose the destination folder from the dropdown. The agent moves immediately.
  </Step>
</Steps>

You can also drag and drop agents into folders in the sidebar if your dashboard supports drag-and-drop interaction.

## Renaming a Folder

Click the three-dot menu next to the folder name in the sidebar and select **Rename**. Enter the new name and confirm. The new name appears everywhere the folder is referenced.

## Deleting a Folder

<Steps>
  <Step title="Check the folder contents">
    Before deleting, open the folder and decide what to do with the agents inside. Deleting a folder does not delete the agents in it, but they will appear under "All Agents" without a folder assignment.
  </Step>

  <Step title="Delete the folder">
    Click the three-dot menu next to the folder name and select **Delete**. Confirm the action.
  </Step>
</Steps>

<Warning>
  Deleting a folder that contains agents will leave those agents without a folder assignment. They remain accessible under "All Agents" but are no longer organized. Move or reassign them before deleting the folder if organization matters.
</Warning>

## Good Folder Schemes

Pick a folder structure that matches how your team searches for agents.

<CardGroup cols={2}>
  <Card title="Use case" icon="folder" href="/common-use-cases">
    Examples: Qualification, Reminders, Collections, Support Intake, Surveys. Best for teams that search by what the agent does.
  </Card>

  <Card title="Customer or project" icon="briefcase" href="/platform/workspaces">
    Useful for agencies or teams running separate customer deployments. One folder per client keeps things clean.
  </Card>

  <Card title="Environment" icon="layers" href="/agents/agent-versions-and-publishing">
    Examples: Production, QA, Archived. Separates agents ready for live traffic from agents still being tested.
  </Card>

  <Card title="Team ownership" icon="users" href="/platform/workspaces">
    Examples: Sales Ops, Support Ops, Growth. Helps teams find agents they own without searching across everyone else's work.
  </Card>
</CardGroup>

## Using Folders for Environment Separation

A common pattern is to use folders as an environment indicator alongside your naming convention. For example:

* Folder: `Production` containing agents named `Lead Qual - English`, `Appointment Reminder - Hindi`
* Folder: `QA` containing agents named `Lead Qual - English [TEST]`, `Appointment Reminder - Hindi [TEST]`
* Folder: `Archive` containing old experiments and deprecated versions

This approach makes it clear at a glance which agents are live and which are candidates or retired.

<Note>
  Environment folders are an organizational convention, not a technical enforcement layer. DialNexa does not prevent you from assigning a "QA" folder agent to a production phone number. Enforce environment discipline through team process and naming.
</Note>

## Folder Questions

<AccordionGroup>
  <Accordion title="Does moving an agent change its behavior?">
    No. Folder placement is purely organizational. The agent's prompt, published version, phone number assignment, workflow connections, and all other configuration are unaffected by folder moves.
  </Accordion>

  <Accordion title="Can a folder replace workspace separation?">
    No. Workspaces are isolated environments with separate billing, phone numbers, and API keys. Folders organize agents within a single workspace. Use workspaces for true isolation and folders for agent organization inside one workspace.
  </Accordion>

  <Accordion title="Can the same agent be in multiple folders?">
    No. Each agent belongs to one folder at a time. To "copy" an agent across folders, duplicate the agent and assign the duplicate to a different folder.
  </Accordion>

  <Accordion title="What happens to agents when a folder is deleted?">
    The agents remain in the workspace and are accessible under "All Agents". They lose their folder assignment but retain all their configuration, version history, and routing.
  </Accordion>

  <Accordion title="Is there a limit on the number of folders?">
    There is no documented hard limit on folders, but very large numbers of folders can make navigation harder rather than easier. A flat structure of 5 to 15 folders covers most workspace needs.
  </Accordion>
</AccordionGroup>

## Keep Folders Useful Over Time

<Steps>
  <Step title="Use names people would search for">
    The folder label should be obvious to someone new to the workspace. Avoid internal codes or abbreviations that only one person understands.
  </Step>

  <Step title="Move agents after creation">
    New agents land outside any folder by default. Move them into the right folder before handing off to someone else.
  </Step>

  <Step title="Archive by moving, not deleting">
    Move old experiments into an Archive folder before deleting them outright. This gives you a recovery window if you need the configuration later.
  </Step>

  <Step title="Review folder counts periodically">
    High counts in one folder and low counts in another may indicate the structure needs revisiting. An "Archive" folder with 60 agents and a "Production" folder with 3 is a signal to clean up.
  </Step>
</Steps>

## Related Reading

<CardGroup cols={2}>
  <Card title="Agents Overview" icon="sparkles" href="/agents/overview">
    Understand the full agent list and how agents are managed.
  </Card>

  <Card title="Agent Versions and Publishing" icon="git-commit" href="/agents/agent-versions-and-publishing">
    Manage draft and published versions of agents inside folders.
  </Card>

  <Card title="Agent Templates" icon="layout-template" href="/agents/templates">
    Create new agents faster with pre-built templates.
  </Card>

  <Card title="Import Agents" icon="upload" href="/import-agents">
    Import agent configurations from other workspaces.
  </Card>
</CardGroup>