We often have several design changes that need to be made, and letting multiple designers access and make changes to the same project simultaneously would be incredibly valuable.
+1 for tis feature!
a practical proposal: still block simultaneous editing on the same element (class) but allow opening a project and working on different elements at the same time
blocking whole sites from collaboration could be handy too but is not ultimately required for consistency
Very important feature!!!
1 designer per project is huge bottleneck. Must have 2 working on different pages and I must speak to support over the phone or skype call please.
This is a must have for our team.
A must have functionality to organise our work voor multiple projects
We are considering to use Webflow for our teams. This is vital functionality for our teams though.
I'm trying to sell Webflow to my executive team for our marketing and CMS. They immediately wanted to see the designer interface. Please make this happen.
The lack of this feature has been the single biggest pain point for our team.
We made the decision to migrate from Squarespace to Webflow assuming that Webflow's support for multiple "editors" would allow us to collaboratively work in the designer at the same time.
Not being able to work in the designer simultaneously slowed our migration down significantly and caused no small amount of frustration.
+1. I could live with blocking on page level (so that only 1 designer is allowed per page). But locking the whole project is becoming more and more difficult for my team.
+3.Marco put it best—I too could live with blocking on page level (so that only 1 designer is allowed per page). But locking the whole project is becoming more and more difficult for my team.
I ran out of votes, but this is a +100 for me and my team. We have internal designers, as well as contractors that all need to be in Webflow at the same time, and we've bumped up against the limitations very quickly.
This was a huge pain point for my team as we migrated to Webflow. We could be a lot more agile if multiple people could be working on a project at the same time.
We are considering migrating our agency to use Webflow, but we are a team of designers that often need to work on the same project at the same time.
As a short-term solution, perhaps you could allow cloning pages to other sites? This would allow me to clone a site, build a page and essentially merge it back into a main project. Eventually, full real-time collaboration would be preferable, but this fix should not require much development work.
This is not a hard problem anymore. Support multiple real-time cursors in the designer. If people make conflicting changes (in the same millisecond?!) you just apply them in order they arrive at the server and it will be obvious to the users to resolve it among themselves. Online (realtime) collaboration is the primary reason people suffer the downsides of browser-delivered software. You need this feature.
Any response from the Webflow employees whether they're open to this idea, and if so, where it stands to happen?
My team is also greatly slowed down by this. When we need to make any changes, from a small fix to developing a new page, only one of the changes can be worked on at the same time, regardless of how closely related they are in terms of elements and styles or even if they’re on separate pages. I see the challenge with multiple designers editing the same classes (even unknowingly), but perhaps there’s a way to lock / freeze those items that two or more designers could potentially edit at the same time.
Figma solved this. You can too.
Want to be clear here, I do not care about multiple users being able to edit the same page at the same time. I care that admin users should be able to edit separate pages at the same time. It's incredibly frustrating that this isn't possible.
please please please
This is my #1 pain point with webflow. We need the ability to do individual page takeovers instead of entire site takeovers. We also need the ability to publish a single page's changes rather than publish the entire site anytime we make an adjustment. Wordpress does this. Webflow needs this, otherwise it isn't a good solution for large teams or large projects, and will remain a technology only good for microsites.
agreed with Brian Krall^ on this one. make multiple editors available for separate pages only. Hugely difficult to collaborate with a team because of this.
Would be great, seems like a must for when our team grows. Even a way to use git?
I understand syncing/collaborative applications are hard to do properly, and the risks of overwriting. and do know the challenges of teamwork with developers on the same site in a traditional setting.
A team exists for manpower, and doing a project quicker than one person.
£80 just seems a bit much too much for something that requires a workaround (constantly copying the site back and forth so we can work on 'sections' of the site and paste back in.
Webflow is great, its the way everything should work in 2018, and get why this doesn't work; but its a pain for sure.
In an agency, if we need to expand and do work quicker we would hire more people, this is not an option here, as we are restricted to one person per site - maybe this is the wrong place to start a workflow discussion, but maybe just explaining a workaround in regards to the team account would help a little for now.
Agreed that locking down a page is fine, just not the whole project, please prioritize this feature!
We are building out a large non-profit site and thought we would be able to work in the collaborative editor mode. Not having the ability to have at least TWO people working on the site at one time is a huge setback to getting the project done in a timely fashion. There are many other CMS that I have personally worked in that provide the feature of locking out others from a page that is being worked in and it works well. Would love to see this ability in Webflow!
This feature would be super helpful for our team!
Much needed feature
+3 and hoping that this issue gets better visibility
We migrated to a team account assuming that this feature was already in place. Our mistake, apparently... We had assumed that when Webflow's page says, "Team plans allow you to collaboratively work on sites...." that it meant having multiple people being able to work in the same project at the same time. NOWHERE on that page is there fine print about only one team member being able to access the designer for a project at a time. Even under the "Need to Know" section, pasted below.
Separately but relatedly, "upgrading" an individual account to a team account (i.e. adding new designer logins for existing projects in an account) is fraught with pain points. When you sign up for a team plan via your dashboard, the Webflow UI makes it look like you are "upgrading" your account; however, you are actually creating a different account that you have to transfer your projects to. If your individual account includes a hosted project that you're trying to transfer, you actually have to take it offline briefly in order to make the transfer to a team account, even if your individual account is the owner of a team account. We were willing to go through that process because of the prospect of having designers collaborate. Had we known this was not the case, we definitely have waited to go through this hassle.
Team Plans allow you to collaboratively work on sites that are managed and billed under a Team, outside of your individual dashboard. Create a new team
Individual Plans use the same login credentials, but you can work on sites privately from a separate dashboard.
I hope this doesn't become the big negative with Webflow like it seems it may for our team and clients. Big fan of Webflow for sure. This feature would be super helpful though. Thanks!
This feat is a 'must have' nowadays. It's a deal breaker honestly.
Agreed - we're working on a major migration for a fortune 500 tier client and hit the limit really, really quick. LOVE Webflow, truly. But I'm writing this post while waiting on other team members to finish up their work so I can make what are effectively minor changes, but that are causing a large executive review bottleneck. Can we give this 10,000 votes? Thanks!
You won't be notified about changes to this idea.