Nuggetz is built around teams. Colleagues are the players: they own Nuggets, make decisions, and bring the agents they already use. Everyone sees the same workflows and shares the same Review Inbox, so the work and the judgment behind it stay in one place.
If you're new to nuggets and workflows, read Workflows & nuggets first.
Inviting teammates
The fastest way to invite someone is to make them an owner. Whenever you type an owner name that isn't on the team yet — while adding or editing a nugget — the form tells you right there and asks for their email. Save the nugget and the invite goes out in the same step. They get an email naming the exact nugget they now own, and the link drops them straight onto it — not a generic dashboard.
The same one-click invite appears in two more places (for admins):
- A banner at the top of a workflow whose owners aren't all on the team yet — one invite button per missing owner. This covers workflows Chef built for you, where it named owners from your description.
- An invite chip next to the owner's name when you open a nugget.
Invitees join as editors with their nugget waiting for them.
You can also invite people the classic way, without tying them to a nugget:
- Open the team switcher at the top of the sidebar.
- Choose Manage (or Manage organization) to open team settings.
- Go to Members and click Invite.
- Enter the person's email and pick a role.
- Send the invite. They get an email and join once they accept.
To start a brand new team instead, open the team switcher and choose Create team. You become its admin, and Nuggetz drops you into the welcome flow to pick a starter workflow.
Use the same switcher to move between teams. The app reloads to show that team's workflows.
Roles
Nuggetz has two roles. You set a person's role when you invite them, and you can change it later from Members.
| Role | What they can do |
|---|---|
| Admin | Everything an editor can do, plus team settings, member management, and invites. |
| Editor | Create and edit workflows, Nuggets, and corrections. Resolve runs in the Review Inbox. View registered-agent health for the team's agents. |
Most people who build and run workflows only need the editor role. Keep admin for the people who manage the team itself.
Owners on nuggets
Every nugget has an owner, the person accountable for that step. The owner stays the same whether a person does the work by hand or an agent runs it Autonomously. Owning a nugget means:
- You decide when it's ready to promote toward Autonomous, and you can demote it any time.
- Runs that need a human land in your view of the Review Inbox.
- You're the person the rest of the team looks to when that step needs a call.
Set owners as you build a workflow so it is always clear who is accountable, even for steps run with an agent. The fastest everyday action is Run with…: the owner picks a personal Codex or Claude Code connection, or an always-on team agent, continues the work there, and brings the result back to the shared workflow.
How the Review Inbox routes judgment
When an agent isn't sure it got a run right, it flags the run for review instead of guessing. Those runs, along with any upgrades agents propose, collect in the Review Inbox at /team/{teamId}/inbox.
The inbox is where a person applies judgment:
- Approve a run to accept it as-is.
- Correct or reject it to say what should have happened instead. Either action captures one correction, a short note the agent can act on next time.
- Approve or reject an agent's proposal to change a nugget. Nothing an agent proposes applies on its own.
Anyone with the editor or admin role can resolve items. Runs surface to the nugget's owner first, but the whole team can pitch in when the queue is busy.
The Nugget keeps the team's learning
A correction attaches to the workflow, not to the agent that triggered it. That matters:
- It applies no matter which agent runs the nugget next.
- It survives when you swap agents or add new ones.
- It's visible to the whole team in the Nugget's History, beside the run and configuration version it affected.
So the guidance your team builds up stays with the work. History also shows before/after configuration changes, making it clear how the definition of done and instructions evolved. New teammates and new agents inherit the current version without anyone re-explaining it.
Next steps
- Workflows & nuggets: how nuggets, stages, and definitions of done work
- Connecting your agents: run Assisted and Autonomous Nuggets and handle the review cycle