Skip to main content

Updated Oct 6, 2026

Open in ClaudeOpen in ChatGPT

Shared teams

Shared teams are groups of workspace users you define in FunnelStory. When an account’s data includes a matching team identifier, every member of that team can be auto-assigned to the account after an Account model refresh—useful when portfolios are owned by pods or regions rather than a single CSM. A team can also have managers, who get a view of their team's book of business on Focus Areas and Accounts.

This page is about Shared teams in Admin → Team. It is not the same as the Microsoft Teams data connection used for notifications and channels.

Where to configure teams​

  1. Open Admin Settings → Team Permissions.
  2. Use the tabs:
    • Team Members — workspace users, invites, roles, and designations (see Inviting users).
    • Shared Teams — create and manage named teams and their members.

Create a shared team​

On Shared Teams:

  1. Choose Create team.
  2. Set External Team ID — a stable string you will reuse in your Account model (for example portfolio-east or a value that already exists in your warehouse). This value cannot be changed after the team is created; pick something durable.
  3. Set Name and optional Description for humans reading the list.
  4. Add members (workspace users) to the team.

The External Team ID is what FunnelStory matches against the account property team_id (see Field reference).

Team managers​

Mark the people who lead a team as its managers. A manager can then switch Focus Areas and Accounts between their own accounts and their team's—without an admin building a filter for them.

To set managers:

  1. On Shared Teams, open the team's Actions menu and choose Manage Members.
  2. Select the team's members, then tick Manager for the people who manage it. Only selected members can be managers; removing someone from the team also removes them as manager.
  3. Click Save.

A team can have several managers, and a person can manage several teams.

What changes for a manager:

  • A scope picker on Focus Areas and Accounts. On Focus Areas it offers My book, My team (or My teams when they manage more than one) and each team they manage. On Accounts it also offers each member, and All accounts for roles that already see every account. See Focus Areas and Accounts View.
  • Access to their members' accounts. A manager whose role limits them to their own accounts (for example Account User) also sees the accounts assigned to the members of the teams they manage. This adds the members' assigned accounts only, not the accounts the members can see through CRM visibility.

Managers are still team members for everything else. In particular, team-based assignment (below) assigns a team's accounts to its managers too, so marking someone a manager doesn't change their assignments.

In your Account model, map a column or expression to the reserved property team_id. For each account row, the value must exactly match the shared team’s External Team ID (same spelling and casing as stored in FunnelStory).

  • If the value is empty or does not match any shared team, no team-based assignments are created from that property.
  • If it matches, on Account model refresh FunnelStory assigns every member of that team to the account.

Coexistence with CSM / AE properties: Role-based auto-assignment from fields like csm_email is separate. Both can apply to the same account when the model defines both.

Manual assignments: If someone is already manually assigned to an account, FunnelStory does not overwrite that with a team-based auto-assignment for the same user on that account.

When assignments update​

Team-based assignments are reconciled when the Account model runs its refresh (scheduled or manual Refresh model). After changing teams, members, or team_id values in your source data, run a refresh and spot-check assignments (see Verification).

Deleting a shared team​

Deleting a team removes the team definition from the workspace. Auto-assigned account memberships that came from that team are cleared on the next Account model refresh after deletion.