> Source: https://builder.ema.ai/v2/groups/with-autopilot
> Title: Doing All of This with Autopilot

# Doing All of This with Autopilot

Every action in this section has a form in the interface, and none of them require it. Autopilot can create teams and groups, staff them, change roles, nest one team inside another, and archive and restore, from a plain-language request.

This is usually the faster path. One sentence can do what several forms do, and Autopilot applies the same rules the interface applies, so it refuses the same things for the same reasons.

## What to say

Describe the outcome. There is no syntax to learn and no need to name a tool.

What you want

What to say

Create several teams at once

"Create three teams: Support Team, Tier 2 Escalations, and Finance."

Create a group rather than a team

"Create a group called Customer Support with the description Front-line support for customer questions."

Nest one team inside another

"Nest Tier 2 Escalations under Support Team with member access."

Staff a group

"Add Maya as admin and Devon as builder of Customer Support."

Change somebody's role

"Make Priya an admin of Tier 2 Escalations."

See who really has access

"Who are the effective members of Customer Support?"

Archive and restore

"Archive the Finance team." / "Restore Finance."

Say "team" or "group" and Autopilot uses that literally, because the two are different things that cannot be converted later. If you say "team" it creates a list of people. If you say "group" it creates a container that can own AI Employees and knowledge bases. See [Groups and Teams](/builder/v2/groups).

## Creating several teams in one request

Ask for three teams and a nesting link, and Autopilot creates all three in parallel, then adds the nesting.

![Autopilot creating three teams in one request, then nesting one under another](/builder/v2/assets/img/03-groups/autopilot-creates-teams.png)

Autopilot creating three teams in one request, then nesting one under another

It reports what it did in the same terms the interface uses: each team created with you as its first admin, and the nesting described by what it changes about access.

## Creating groups

The same request shape creates groups. Autopilot confirms the type it used, because the choice is permanent.

![Autopilot creating two groups and nesting a team into one of them](/builder/v2/assets/img/03-groups/autopilot-creates-groups.png)

Autopilot creating two groups and nesting a team into one of them

## Staffing in one step

Give it the whole staffing plan in one sentence per group and it resolves the people, then applies every assignment together.

![Autopilot adding seven people across three groups in one request](/builder/v2/assets/img/03-groups/autopilot-staffs-members.png)

Autopilot adding seven people across three groups in one request

## The rules still apply

Autopilot is held to the same rules as the forms. It can only do what your role allows, and it will not remove or demote a team's only admin. See [Teams](/builder/v2/groups/teams#roles-inside-a-team).

## What's next

-   [Teams](/builder/v2/groups/teams) for the same operations through the interface.
-   [Groups](/builder/v2/groups/groups) for the group page.
-   [Autopilot](/builder/v2/autopilot) for what Autopilot does across the rest of the platform.