Understanding Meta users and Business Manager roles

Last updated: May 19, 2026

Understanding Meta users and Business Manager roles

A Meta user in Wevion = the Facebook account that authenticated. Multiple teammates can each connect their own Meta user → Wevion sees the union of all their Meta BM permissions. Manage at /settings/personal/connected-accounts (your own) or /connect/meta → Meta users (workspace view, admin only).

Who is this for

Mediabuyers troubleshooting "why don't I see ad account X" issues, admins planning the right Meta access strategy for the team, anyone managing Meta-side permissions.

The Meta user model

When you connect Meta, Wevion stores:

  • Meta user record (meta_user model) — the Facebook account ID + display name + OAuth token (encrypted)

  • Meta ad accounts linked to this Meta user (whatever the Meta user can access in Meta BM)

  • Meta fan pages linked to this Meta user

One Wevion teammate = one Meta user record per connection. If a teammate connects again later (token refresh, switch FB account), Wevion updates the existing record.

Multiple Meta users per workspace

Different teammates can each connect their own Meta user. Common pattern:

Teammate

Their Meta BM access

Wevion gains

Sara (head of marketing)

Admin in BM-Client-A and BM-Client-B

All accounts of A + B

Luca (mediabuyer)

Advertiser in BM-Client-A only

Already covered by Sara

Anna (client mediabuyer)

Admin in BM-Client-C (not Sara's BMs)

Adds Client-C accounts

Result: workspace sees ad accounts of A, B, and C — union of all teammates' Meta BM access.

This is useful when no single Meta user has access to everything.

Why connect multiple Meta users

  • Single user lacks access: agency where the client-specific BM admin is the client themselves

  • Distributed responsibility: each teammate manages their own clients

  • Backup: if Sara's Meta token expires and she's on vacation, Luca's connection still keeps the BM-A accounts syncing

  • Compliance: each Meta user's actions are audited separately

Meta Business Manager roles vs Wevion roles

Two different role systems:

System

Roles

Where set

Wevion

super_admin, admin, owner, manager, mediabuyer, finance, viewer

In Wevion (Settings → Team → People)

Meta BM

Admin, Advertiser, Analyst (BM level) + Admin, Editor, Advertiser, Analyst (per ad account)

In Meta Business Manager

A user can be Wevion admin but only Meta Advertiser on a given ad account — they can launch ads via Wevion (Meta-level permission), but can't change BM settings (Meta-level limit). Wevion respects both layers.

What each Meta BM role enables in Wevion

Meta BM role on ad account

What Wevion can do

Admin

All: launch, edit, pause, delete, change billing

Advertiser

Launch, edit, pause; no billing or BM settings

Analyst

Read-only — view performance only

(no role)

Account not visible in Wevion

If a teammate has only Analyst access on an ad account, Wevion shows that account as read-only with a tooltip.

Manage your own Meta connections

At /settings/personal/connected-accounts (or via the Connect page), you see:

  • Each Meta user you've connected

  • Last refresh time

  • Status: Active / Token expiring / Disconnected

  • Reconnect button (forces re-OAuth — see meta-107)

  • Disconnect button (revokes the token + removes the Meta user record from your workspace)

Admin view of all Meta users in workspace

Admins/owners can see all Meta users connected by any teammate at /connect/meta → Meta users tab:

Column

What

Wevion user

The teammate who connected

Meta user

The Facebook account they authenticated with

Connected at

When

Last refresh

Last successful token refresh

Status

Healthy / Token expiring / Disconnected

Accounts

How many ad accounts this Meta user contributes

Pages

How many Pages this Meta user contributes

Admin can force-disconnect any Meta user (e.g. when removing a teammate from the workspace).

When a teammate leaves the workspace

If you remove a teammate (team-107) who had connected Meta users:

  • Their Meta tokens are revoked (Wevion stops syncing data via their tokens)

  • Ad accounts they were the only source for: marked Disconnected (need re-import via another teammate)

  • Ad accounts also accessible via other teammates: continue syncing via those other teammates

The "Also revoke their API keys + Meta tokens" checkbox in the Remove member flow handles this cleanly.

Best practices

  • At least 2 Meta users per critical ad account: redundancy against single-token failure

  • Use Meta Business Manager admin roles sparingly: most teammates should be Advertiser (sufficient for ad management without governance)

  • Audit quarterly: review the Meta users list, disconnect ones from former teammates, re-attribute critical accounts

  • Don't share Facebook accounts: each teammate connects their own personal/work FB. Shared accounts break audit + 2FA + offboarding

Common issues

  • Account visible to one teammate, not another: that teammate's Meta user lacks role on it. Either upgrade their Meta BM role or have a different teammate cover that account.

  • "All my accounts disappeared!": your Meta token expired and didn't auto-refresh. Reconnect.

  • Connected Meta user shows wrong name: Facebook display name changed. Reconnect to update.

  • Conflict: two Meta users see the same account, with different roles: Wevion uses the highest role for permission decisions (e.g. if one user is Admin and another is Advertiser on the same account, Wevion treats it as Admin).

  • Cannot disconnect Meta user as workspace admin: a teammate's Meta user can only be disconnected by that teammate OR by removing the teammate from the workspace.

Related