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
  • Joe Villanueva commented
    12 May 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 03:52pm

    I have another job that requires this feature.

  • Zissou commented
    20 Apr 10:41pm

    Vital for ecommerce sites with multiple editors

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

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

  • Gary Spindler commented
    12 Mar 05:25pm

    Desperatly needed!

  • Darren Chait commented
    10 Feb 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.)

  • Hamish Maclean commented
    21 Jun, 2019 12:59am

    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
    3 Apr, 2019 07:14pm

    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
    2 Mar, 2019 06:12pm

    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
    30 Nov, 2018 04:44pm

    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
    26 Oct, 2018 07:52am

    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
    11 Aug, 2018 08:55pm

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

  • Gonsalves Media commented
    5 Aug, 2018 04:36am

    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
    16 May, 2018 05:14pm

    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.

  • Alex Tapper commented
    1 Feb, 2018 06:43pm

    Would also love this feature so clients can add me to help fix small-scope issues (5min - 1 hr) on their site.

    Right now we're using screen-share "remote takeover" as a workaround -- but it requires that we are both on the computer at the same time and is a little laggy. 

  • Michael Naylor commented
    9 Oct, 2017 09:13pm

    This is really important to us. I would like to restrict access and visibility of sites and folders within a team account to certain team members. With sites being deleted permanently on Webflow, there is zero redundancy if a single of or an entire portfolio of sites is deleted accidentally or maliciously by a team member. Additionally, it is important that user based permissions are added to restrict junior users/freelances/etc from publishing to the live site (on a custom domain), restricted from editing/deleting/having visibility of sites as appropriate.

  • Vincent Bidaux commented
    4 Oct, 2017 08:16am

    I'd like to stop having to deal with my clients credentials and browser auths.

    Also, when cross site copy paste is unveiled, we're going to be frustrated if we can't copy paste components from our stuff to clients stuff without having to transfer a site first.

  • Load older comments
  • and 206 more