Share ad accounts with team members

Last updated: May 19, 2026

Share ad accounts with team members

By default, members see all ad accounts in the workspace based on their role. For granular per-account sharing (only certain users see certain ad accounts), create Teams inside the workspace at Settings → Team → Teams → assign ad accounts to teams → assign users to teams. Owners and admins always see all.

Who is this for

Admins at agencies with multiple clients in the same workspace, or in-house teams where different perf buyers handle different brands. Anyone needing per-ad-account access control beyond role-level.

Default behavior (no Teams)

If you don't create any Teams, the role-based default applies:

  • viewer / finance / mediabuyer / manager / admin / owner / super_admin: see all ad accounts in the workspace (read or edit based on role — see team-101)

This is fine for small in-house teams. For agencies and multi-client setups, you usually want granularity.

When to create Teams

Use Teams when:

  • An agency has 5+ clients in one workspace

  • Mediabuyers should only see their assigned client(s)' ad accounts

  • Compliance requires separation (one client cannot see another's data)

  • You want to delegate client management without sharing the whole agency view

Don't create Teams when:

  • You only have 1-3 ad accounts (overhead > benefit)

  • All teammates need full visibility

  • You'd be better served by separate workspaces (true data isolation between clients — see team-102)

How Teams work

A Team is a named grouping inside a workspace with:

  • A set of users assigned (via team_membership table — user_id + team_id + role)

  • A set of ad accounts assigned (each ad account can belong to multiple teams)

  • A scope: users in the team see only the ad accounts assigned to that team

Users can belong to multiple teams, accumulating visibility (union of all their teams' ad accounts).

Admins and owners always see all ad accounts regardless of Team membership.

How to create and use Teams

Step 1: Create a Team

Navigate to Settings → Team → Teams → Create team. Enter:

  • Team name (e.g. "Client A", "Brand X EU team")

  • Description (optional)

Step 2: Assign ad accounts to the team

Open the team → Ad accounts tab → Add ad account. Multi-select from your connected ad accounts (across all platforms). An ad account can be assigned to multiple teams.

Step 3: Add users to the team

Open the team → Members tab → Add member. Pick from existing workspace members. They inherit the team's ad-account access.

Step 4: Member sees only assigned ad accounts

Members of a team see, in Ads Manager / Dashboard / etc., only the ad accounts assigned to teams they belong to. If they belong to no team and have a non-admin role, they see no ad accounts until added to at least one team.

Combining Teams with roles

Teams don't replace roles — they layer on top. A user's effective access is:

effective_access = role_permissions ∩ team_ad_accounts

So a mediabuyer who is in Team A (containing Ad Account X) can edit campaigns on Ad Account X (mediabuyer can edit) but cannot connect new ad accounts (mediabuyer can't connect, regardless of Team).

Adding a viewer to Team A makes them able to see Ad Account X (viewer can see), not edit.

Common patterns

Pattern A: Agency with separate buyers per client

  • Teams: "Client A", "Client B", "Client C"

  • Buyer 1: member of Team A only → sees Client A's ad accounts only

  • Buyer 2: member of Teams B + C → sees both clients' ad accounts

  • Account manager: admin role → sees all

Pattern B: Brand with regional teams

  • Teams: "EU team", "US team", "APAC team"

  • EU buyer in "EU team" → sees only EU ad accounts

  • US buyer in "US team" → sees only US ad accounts

  • Global perf lead: admin role → sees all

Pattern C: Project-based contractors

  • Team: "Q4-2026 launch project"

  • Add contractor with mediabuyer role

  • At project end: remove them from the team (or remove from workspace entirely)

  • Frees the seat + revokes ad-account access

What you'll see

In the Teams section:

  • A list of all teams in the workspace

  • Per team: member count, ad-account count, created date

  • Click any team → detail view with two tabs (Members, Ad accounts)

  • Action menu per row: rename, delete team, export members CSV

In Ads Manager / Dashboard:

  • Members see a filtered view based on their Team memberships

  • Admin badge in the workspace switcher confirms "full visibility" if you have it

Removing users from a team

Two ways:

  1. Open the team → Members tab → action menu → Remove from team: removes only from this team. User keeps workspace membership; loses access to this team's ad accounts.

  2. Remove from workspace entirely (team-107): removes from all teams + workspace.

Removing ad accounts from a team

Open the team → Ad accounts tab → action menu on the ad account row → Remove from team. Members lose access immediately (they may need to refresh).

Limits

  • Number of teams per workspace: no hard cap on most plans; performance-tested up to 50+ teams

  • Users per team: no cap

  • Ad accounts per team: no cap

  • Teams per user: no cap

If you have hundreds of teams, consider whether the structure should be multiple workspaces instead.

Common issues

  • Mediabuyer doesn't see any ad accounts: they're not in any team. Either add to teams or upgrade their role to admin/owner.

  • Member sees ad accounts I didn't add: they're in another team that includes those. Check all team memberships.

  • Cannot remove the last user from a team: empty teams are allowed — the constraint is just "don't delete a team while it has unique-owner assignments". You can remove all users; the team persists.

  • Deleted a team but ad accounts still associated with members: refresh; the cache may take 30s to clear.

  • Want to clone team structure: not supported in UI. Use CSV export of memberships from one team + bulk-add to a new team.

Related