Skip to main content

Account Roles and Project Roles

Ensure that each member on your Vev account has appropriate access to features and permissions needed to perform their tasks effectively.

Iselin Ekornes avatar
Written by Iselin Ekornes
Updated this week

Understanding Roles in Vev

Vev uses two distinct role systems to manage permissions:

  • Account Roles: Determine what members can manage across your entire account, including subscriptions, hosting, and editor access

  • Project Roles: Define what members and guests can do within specific projects

Account Roles Overview

Account roles control administrative permissions and access levels across your entire Vev account.

Available Account Roles:

Owner

  • Automatically assigned to the person who creates the account

  • Has access to all account features and settings

  • Can manage all projects except draft projects (which are personal to individual members)

  • Note: To transfer account ownership, contact Vev Support for assistance

Admin

  • Has full administrative power similar to the Owner

  • Can manage users, hosting options, and integrations

  • Can access subscription and billing details

  • Has access to all editors

  • Can manage all account settings

Member

  • Can edit projects based on their assigned role

  • Has access to all features in your paid plan

  • Can create and edit projects

  • Can access specific teams, folders, and projects within them

  • Cannot manage account users, subscriptions, or billing

Specialized Roles (Organization Plan Only)

  • Designer: Has access to all editors

  • Content: Can access projects in folders from the Content Editor; in Drafts, can access projects from all editors

  • Developer: Has access to all editors

Managing Account Roles

How to Change a Member's Role

  1. Navigate to Account Settings

    • Click your account avatar in the sidebar

    • Select ⚙️ Settings from the dropdown menu

  2. Access Members Section

    • Click "Members" in the left navigation menu

  3. Edit Member Role

    • Hover over the member whose role you want to change

    • Click the edit (✏️) icon

    • Select a new role from the dropdown menu

    • Click "Save" to confirm changes

Only Account Owners and Admins can change roles.

Removing Users from Your Account

Removing Members

Steps to Remove a Member:

  1. Go to Account Settings

  2. Click "Users" in the left menu

  3. Locate the member and click the three-dot (⋮) menu next to their name

  4. Select "Remove user"

  5. Confirm the removal

What Happens When a Member is Removed:

  • They immediately lose access to the account

  • Their profile is moved to a Free account

Only Account Owners and Admins can remove members.


Removing Guests

Steps to Remove a Guest:

  1. Go to Account Settings

  2. Click "Guests" in the left menu

  3. Find the guest in the list and click the three-dot (⋮) menu

  4. Click "See details" to view their project access and permissions

  5. Click the trash bin icon to revoke access and confirm

What Happens When a Guest is Removed:

  • They immediately lose access to the project

  • If they try to access it, they'll see a "restricted access" message

If you prefer to remove a guest from within a project they have access to, you can do so from within the project itself.

Only Account Owners, Admins, and Project Owners (for guests in their projects) can remove guests.

What happens when a guest is removed?

  • They immediately lose access to the project.

  • If they try to access it, they’ll see a "restricted access" message.

Project Roles and Permissions

Project roles define what access and permissions users have within specific projects.

Project Owner

  • Automatically assigned to the person who creates the project (if they are an account member)

  • Can delete, duplicate, and move projects between teams or folders

  • Can change editing permissions and revoke project access

  • Can transfer project ownership to another user

  • Note: When external collaborators create projects, ownership is assigned to the account owner

  • Project ownership can be transferred to another user by the current owner.

Collaborators

Members

  • Users on your account who are not admins or owners

  • Have access to teams and/or folders where projects are located

  • Have full access to projects and can share them with others

Guests

  • External collaborators invited to work on specific projects

  • Have access to all project content and can use collaborative features

  • Guests must be invited to individual projects in order to view and edit them, and they can't be given folder or team access.

  • Are not full members of your account

Project Permissions for Guests

When inviting guests to projects, you can assign these permission levels:

Available on All Plans

  • View-only: Guests can view the project and leave comments, but cannot edit or publish

Available on Professional and Organization Plans

  • Guests can edit using all Vev editors and share the project, but cannot publish, embed, or manage integrations.

Note: To enable publishing rights, invitees must be added as members at the account level.

FAQs

Do you have Role-Based Access Control?

Yes, Vev takes security seriously. Our different account roles and project roles ensure everyone has the appropriate access needed to work effectively and securely.

Can we all work on the same project at the same time?

Yes! Vev is designed for team collaboration. As long as you've set up a team and created a folder for your project, everyone with access to that team can work on the project simultaneously.

Can I hide a project from a specific team member?

Yes, you have several options:

  • Create a project in your drafts - only you can see draft projects

  • Invite specific people into a project draft to limit access

  • Use Teams (Organization Plan feature) to give access only to specific members

Can everyone on my account invite users?

No, only Account Owners and Admins can invite others to the account. However, everyone on your account can share projects with external collaborators. This maintains security while enabling flexible collaboration.

Did this answer your question?