Workspace, Team, Account — what's the difference

Last updated: May 19, 2026

Workspace, Team, Account — what's the difference

Wevion has a 3-tier hierarchy: Organization (billing scope) > Workspace (project or brand boundary) > Team (people grouping inside a workspace). Your personal Account is your individual user that can belong to many workspaces.

Who is this for

Anyone choosing how to structure Wevion for their company — especially admins setting up for the first time and agencies onboarding clients.

The 3 tiers

Organization

The top-level container. One Organization = one billing entity. It owns:

  • The subscription plan (Starter, Pro, Enterprise — see trial to paid)

  • Payment method and invoices

  • Seat pool shared across all workspaces

  • Single Sign-On configuration (Enterprise only)

  • Cross-workspace RBAC for super admins

Typical setup: one Org per legal entity. An agency has one Org. A holding with three independent brands also has one Org but three Workspaces.

Workspace

The project or brand boundary. One Workspace contains its own:

  • Connected ad accounts (Meta, Google, TikTok, ...)

  • Campaigns, ad sets, ads, creatives

  • Rules and automation

  • Reports and dashboards

  • Team members and roles

  • Workspace defaults (currency, timezone)

Data is fully isolated between workspaces. A user with access to Workspace A cannot see Workspace B unless explicitly added. Switching between workspaces happens from the workspace switcher in the header.

Typical setup:

Scenario

Suggested structure

In-house team, single brand

1 Org + 1 Workspace

In-house team, multiple brands

1 Org + 1 Workspace per brand

Agency, client work

1 Org + 1 Workspace per client

Holding with subsidiaries

1 Org per subsidiary (separate billing), or 1 Org + 1 Workspace per subsidiary (shared billing)

Team

A grouping of users inside a Workspace. Used to bundle permissions for ad accounts: "Creative team can edit creatives in any campaign", "Performance team can edit budgets". A Team is not a separate billing or data boundary — it's a permissions shortcut.

You can run a Workspace without ever creating a Team (assign roles directly to people). Teams help when you have 10+ members and recurring permission patterns.

Personal Account vs Workspace membership

Your personal account is your user identity: email, password, profile, 2FA, language. It lives at /settings/personal/*.

You can belong to many workspaces simultaneously. The workspace switcher shows your role in each. Roles are per-workspace — you can be Owner in one and Viewer in another.

How invitations work

  • An admin in a Workspace invites you by email

  • You receive an invite link valid 14 days

  • Clicking the link adds your existing account to that workspace (or creates one if you don't have one yet)

  • You appear in Settings → Team → People of that workspace

  • Your role in that workspace is set at invite time and editable later

See Invite your first team member for the admin-side walkthrough.

Roles at a glance

7 roles, ordered by power:

Role

Typical use

super_admin

Org-level platform admin (rare)

admin

Workspace lead, full control of that workspace

owner

Owns billing within a workspace (one per workspace usually)

manager

Day-to-day campaign manager

mediabuyer

Launches and edits campaigns

finance

Read-only on performance, full on billing

viewer

Read-only across the workspace

Full role-by-role permission breakdown in Roles and permissions in 5 minutes.

Seats and billing

Seats are per-Organization, shared across workspaces. The plan you pick (see from trial to paid plan) sets the seat ceiling. Adding the same user to 3 workspaces still counts as 1 seat. Deleting a user from all workspaces frees the seat for someone else.

How to set this up

  1. After signing up you automatically have 1 Org + 1 Workspace (named after your business name)

  2. Decide if you need more workspaces. Create new workspaces from Settings → Workspaces → New Workspace (admin only)

  3. Invite people into each workspace with the role they need

  4. Optionally create Teams to bundle ad-account permissions

Common questions

  • Can I move data between workspaces? No. Workspaces are isolated. Set up the right structure before importing.

  • Can I be a Viewer in my own workspace? Yes, but you'd lock yourself out of admin actions. Keep at least one Owner per workspace.

  • Does deleting a workspace cancel my subscription? No — subscriptions live at the Organization level. Deleting workspaces only removes the data inside.

  • What happens to a user when I delete a workspace? Their access to that workspace ends. They keep their account and any access to other workspaces.

Related