Published
9 MIN READ
Framer CMS: who edits the website after handoff
The Framer CMS is the part of the website that holds content that changes often, like posts, case studies, job openings and FAQs, stored in collections and edited without touching the design. Since September 2026, it has a List field, and people who only edit content have their own, cheaper role.
The Portuguese-language tutorials we read in September 2026 teach how to set up collections for whoever builds the website. This guide looks from the other side of the table: whoever owns the website and will edit it after handoff.
The starting point is knowing who owns the account. At Wama, the project is transferred to the client's account and the subscription goes on the client's card, so the client becomes the owner of the website, the domain and the Framer account. That changes the conversation about editing: whoever invites editors and sets permissions is the company, not the vendor. It's also what weighs on the cost of maintaining the website after handoff.
What is the Framer CMS and what does it edit?
The CMS is a content database inside the project itself. Each collection groups one type of content, like the blog or the case studies. Each item is a record, like a post. The fields define what every item has: title, image, text, date, link, reference to another collection.
The page design is done once, and the CMS generates a page for each item. A blog with 80 posts has one post layout and 80 items in the collection, not 80 pages designed by hand. That's why you can move a WordPress blog into the CMS without redesigning post by post. When someone fixes a title in the CMS, the corresponding page changes without anyone opening the Framer canvas.
That's why the way collections are modeled decides how much the team can edit on its own. Content written directly on the canvas only changes with design access. Content that became a collection field changes through the CMS. That separation is set early, and the brief defines the collections when it lists which content the company will publish often.
What changed in September 2026 with the List field?
The List field groups repeated content inside a single collection item. According to Framer's updates log, published on September 8, 2026, it's meant for FAQs, product features, tutorial steps and case studies, with rows you add and reorder like in a table.
Before, the workaround was duplicating fields: Title 1, Description 1, Title 2, Description 2. The model locked the quantity. If a case study had four results and the model allowed three, the fourth didn't fit unless someone changed the structure. With the list, the person editing adds a row and moves on.
For websites already live, the announcement says Framer's agent converts repeated fields into a List and reconnects the data on the canvas. Wama uses Framer's agents a lot in its production workflow, and this is the kind of task where they save mechanical work, as long as someone checks the result before publishing. Whoever is going to give the team that access first needs to roll out Framer's agent to the team with clear rules.
Who can edit: Editor, Content Editor or Viewer?
There are three roles with different access. According to Framer's help center article on roles and permissions, updated on August 19, 2026, the Editor creates and edits projects. The Content Editor handles the CMS, translation and on-page editing. The Viewer only reads and comments, and doesn't pay.
Role | What it does | Cost on the pricing page (Sep/2026) |
|---|---|---|
Editor | Designs, edits content and publishes, according to permissions | US$ 20 per additional editor per month |
Content Editor | Updates the CMS and translation and uses on-page editing | US$ 10 per editor per month |
Viewer | Views and comments on pages and designs | Free |
On plans with advanced permissions, the owner can also separate three keys per project: Design, Content and Deploy. The last one decides who pushes a change live. With a staging environment turned on, any member publishes to staging, and only those with Deploy promote it to the real website.
For most companies, the setup that works is simple: marketing as Content Editor, one person with Deploy and everyone else as Viewer. When Wama hands off a website, whoever only publishes content gets the content editor role and edits through the CMS, without touching the design.
There's a detail that matters for the budget. Framer's pricing page states that Pro-level Experts get free editor access on client projects. As a Framer Expert Pro, Wama keeps working in the client's project for adjustments without taking up one of the company's paid seats.
Editing directly on the published website
On-page editing lets you change text, images, component properties and CMS content by opening the website itself in the browser, without going into the canvas. The help page on on-page editing, updated on September 15, 2026, details who sees the Edit button and what it reaches.
On a custom domain, the button only shows up for the owner and for collaborators with content permission. You can create a new CMS page from an existing detail page, like a post or a job opening, and the Show All Fields command opens the fields that don't appear on screen, like the SEO description.
The point that protects the company most comes at the end: when you click Finish Editing, whoever has publishing permission gets an email, and the change only goes live after it's reviewed and published. Layout templates and overlay content, like menus and modals, can't be edited this way.
What are the CMS limits per plan?
The limit matters when the website generates many pages from collections. On the Framer pricing page we read on September 28, 2026, the Basic plan, at US$ 10 a month, has 30 pages, 2 collections and 1,000 items. Pro, at US$ 30 a month, has 150 pages, 10 collections and 2,500 items.
Limit | Basic | Pro | Pro with add-ons (cap) |
|---|---|---|---|
Designed pages | 30 | 150 | 700 |
CMS collections | 2 | 10 | 40 (US$ 40 per 10) |
CMS items | 1,000 | 2,500 | 40,000 (US$ 20 per 10,000) |
People with editing access | 10 | 10 | 10 |
Two collections on Basic run out fast: a blog and case studies already take both. Among Wama's clients, the typical plan is Pro, almost always. To see the rest of the bill, like AI credits and domain, it's worth looking at Framer's plans from the inside.
What to ask the studio for at CMS handoff
A well-delivered CMS is one the team edits without calling anyone. Before receiving the project, check these seven points with whoever built the website:
A list of the collections, with the fields of each one and what they're for.
Repeated content in a List field, not in Title 1, Title 2, Title 3.
SEO description and share image as collection fields.
Defined roles: who is Content Editor, who has Deploy, who stays as Viewer.
Staging turned on when more than one person edits, so changes are reviewed before publishing.
Training for the team that will publish, with a post created from scratch in front of them.
Project and subscription in the company's account, not the vendor's.
At Wama, after handoff, the client's team gets training on how to use the CMS, there's a warranty period with free fixes and an open channel for one-off questions, with no monthly maintenance contract. That's the package a studio that delivers in Framer should describe in its proposal.
Modeling collections also costs time. At Wama, a website with a CMS takes longer: 8 to 12 weeks, versus 4 to 6 for a corporate website without collections. If you're coming from another platform with years of posts, add the migration to the schedule.
Common mistakes in the Framer CMS
Fixed text on the canvas. Content that changes every month written directly on the page means calling someone with design access for every change.
Everyone with Editor access. It costs twice as much as Content Editor and opens the design to people who only needed to change some text.
Nobody with Deploy. On-page edits sit waiting for review.
Plan chosen by the number of designed pages. What runs out first on a website with a blog is usually collections or items, not pages.
Content rules that live only in someone's head. It's worth saving the website's rules as a skill, so the agent and the team follow the same standard.
Frequently asked questions about the Framer CMS
Do I need to know how to code to edit the Framer CMS?
No. The CMS works like a table: each row is an item, each column is a field. Anyone who can fill out a spreadsheet can create a post, swap an image or fix a title. With on-page editing, you can even do it by clicking on the website itself.
Can a Content Editor break the website's design?
Not through the CMS. The Content Editor role, according to Framer's help center, handles content, translation and on-page editing, with no access to the design tools. They can put text that's too long into a short space, so the handoff training should show the limits of each field.
Does a change made in the CMS go live right away?
It depends on who edits. With on-page editing, the change only shows up after someone with publishing permission reviews and publishes it. With staging turned on, the member publishes to staging and only someone with Deploy pushes it to the real website. Someone with Deploy who publishes directly puts it live right away.
How many editors can a Framer website have?
On the Basic and Pro plans, the Framer pricing page we read in September 2026 limits editing access to 10 people. Viewers don't count and don't pay. The Enterprise plan has custom seats, without that cap of ten people editing the same website.
Does the List field work on websites built before September 2026?
Yes. Framer's announcement says the agent converts repeated fields into lists and reconnects the data on the canvas. Even so, the conversion changes the collection's structure. Ask whoever takes care of the website to make the change in staging and check page by page before publishing.
If your company wants a Framer website that the team can edit on its own from day one, talk to Wama about your project.
