Invite your leads

Briefs follow your org chart: who reports to whom decides which Briefs exist and who reviews them. Waltz keeps two lists:

• People are your org's directory: names, titles, levels, managers and teams. They need no Waltz account.
• Members are accounts that sign in to the console.

Add your people

Under People, choose Import CSV. One row per person under a header row; columns in any order, names case-insensitive. UTF-8, up to 5,000 people.

Column	Required	Meaning
email	yes	Unique in the file; how a later import matches people
name	yes	Display name
title	no	Job title
level	no	ic (default), tl, em, director, vp, cto, ceo or pm
manager_email	no	A person in the same file; empty for exactly one person, the root
team	no	One team per row
github_login	no	Their GitHub login
repos	no	Repos the team owns, owner/repo, separated by ;

email,name,title,level,manager_email,team,github_login,repos
cto@acme.test,Ana Ruiz,CTO,cto,,Engineering,,
em@acme.test,Ben Ode,Engineering Manager,em,cto@acme.test,Payments,bode,acme/payments;acme/ledger
dev@acme.test,Cy Lin,Software Engineer,ic,em@acme.test,Payments,,

• Teams come from the rows. A person at em, director, vp, cto or ceo leads the team on their row. A team sits under the team of the nearest manager above its lead.
• Waltz checks the whole file first and lists every problem by row and column: a duplicate address, an unknown level, a manager not in the file, a reporting loop, more than one root.
• You preview the difference (people and teams added, changed and removed) before applying it.
• The file is the whole chart. People missing from it are marked removed, and console edits to people it names are overwritten. Importing the same file again does nothing.

Edit the hierarchy

People shows your teams as a tree. Admins edit a person's name, title, level, GitHub login and manager, and a team's name, lead, repos and place in the tree (Move to). Waltz refuses any change that would make a reporting loop.

Review identities

Commits, pull requests and agent sessions name people differently. Waltz links them to one person:

• An exact email match links on its own, including GitHub's noreply addresses.
• Weaker evidence, such as an identity that appears on the same changes as a known person, only suggests. Its confidence says how sure Waltz is about the identity, never anything about the person.

Identities holds the queue: Suggestions (most confident first), Unmatched, Not people and Unlinked. Confirm or reject a suggestion, link by hand, or mark a bot or service account as not a person. Waltz never overrides an admin's decision. Bots never count as seats.

Invite members

Under Settings → Members, choose Invite someone. They join when they sign in with that address within 14 days.

Role	Can
Owner	Everything an admin can, plus billing and granting owner
Admin	Integrations, repos, people, identities and Brief subscriptions
Member	React, comment, correct and record decisions on Briefs; connect the CLI; make MCP tokens
Viewer	Read

Brief recipients don't need to be members: a subscription sends to email addresses. People who only read Briefs are not seats.

Give each lead their Brief

With your chart in, an admin chooses Give each lead their Brief on the overview's checklist:

• each team led by an engineering manager or tech lead that owns an included repo gets the weekly EM Brief;
• each team led by a director or VP, with teams under it, gets the weekly VP Brief, on Wednesdays;
• the root lead gets the monthly exec Brief.

Types your plan doesn't include are skipped and listed; running it again leaves existing subscriptions alone. Change recipients, timing and delivery on each subscription under Briefs.

Each Brief is reviewed by its audience. Next: Read your first Brief.