Granular permissions (per team or per project)

Add granular permissions for team members on a site by site basis, instead of on the account level.  Specific users to work on specific projects, in specific roles.

  • Waldo Broodryk
  • Jan 11 2017
  • In backlog
  • Liran Aloni commented
    14 Jan 08:16am

    This is extremly important. As a company we find oursleves considering other solution just because of this matter.

  • Marcel commented
    22 Nov, 2020 08:55pm

    Yes please. This will be helful if I can assign a person to work on a project for a limited time and then remove their login permissions once they are done with their portion of the project. Currently the Team plan allows for a minimum of 2 seats. I would like to have the option to add a temporary seat for a limited time period.

  • Dammon Burden commented
    19 Nov, 2020 06:36pm


  • Brad Harris commented
    19 Oct, 2020 10:13pm

    Absolutely essential for a team environment. Permission controls to prevent edits are a must. I am trying to teach Webflow to a class of design students. Any student can edit each other's work. I'm reconsidering teaching this because of this lack of security.

  • Inky Ajanaku commented
    6 Oct, 2020 10:21pm


  • Ali Attrill commented
    21 Aug, 2020 11:31am

    Can't believe this doesn't exist already.

    For collaborative work with individuals within an agency or freelancers you would expect to be able to give access to certain projects. This is the case on most PM systems such as teamwork etc.

    Much needed feature, please implement this soon, this is a massive hinderance to use at the moment!

  • One Branding commented
    20 Aug, 2020 04:46pm

    Yes please! We use 3rd party developers and animators and it's definitely not ideal to share all projects with every individual vs selecting specific projects.

  • Tim Daff commented
    13 Aug, 2020 12:31am

    This is a really much needed feature of Teams.

  • Alex Dixon commented
    29 Jul, 2020 08:01pm

    It would be super useful to be able to restrict collaborators to certain pages, folders, collections and functionality (such as meta data).

    The best implementation of this would probably be a simple role based permission system.

    As real world example: You have someone who just writes blog posts for your business (who could be external or internal to the business). Currently they would have access to everything on the website, including sensitive data such as form submissions (which is not ideal from a GDPR standpoint).

  • Christopher Francis commented
    14 Jul, 2020 01:19pm

    This would be really useful. We often work with freelancers on individual projects and it would be great to give them a seat on our account and access to specific projects without them having full uncontrolled to access all the projects on the team. I'm a pretty trusting person, but that's a little too far for me!

  • Zakk Kaye commented
    21 Jun, 2020 12:34pm

    This would be helpful, the ability to allow editing of products of only a specified category would be handy too.

  • Joe Villanueva commented
    12 May, 2020 09:36pm

    Please add the ability to selectively apply a permission to users. Not all collaborators are created equal - their willingness to test before publishing, their testing rigor, and their grammatical prowess, are hardly ever equal. Its a lot of responsibility to add even a single collaborator that creates a number of unnecessary and avoidable problems related to publishing. Extending the control to directories would also be a welcome addition.

  • Jason Roach commented
    22 Apr, 2020 03:52pm

    I have another job that requires this feature.

  • Zissou commented
    20 Apr, 2020 10:41pm

    Vital for ecommerce sites with multiple editors

  • Hürkan Gökkaya commented
    30 Mar, 2020 07:17pm

    It is important. It has to be some editor or manager levels.

  • Gary Spindler commented
    12 Mar, 2020 05:25pm

    Desperatly needed!

  • Darren Chait commented
    10 Feb, 2020 07:28pm

    Very important to be able to use contractors. Would want to limit ability to publish to live site.

  • Andy Bell commented
    27 Nov, 2019 11:53am

    Please! This would be a huge improvement... 

  • Vivek Rai commented
    30 Oct, 2019 10:48pm

    Hi @webflow team! Are there any updates to this? Echoing most other comments, this would be very useful - something as simple as a "push for review" with a notification sent to a designated member from a UX point of view.

  • Alan McDonnell commented
    2 Sep, 2019 04:49pm

    Just throwing my 2 cents in here as I think it could do with a bump and is becoming an issue when I introduce clients to the CMS. Maybe a "push for review" button should be introduced so lower-level editors can't accidentally publish unwanted changes. Ideally would love to assign roles with different levels of access (only to blog collection or full admin access etc.)

  • Load older comments
  • +275