Teams are how you carve up visibility inside an Aggrandize org. Once you grow past a small group sharing one shared pipeline, you'll usually want different parts of the org to see different parts of the data — Commercial doesn't need to wade through Civil/Infrastructure deals, and most reps shouldn't have access to a privileged executive pipeline. Teams make that scoping explicit.

Where to find it

Open Settings → Teams. Like Pipeline Settings, this page is Owner and Admin only. Members never see the Teams card in Settings.

Each team card shows the team's name, a short description, the member count, and an expand toggle that reveals the team's roster. Cards are sorted alphabetically. The empty state — no teams created yet — shows a single Create Team call to action.

What a team controls

The team a record is assigned to determines who can see and edit it. The rules apply uniformly to contacts, companies, deals, and pipelines:

• Org-wide (no team) — visible to every member of the organization. This is the default for new records.
• Assigned to a team — visible only to that team's members, plus all Owners and Admins.
• Private (personal team) — visible only to you. Useful for personal prospect lists, half-formed ideas, or anything you're not ready to share with the org yet.

Owners and Admins always see everything, regardless of which team owns a record. Team scoping is a sharing tool for members, not a wall against admins.

Creating a team

Click New Team in the top-right. The dialog asks for just two things:

• Team Name — required (e.g., Commercial, Public Bids, Northeast Region)
• Description — short blurb that appears under the team name in the list

That's the entire form. No member picker, no permission switches — once the team exists, you add members and assign records from elsewhere.

Adding and removing members

Click any team card to expand it. The body switches to a member list with an Add Member affordance:

Click Add Member and the search box lets you find anyone in the org who isn't already on this team. Picking someone adds them immediately — no email, no invite — because they're already in the org.

A person can belong to multiple teams. Sarah might be on both Commercial and Civil/Infrastructure if she splits her time. Their effective visibility is the union — they see every record assigned to any of their teams, plus everything Org-wide.

To remove someone, hover their row and click the X at the end. Removal is instant; their CRM access elsewhere is unaffected, but they immediately stop seeing records scoped to that team.

Editing, archiving, and deleting

The three-dot menu on a team card has three actions:

• Edit Team — change the name or description. No effect on assignments.
• Archive Team — soft-hides the team. Existing records keep their team_id (they still belong to the archived team), and Owners/Admins can still see them, but the team disappears from the Team Selector dropdown elsewhere in the app. Use this when a reorg happens and you want to retire a team without losing its history.
• Delete Team — permanently removes the team. Only enabled when the team has zero members. When a team still has members, the menu reads "Remove all members to delete" — strip the roster first, then come back.

Archived teams collect at the bottom of the page under a collapsible Archived Teams section. You can restore one from its three-dot menu and it returns to the main list.

Assigning records to a team

Teams only matter once records are scoped to them. Every contact, company, deal, and pipeline has a Team Access picker — the same UI everywhere:

Three buckets show up at the top of the dropdown:

• Org-wide (globe icon) — the default. Anyone in the org can see this record.
• Private (amber lock) — visible only to you. The first time a member picks Private, the app auto-creates their personal team behind the scenes; you don't need to set it up in advance. Private items can be reassigned to a real team later — there's no penalty for parking a draft contact in Private while you decide.
• Your real teams — anything created on the Teams page lists below the divider.

You'll see this picker:

• Contacts — in the Contact form, and on the Contact detail page in the right rail
• Companies — same pattern
• Deals — in the Deal form
• Pipelines — as Team Access on the Pipeline form. When a pipeline is team-scoped, every deal on it inherits the scope — non-members of that team can't see those deals at all, even if a particular deal is itself Org-wide.

How teams interact with the AI assistant

When the AI assistant queries contacts, companies, or deals on your behalf, it sees what you see. That means:

• A member on the Commercial team can ask "how many open deals do I have?" and the assistant counts only deals visible to them — Org-wide deals plus Commercial-team deals. Civil/Infrastructure deals don't leak in.
• The Owner/Admin always-see-everything rule applies to assistant queries too. An Owner asking "show me last quarter's pipeline" gets the full picture, regardless of team scoping.
• If you'd rather scope an assistant question to a single team, mention the team by name: "summarize the Civil/Infrastructure pipeline."

This is one of the main reasons teams matter for orgs that have grown past a handful of people — the assistant becomes much more useful when its answers are filtered down to what the asker actually owns.

Patterns we see in the field

• By construction segment. Commercial, Civil/Infrastructure, Residential, Public Bids — each team works a distinct kind of project and shouldn't be distracted by the others' deals. Pipelines tend to differ by segment too, so team-scoping pipelines reinforces the separation.
• By geography. Northeast, Southeast, Midwest, West — useful when reps own a region and shouldn't be pinging contacts in someone else's territory. Pair with company location fields and the relationship graph for a clean territorial view.
• By function. A small Executive team that only sees the top-dollar deals; a Channel Partnerships team that owns the partner relationships. Both work well as team-scoped pipelines feeding team-scoped dashboards.
• Solo with Private. Even in a one-person org, Private records are useful for prospect lists or half-formed deals you're not ready to share. When you grow and bring in a partner, you reassign the ones worth keeping to Org-wide or to a team.

Who can manage teams?

Creating, editing, archiving, deleting teams, and adding or removing members is Owner and Admin only. Members can be assigned to teams (it's how they get visibility), and they can read the Team Selector on records they're editing, but they can't reshape the team structure itself.

If you're rolling Aggrandize out for the first time, you don't have to set teams up on day one — leave everything Org-wide for a couple of weeks, watch how your team actually works, then come back and carve up the world once the seams are obvious.