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

# Create a crew

> Build a crew from registry agents on the canvas and save it.

You create a crew to automate a workflow with a team of AI agents. You add agents and tasks on a canvas, connect each
task to the agent that does it, and save the crew.

## Prerequisites

Before starting this task, ensure you have the following:

* Required roles: `nx1_crew`.
* At least one registry agent that has an approved version.

## Create a crew

> [tab] Web portal
>
> Perform these steps to create a crew:
>
> 1. Log in to NexusOne.
>
> 2. On the top navigation bar, hover your mouse over **Agents** and then select **Crews**.
>
> 3. Click **Crews**. The crew canvas opens.
>
> 4. In the crew name field at the top-left corner, enter a name for the crew.
>
> 5. In the **Blocks** list on the left, drag **Task** onto the canvas. Add one task for each step of the workflow.
>
> 6. Select a task to open its panel on the right, and then fill in the following:
>
>    * **Description**: What the agent should do. To enter a value each time you run the crew, add a placeholder
>      in curly braces. For example, `Summarize last month's sales for {region}`.
>    * **Expected output**: What the agent should return.
>
> 7. Under **Agents**, select the **Global** tab for agents everyone can use, or the **Personal** tab for your own
>    agents.
>
> 8. Optional: In the **Search agents** field, enter a name to narrow the list on the **Global** or **Personal** tab.
>
> 9. Drag each agent you want onto the canvas. The list shows only agents that have an approved version, and each
>    entry shows that version.
>
> 10. Draw a line from each agent to the task it should do. Every task needs an agent.
>
> 11. Optional: Draw a line from one task to another to let the second task use the output of the first.
>
> 12. Optional: Select an empty part of the canvas to open the crew settings, and then set any of the following:
>
>     * **Name**: The name of the crew. This is the same name you can enter at the top left of the canvas.
>
>     * **Description**: What the crew does.
>
>     * **Tags**: Words that help you find the crew, separated by commas.
>
>     * **Process**: How the crew runs its tasks. Select one of the following:
>
>       * **Sequential**: Runs the tasks in order.
>       * **Hierarchical**: Lets a manager delegate the tasks.
>
>     * **Shared**: Lets everyone with crew access see and run the crew. A shared crew can use only Global agents.
>
>     * **Variables**: The placeholders your tasks use, such as `region`. Click **Add variable**, and then set any of
>       the following:
>
>       * **Name**: The placeholder name. Use letters, digits, and underscores, and don't start with a digit.
>       * **Label**: The name of the field you see when you run the crew.
>       * **Help text**: A hint shown below the field when you run the crew.
>       * **Type**: The kind of value, such as string, text, number, integer, boolean, select, multi\_select,
>         domain, dataset, table, tag, glossary\_term, or document.
>       * **Required**: Turn it off to let the person running the crew leave the field empty. This is on by default.
>       * **Choices**: The values a person can pick, separated by commas. This appears for the select and
>         multi\_select types.
>       * **Min length** and **Max length**: The shortest and longest value allowed. These appear for the string
>         and text types.
>       * **Min value** and **Max value**: The smallest and largest value allowed. These appear for the number
>         and integer types.
>       * **Default value**: The value NexusOne uses when the person running the crew leaves the field empty.
>       * **Sensitive**: Masks the value as someone types it, and hides it from the logged record of the run.
>
>     * **Context packs**: Packs that every agent in the crew loads. To attach packs, do the following:
>
>       1. Click **Attach packs**.
>       2. Optional: In the search box of the **Attach context packs** dialog, enter a name to narrow the list.
>       3. Select each pack you want to attach.
>       4. Click **Done**.
>       5. Optional: In the **Budget** box next to an attached pack, enter a lower number to limit how much of the
>          model's context the pack may use.
>       6. Optional: To remove an attached pack, click the detach icon next to it.
>
>     * **Repository**: The approved code repositories the crew's agents might read. Click
>       **Give this crew a repository**, and then set any of the following:
>
>       * **Repositories it might read**: Select one from the **Add a repository** drop-down.
>         To remove it, click its remove icon.
>       * **Branch prefix**: The start of the name of any branch a run creates. NexusOne generates the rest.
>         The default is `nx1/`.
>       * **Max files**: The most files a run might change, from 1 to 50. The default is 5.
>       * **Max lines**: The most lines a run might change, from 1 to 5000. The default is 200.
>       * **Open a pull request once approved**: Lets the crew store a patch, which NexusOne pushes after a
>         reviewer approves it. This is on by default.
>       * **Comment on a pull request**: Lets the crew comment on a pull request. This is off by default.
>
> 13. Click **Save**. NexusOne shows **Crew created**, and the crew stays open on the canvas.

> [tab] REST API
>
> Use the [Create template](https://docs.nx1cloud.com/api-reference/endpoints/crew-templates/create-template.md) endpoint to create a crew.

## Additional resources

For a high-level overview of crews and how they're used in NexusOne, refer to
[Crews](https://docs.nx1cloud.com/documentation/agents/overview/crews.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.