Workspace, Team, Account — what's the difference
Wevion has a 2-level model: Organization > Workspace. Teams are people groups granted Workspace access. Here's what each holds and when to use them.
Written By Salvatore Sinigaglia
Last updated 8 days ago
Wevion has a 2-level model: Organization > Workspace. Teams are people groups granted Workspace access. Here's what each holds and when to use them.
Workspace, Team, Account — what's the difference
Wevion has a 2-level hierarchy: Organization (top container — billing, seats, AI credits) > Workspace (project or brand boundary holding your data). A Team is a group of people under the Organization, granted access to one or more Workspaces with a role. 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 building blocks
Organization
The top-level container. It owns:
- Organization membership and roles — every person has an Org role:
owner,admin, ormember - Billing: the subscription plan (Starter, Pro, PLUS; Enterprise is negotiated separately — see trial to paid), payment method, and invoices — one subscription per Organization, shared by all its Workspaces
- Seats — the seat cap is one pool counted per Organization (see Seats and billing below)
- Credit balance for AI features — one organization-wide pool
Enterprise capabilities such as SSO/SAML, SCIM provisioning, and SLAs are available on request as a dedicated configuration set up with Sales — they aren't self-serve toggles in the app.
Typical setup: one Org per company. An agency has one Org. A holding with three independent brands also has one Org but three Workspaces.
Workspace
The project or brand boundary — the container you switch between with the scope switcher. One Workspace contains its own:
- Connected ad accounts (Meta, Google, TikTok, ...)
- Campaigns, ad sets, ads, creatives
- Stores and trackers
- Rules and automation
- Reports and dashboards
- Members and roles
- Workspace defaults (dashboard preset/profile, hub layout, member policy flags, conversion source)
Data is fully isolated between workspaces. A user with access to Workspace A cannot see Workspace B unless explicitly added. Owners and admins can create additional workspaces self-serve at Settings → RBAC → Workspaces (/settings/rbac/workspaces), up to the plan's workspace quota — see Navigating Wevion for how workspaces fit into the app.
Typical setup:
Team
A group of users under the Organization — not a billing or data boundary. A Team is granted access to one or more Workspaces, each grant carrying a role (manager, mediabuyer, finance, or viewer): everyone in the Team gets that role in the granted Workspace(s). Teams do not scope individual ad accounts — access is per-Workspace.
Access to a Workspace always comes through a Team — there is no "add a member directly to a Workspace" anymore. A person joins a Team, the Team is linked to one or more Workspaces, and each person inherits, on those Workspaces, the role they hold in their Team. When someone's Teams grant overlapping access to the same Workspace, the highest Team role wins. Organization owner/admin roles are the exception: they carry admin-level access across all Workspaces in the Org without needing a Team; an Org member only gets Workspace access through Team membership.
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 Teams and reach many Workspaces at once. Your effective role on a Workspace is the highest role among your Teams linked to it — so you can be a manager on one Workspace and a viewer on another, depending on your Team memberships.
How invitations work
- An Org
owner/admininvites you by email and places you in a Team - You receive an invite link valid 7 days
- Clicking the link adds your existing account to the Organization (or creates one if you don't have one yet)
- Your Team's role applies on every Workspace that Team is linked to
- You appear in the Members tab of that Team, under Settings → RBAC → Teams
See Invite your first team member for the admin-side walkthrough.
Roles at a glance
Wevion uses a two-tier role model — Organization roles and Team roles are separate vocabularies:
owner/admin/member are Organization roles, not Workspace roles. The role you hold on a Workspace is a Team role (manager/mediabuyer/finance/viewer). (super_admin is not a role you assign — it's an internal platform-staff bypass.) Full breakdown in Roles and permissions in 5 minutes; authoritative source: docs/architecture/RBAC-HIERARCHY.md.
Seats and billing
Billing and the seat cap live on the Organization — the seat check is enforced per Organization at invite time, as a single pool shared across all its Workspaces. The plan you pick (see from trial to paid plan) sets the seat ceiling and the workspace quota for the whole Organization.
How to set this up
- After signing up you automatically have 1 Org + 1 Workspace (billing lives on the Org)
- If you need more workspaces (agencies, holding companies), create them self-serve at Settings → RBAC → Workspaces, up to your plan's workspace quota
- Create Teams (Settings → RBAC → Teams) and link each Team to the Workspaces it should reach
- Invite people into the right Team — they inherit that Team's role on every linked Workspace
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. The subscription lives on the Organization and covers all its workspaces. To stop billing, cancel the subscription itself — see from trial to paid plan.
- 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.
FAQ
What's the difference between an Organization, a Workspace, and a Team in Wevion?
Wevion uses a two-level hierarchy: the Organization is the top container holding billing (subscription, payment method, seats) and the AI credit balance; a Workspace is a project or brand boundary holding connected ad accounts, campaigns, rules, and reports. A Team is a group of people under the Organization, granted access to one or more Workspaces with a role.
How are Wevion seats counted across workspaces?
Billing and the seat cap live on the Organization, and the plan you pick sets the Organization's seat ceiling, enforced at invite time — seats are one pool shared across all the Organization's Workspaces. Deleting a user frees a seat.
Can one person belong to multiple Wevion workspaces?
Yes. Your personal account can belong to many Teams and reach many Workspaces simultaneously. Your effective role on a Workspace is the highest role among your Teams linked to it, so you can be a manager on one Workspace and a viewer on another. Data is fully isolated, so you always act within one workspace's accounts at a time.
Do I have to create a Team to use a workspace?
Yes — access to a Workspace comes through a Team. A person joins a Team, the Team is linked to Workspaces, and the person inherits that Team's role on those Workspaces. (Organization owner/admin are the exception: they have admin access across all Workspaces without a Team.) There is no "add a member directly to a Workspace".
How many roles does Wevion have?
Wevion uses a two-tier model. Organization roles — owner, admin, member — describe your role in the Org. Team roles — manager, mediabuyer, finance, viewer — describe your role inside a people group and are inherited on the Workspaces that Team is linked to. super_admin is an internal platform-staff bypass, not an assignable role. The full breakdown lives in Roles and permissions in 5 minutes; authoritative source: docs/architecture/RBAC-HIERARCHY.md.
FAQ
What's the difference between an Organization, a Workspace, and a Team in Wevion?
Wevion uses a two-level hierarchy: the Organization is the top container holding billing (subscription, payment method, seats) and the AI credit balance; a Workspace is a project or brand boundary holding connected ad accounts, campaigns, rules, and reports. A Team is a group of people under the Organization, granted access to one or more Workspaces with a role.
How are Wevion seats counted across workspaces?
Billing and the seat cap live on the Organization, and the plan you pick sets the Organization's seat ceiling, enforced at invite time — seats are one pool shared across all the Organization's Workspaces. Deleting a user frees a seat.
Can one person belong to multiple Wevion workspaces?
Yes. Your personal account can belong to many Teams and reach many Workspaces simultaneously. Your effective role on a Workspace is the highest role among your Teams linked to it, so you can be a manager on one Workspace and a viewer on another. Data is fully isolated, so you always act within one workspace's accounts at a time.
Do I have to create a Team to use a workspace?
Yes — access to a Workspace comes through a Team. A person joins a Team, the Team is linked to Workspaces, and the person inherits that Team's role on those Workspaces. (Organization owner/admin are the exception: they have admin access across all Workspaces without a Team.) There is no "add a member directly to a Workspace".
How many roles does Wevion have?
Wevion uses a two-tier model. Organization roles — owner, admin, member — describe your role in the Org. Team roles — manager, mediabuyer, finance, viewer — describe your role inside a people group and are inherited on the Workspaces that Team is linked to. super_admin is an internal platform-staff bypass, not an assignable role. The full breakdown lives in Roles and permissions in 5 minutes; authoritative source: docs/architecture/RBAC-HIERARCHY.md.
Last updated: 2026-07-07
Related articles
Was this helpful?
Still need help? Ask the team