Guest Posting to CMS

I am on the Freelancer platform. Is it possible to give guest access while the site is still on a staging site? If so, can they post new blog posts (or add to another CMS Collections) on a staging site? The reason for this is to simply test posting before the site goes live.

Hi there,

Guests in your Workspace have view-only access to all sites, including staging sites. They can browse and interact with published content but cannot make changes to the site design, content, or settings. This means they can:

  • View all published pages and content
  • Access staging sites for preview purposes
  • Navigate through CMS collections and blog posts
  • See the site in both published and staging environments

However, guests cannot edit, create, or delete any content, including CMS items or blog posts. For team members who need editing capabilities, you’ll need to invite them with appropriate permissions (Admin, Editor, or Designer roles).

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.

Ok, so is it only possible to edit on another site if you have a paid seat? Is that correct?

Does this mean that I would have to pay for a seat on a client site if they want me to edit for them? I’m afraid I don’t really understand this

Webflow’s in the middle of a rearchitecture regarding client-editor access.

Currently, the legacy editor is free, but it’s limited in capability and it’s tied to the Site Plan, which means they cannot use that until you add hosting.

You can purchase a half-price “limited seat”, and give them Editor or Build mode access to the site, which allows them to use the modern designer to add content.

Once the migration is complete ( late this year? ) Webflow will roll out client seats which are exactly what you’re looking for.

  • Full editor or build-mode access through the designer
  • Site-specific
  • Available before the site is on a hosting plan
  • Free- they’re become a feature of your Agency / Freelancer workspace rather than the site plan

I’ve written more at the link below.

For now I’d recommend;

  • Pay for a 1/2 price client seat for now, so your client can edit during the design phase
  • Once you add a site plan, you can choose to remove that, and teach them to use the more limited [ but still functional ] legacy editor
  • Regardless, assign as many legacy editors as you’ll actually be able to use
  • Then once client seats is rolled out, those legacy editors will be automatically converted to client seats at no cost.