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
  • Alex Dixon commented
    29 Jul 20:01

    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 13:19

    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 12:34

    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 21:36

    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 15:52

    I have another job that requires this feature.

  • Zissou commented
    20 Apr 22:41

    Vital for ecommerce sites with multiple editors

  • Hürkan Gökkaya commented
    30 Mar 19:17

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

  • Gary Spindler commented
    12 Mar 17:25

    Desperatly needed!

  • Darren Chait commented
    10 Feb 19:28

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

  • Andy Bell commented
    November 27, 2019 11:53

    Please! This would be a huge improvement... 

  • Vivek Rai commented
    October 30, 2019 22:48

    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
    September 02, 2019 16:49

    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.)

  • Hamish Maclean commented
    June 21, 2019 00:59

    In addition when a project is transferred to a client, a designer should be able to retain access to the designer. The simple fact is Webflow is behind shopify and wordpress when it comes to a client being able to own the site and invite collaborators in to the site. I go into shopify and I see sites that I manage. 

  • Monika commented
    April 03, 2019 19:14

    I would like to have a policy where if a project is transferred to a different account I'm informed beforehand, and I would have to approve it first (same way if email or password is being changed - I get an email and need to confirm the change). 

  • Michael Naylor commented
    March 02, 2019 18:12

    Any update on this guys? This is essential for team account security without necessitating multiple team accounts (kind of defeating the purpose).

  • Bailey Simrell commented
    November 30, 2018 16:44

    This can be two fold I think. Granular team permissions are one thing.. but what about granular editing permissions in the CMS editor? There should be different permission levels for different user types. For example, a blog. You would want writers in a specific content category to be able to access their own blogs, but not be able to post to other sections of the site. 

  • Greg Gruenwald commented
    October 26, 2018 07:52

    Hello everyone...

    This week I signed up for a Team Account.  Immediately I needed what is being referred to here as "granular permissions" on a per folder (site) basis to prohibit freelancers from having access to my entire company!  I cannot see where that is possible...yet...right?

    If it is not a formal capability within Webflow as of 10/26/2018, how are any of you handling this situation? 

    Again, one strategy I had was to put all my company's sites into my personal folder and then transfer them into team status to be addressed by the freelancer...and then once the work was completed, transfer them back to personal.  However, that would require that hosting be disengaged and then re-engaged when the work is completed.  Surely there's a better way! 

    Thank you, everyone.

    Greg Gruenwald
    Designed Communication Processes
    Chicago, IL 

  • Andrew Leyland commented
    August 11, 2018 20:55

    Need this big time to maintain control of staff/freelancer access

  • Gonsalves Media commented
    August 05, 2018 04:36

    Lots of great ideas here. I would love to see a lot of these added into a granular permissions overhaul.

    This is a must for Webflow team accounts and would be a fantastic CMS 2.0. 

  • Jeremy Meyer commented
    May 16, 2018 17:14

    I believe this is covered in some of the merged wishlist items but I would like to see granularity that allows me to set a scope so an editor can only modify a specific CMS collections.

  • Load older comments