Teams
For big jobs, one assistant can lead a team of specialists — a crew where a lead delegates steps to members, each holding only the access its role needs. This is how Aivyx PA tackles work that’s too broad or too sensitive for a single agent.
How a team works
A team is a lead plus up to eight specialists — nine members in all, which is where the built-in team’s name, the Nonagon, comes from. Each member has:
- a role (what it’s responsible for),
- a character (how it approaches its work),
- a tightly scoped set of tools and permissions — only what its job requires.
The lead receives the goal, breaks it into steps, delegates each step to the best-fit specialist, checks their work, and assembles the result. Specialists can’t reach beyond their lane — a member that only logs records, for example, physically cannot send a message or spend money.
Why the scoping matters
This is least-privilege by design. Even inside an autonomous job, the consequential actions are confined to the one member authorized for them, and that member still hits an approval gate for anything irreversible. A team multiplies what your assistant can take on without multiplying what can go wrong.
The Teams screen
The Teams screen shows your active team — the lead and each specialist, their roles, what they’re trusted to do, and the tools they hold. You can also edit the roster here: adjust roles, characters, and scopes, within the nine-member limit. Each member can even use its own model.
Vertical packs
A team can be tailored to a domain. Aivyx PA ships an example — a back-of-house kitchen crew (a manager leading stocktake, inventory, purchasing, and food-safety specialists) — that shows how a team plus a set of domain tools becomes a ready-made expert crew for a specific line of work. These domain bundles are called vertical packs; more can be added without changing the core assistant.