CMS: Option to make elements non-editable by default

Before I hand over to a client, I have to make sure to un-check 'collaborators can edit this element' on masses of page elements as I don't want them to be able to mess around with background images, text etc.. this is time consuming and I always miss some. In the worst cases, a client ends up trying to replace a background image or increase a headline by 10x the character count or some just gets confused in the editor who the edit options highlight.

It would make more sense for the default to be unchecked.. then we explicitly allow element sot be editable. 

  • Matthew Sanderson
  • Feb 6 2017
  • Matti commented
    July 06, 2017 12:11

    Hi, how is it actually going with this one? I believe there must be tons of other threads with the same topic. Here it was discussed a year ago https://forum.webflow.com/t/cms-editable-elements-why-cant-they-be-un-editabe-by-default/30006.
    This can be fixed by one checkbox in settings, can you pls. add this option?

    It´s puzzling me that more people are not furious about this? Is nobody handing editor over to clients? People happily click on 1000+ checkboxes? Or just don't care what client will be messing with?

  • Joshua Jacobs commented
    April 16, 2018 14:37

    Bump. Or even include the ability to exclude whole folders/pages from editing in page settings?

  • Jared Diaz commented
    May 08, 2018 17:09

    Just seems like this should be unchecked by default. It's a painstaking process to go back and uncheck all elements you don't want a client to touch. And, they'll sure be able to find it when they start poking around. 

  • Erin Patrick commented
    May 08, 2018 18:42

    Our team would really be interested in getting this set up as well, so that you could exclude pages or folders from editing and be able to give access to some users and remove from others for certain elements in Webflow.

  • Garry Foreman commented
    May 11, 2018 11:32

    I agree with your comment the default should be unchecked.

  • Alex Ross commented
    May 24, 2018 20:18

    There absolutely needs to be either an option to have elements un-editable by default, or disable editing on a page by page basis. Going back and disabling editing on EVERY element on a huge website is absurd.

  • Andreas Posch commented
    October 29, 2018 16:17

    this is really a pain in the ass

  • Fei-Ling Tseng commented
    November 23, 2018 17:28

    Still a huge issue. I suspect there aren't many votes because we already have all our votes used on other pressing issues. Doesn't mean it isn't a problem for more people. And a "simple" fix.

  • Garry Foreman commented
    02 Jan 17:26

    I agree there should be a choice whether all new items are created as editable or non-editable by default.

    I also agree it would be nice to be able to set specific pages as non-editable.

    I like to greatly control what my clients can/can not edit and having to manually select and uncheck each item takes forever.

  • Dimitri Phalen commented
    22 Feb 17:11

    I'll be spending a day or so checking this moronic little box element by element so I can hand over CMS access to depts in our company, a checkbox of "access cms only" would save me ridiculous amounts of time, I work with people who love to poke and prod and change things for no reason beyond their own opinion, when it's not their choice to make. I'm debating just never handing over editor access and taking on the burden of posting all their blogs and announcements and staff page modifications just so I don't have to waste so much time doing this, and remembering it every time i add more content.

    This really should have come out with the addition CMS, or if anybody has a line of code I can add in anywhere that checks alllllllllllllllllllllllllllllllllllllllll those boxes I'd be so greatful

  • Alex Dixon commented
    23 Feb 15:37

    +1

    A switch to choose your preference for this would suit everyones needs.

  • Paweł Nejman commented
    23 Feb 20:11

    It still has not been repaired? <facepalm>

  • Morgan Leahy commented
    22 Aug 19:11

    Not done yet?