Firstly, excited to see that Client Seats are finally here 
, which means we can start migrating Legacy Client accounts to either the Content Editor or Marketer roles. Good news.
I also appreciate that this has just been released, so there will be some gremlins to resolve in the short term. 
In a nutshell, I’ve started playing with Client Seats and have found a few potential issues/concerns, which I’ll list below.
For context, we’re on an agency workspace plan.
Issues:
-
A Content Editor can currently access and edit project settings (equivalent permissions to the Marketer role). I assume this is a bug.
-
Marketer roles have too much access/visibility of site settings and information, such as Shared Workspace templates, Subdomain Indexing & Publishing, Webflow Cloud, Clone of, Folder ID, etc.
-
Marketers can rename components, not ideal.
-
Marketers can create new collections. Is that intentional?
Requests:
-
Give the Marketer role access to 301 redirects.
Would make working with SEO agencies a lot easier. -
Give Content Editors the ability to edit component properties.
Such as selecting collection items in a collection listing component -
Option to lock down SEO and Schema settings on collection templates and static pages.
Sometimes, clients don’t understand dynamic content tags and manually overwrite them. -
Ability for Content Editors & Marketers to pin open the left-hand page nav menu, for easier page navigation.
-
For collection list content on static pages that can’t be directly edited on the page by a Content Editor, add a hover hint to advise that the content needs to be edited via the CMS screen.
-
Content Editors can currently import/export collection item content; make this an optional permission.
-
The ability to hide certain components from Marketer roles.
Link to this post on the new Webflow community forums 
