This idea has been merged into another idea. To comment or vote on this idea, please visit WEBFLOW-I-615 Permission Based CMS Editing (Role Based Editing).
Would be REALLY great to be able to do things like:
1) Permission to access only certain collections / pages
2) Restrict access to page settings (e.g. SEO stuff like metadata)
3) Start with all page elements NOT being on for collaborators. Right now, I have to go into each element and selectively disable collaborator access. I'd prefer to start the other way. No access to anything and then I choose what they have access to. At least give me the option to start one way versus the other.
Josh Gordon
.svg){kind=logo}
Show/Hide collections to client viewers
Merged
Ability to toggle the visibility of static pages and cms collections on / off for the editor (i.e. hide from customer)
Merged