Could someone please explain something! I currently have a WF Agency Workspace. One of my sites is on Business Hosting with a number of users added as Editors (x6). They are all using the Legacy Editor to manage content on the site. I understand the Business Hosting package allows up to 10 users.
Fast-forward to the end of 2025 when the Legacy Editor is depreciated. What happens when an existing Editor needs to edit the site?
When the Legacy Editor is deprecated at the end of 2025, your existing Editors will need to transition to Webflow’s new Roles & Permissions system within the Workspace settings. Since you’re on a Business Hosting plan, you’ll still have up to 10 content editors, but they will now manage site content through Webflow’s updated Editor experience. To ensure a smooth transition, you should familiarize your team with the new interface before the change takes effect and verify that all editorial permissions are correctly set up in the new system. If you need further assistance, please feel free to connect.
Thank you so much for the swift reply, much appreciated!
I have a new staff member who requires training in the Editor this week. It would make sense to get them started on the new Editor. Can I ask - how do I enable access to the new Editor for them?
I read somewhere about ‘seat access’ - is this the same thing, and do I need to pay more for their access?
For site plans setup before the migration ( mid 2025 ), all of your existing Legacy Editors that you are using will be automatically migrated to client seats.
That means you would need to be using all 10 of your legacy editor accounts invites in order to have 10 client seats.
Once that migration occurs, your editors will be accessing the designer edit mode rather than the legacy editor.
Regardless, I’d setup a legacy editor seat for each member of your team. If you want them to use the new designer based editing experience before then, you’d need to purchase limited seats. Once client seats are setup and that migration happens, I think you should be able to cancel those and use the client seats, but it’s hard to guess how Webflow will build that UX.
Existing site plans with existing legacy editor seats will migrate directly to client seats as no added costs.
If you want designer edit mode access now, before client seats is implemented, then yes you’d need to purchase limited seats.
For new projects / site plans after clients seats is implemented, the rules change… client seats are a function of Agency / Freelancer workspaces instead of tied to site plans. So the number of editors a site plan gets depends on the workspace it’s hosted in, not on the site plan itself. I believe it’s 1 client seat if it’s hosted in a Freelancer workspace, and 3 client seats if it’s hosted in an Agency workspace. There are other factors there as well Webflow hasn’t hashed out yet.
So a hypothetical example: if I’m quoting on a NEW site today that requires CMS hosting, and would need x2 content editors, and I’m on the Agency Workspace Plan, do those 2 Content Editors require a paid seat (an additional cost on top of hosting), or would they be included at no additional cost over and above the hosting cost?
If you establish the CMS Site Plan today, you will get 3 Legacy Content Editors due to the Site Plan. In ~4 to 6 months the Editor seats that you’re using would get migrated to Client Seats, still at no cost, where they’d be using the designer Edit mode instead.
In both cases your editor needs are covered.
ADDED
If you quote on that same site in 2026, you’d still get 3 Client Seats for your editors, if the site plan is established inside of your Agency workspace. Client Seats will be tied to workspaces in the future, rather than Site Plans.