Team seats, roles and client access on a website platform: how to set them up safely

By Ranjit Bhinge, founder of Blur Studio · Updated · 10 min read

Short answer: On a website platform, give each person the lowest role that lets them do their job: an owner or admin for the people who control billing and publishing, editor-style roles for staff who change content, and a view-only or limited role for clients. Platforms count seats differently. Webflow (a visual website builder) and Framer (a design-led site builder) bill by seat type, while Ploy (an AI website platform) documents no seat-based pricing and lets you invite people on paid plans. Name each person, never share a login, and remove people the day they leave.

Ranjit Bhinge

You are about to add a teammate, a freelancer or a client to your website platform, and you want to know what each role can touch and what it will cost.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Roles decide who can change your live site, see your bills and delete work. A role set too wide is how a client deletes a page, a former freelancer keeps access, or a junior moves a domain by mistake. A role set too narrow means every small text change comes back to you. The fix is the same on every platform: write down the jobs, match each job to the smallest role that covers it, and test the result.

This page compares how five platforms handle seats and roles, shows the setup steps for Ploy, gives a role plan you can copy, and lists the risks. Role names and seat prices are from each vendor's own help pages, read in November 2026. They change, so confirm on the vendor page before you invite anyone. This is general information, and your contracts with clients decide who owns what.

This page may contain affiliate links from which Blur Studio earns commissions.

Roles at a glance, across five platforms

A seat is a paid or free place for one named person in your workspace. A role is what that person can do once they are in. Some vendors bill by the seat, some bill by seat type, and some include invites in the plan.

PlatformRoles named in its docsHow seats are counted
PloyOwner, Admin, MemberInvites are included on Starter, Pro and Enterprise with no stated limit on people invited, and not included on Free. No seat-based pricing is described.
WebflowFull seats: Admin, Site admin, Designer. Limited seats: Marketer, Content editor. Client seat: Marketer, Content editor, Reviewer. Free seat: Reviewer. Guest: Guest.Every workspace includes one full seat for the owner and 100 free reviewer seats. You can buy more full and limited seats. Client seats per site depend on the workspace plan: 1 per paid site on Starter, 1 per site on Freelancer, 3 per site on Agency.
FramerOwner, editors, content editors, viewersWorkspaces are billed for members with edit access. On Basic and Pro the owner is free, extra editors cost $20 per month, content editors $10 per month and viewers are free. Enterprise is custom.
WixAdmin (Co-Owner), Website Manager, Website Designer, Back Office Manager, Content Writer, Billing Manager, Domain ManagerEach invitee uses one collaborator seat, and free seats differ between Wix and Wix Studio.
SquarespaceOwner, Administrator, Billing, and content rolesOne owner per subscription. Check the current permissions page for what each extra role costs.

Prices are USD where the vendor page shows USD and are as of November 2026. Check Webflow's pricing page for its seat prices, which are not listed here. Framer's figures come from its Subscriptions and charges help page. Webflow's seat and client payment help pages and the Squarespace permissions page were read in November 2026.

How roles work on Ploy

Ploy splits your account into an organization and workspaces. According to Ploy's team docs (updated 5 November 2026), the organization holds people, roles, plan and billing. A workspace holds sites, documents, assets, brand context, databases and integrations. By default, everyone in the organization can reach every workspace.

RoleWhat Ploy's docs say
OwnerOrganization-level control, including People and billing
AdminElevated administrative permissions, including deleting workspaces
MemberStandard collaboration. Members can manage custom domains and path routing in the workspaces they can access (Ploy's team docs). Ploy's changelog adds that they can edit and publish content from the dashboard

Some actions are held for owners and admins: managing people, the plan and billing, workspace settings, deleting a site or workspace, turning site analytics on or off, and publishing through Ploy's agent (the AI assistant that edits your site from chat). Note that a Member can still manage custom domains. That surprises people, so if you do not want a contractor touching DNS-linked settings, limit which workspaces they can enter. For what a domain change involves, see custom domain, DNS and SSL setup.

Invite a person on Ploy

  1. Open People in the organization menu.
  2. Choose Invite and enter the email address.
  3. Pick Owner, Admin or Member. Start with Member.
  4. Send the invite. The person can accept from the email or from the bell in the sidebar.

To limit a Member to chosen workspaces, open People, open the member menu, choose Edit permissions and pick Only these workspaces. Only Members can be limited, and Ploy's docs say this setting is turned on per account and available on request, by emailing sales@ploy.ai. If a client has to see only their own site, that feature or a separate organization is how you get it.

Two more controls help. Only the organization owner can require stronger sign-in, for owners and admins only or for all members, under Organization then Security. Once that is on, Ploy shows an extra confirmation step before removing a custom domain that serves live traffic, deleting a workspace with a published site, or deleting a site tied to a live domain. Ploy's page does not say which plan includes it. See Ploy login and account setup for passkeys, and Ploy for enterprise, SSO and roles for the larger-team features.

Four ways to give a client access

Pick the model before you pick the role. Each one gives a different answer to "who owns this, and who pays".

ModelWhat the client seesPick it whenMain risk
1. Client has no loginNothing. You make every edit.The client sends small changes and you run a care planYou become the bottleneck, and the client may not feel they own the site
2. Reviewer or viewer seatThe site and a way to comment or approve, no edit rightsThe client signs off pages but does not writeFew. Free reviewer seats exist on Webflow, and viewers are free on Framer
3. Content editor seatText and image changes, no design or setupThe client updates news, staff pages or offersEdits that break layout or claims. Pair with an approval step
4. Separate organization the client ownsEverything in their account, with you invited inYou hand the project over, or the client pays their own billsYou lose control when they remove you, so agree this in the contract

On Ploy, an agency can run in two billing set-ups according to its agencies docs (updated 5 November 2026): "agency pays", one organization with many workspaces, where one plan covers everything and no plan limits the number of workspaces, or "client pays", separate organizations, because billing lives at the organization level. You can mix the two. Clients can be limited to their own workspace through the per-account setting, and separate organizations give full isolation. A workspace can also be moved to another organization without rebuilding, if you are an admin of the destination organization. For the full handover picture, read handing a website to a client. For running many client sites, see managing multiple client websites. Ploy's agencies docs do not describe a white label option, so tell clients plainly which tool the site runs on.

On other platforms, client access is built into the seat types. Webflow's client seats are site-level and exist for service-provider workspaces. Webflow Client payments (Freelancer and Agency workspaces) lets the client pay for the site plan directly and defaults the client to the content editor role, which you can change under Site settings then Site access. Wix and Squarespace use named roles instead: a Wix Billing Manager can buy and manage subscriptions, while a Squarespace Billing role handles payments and cannot add or edit content. Squarespace's permissions table also lets Billing delete the site, so give it to as few people as you can.

A copy-ready role plan

Fill in names and keep this in your project folder. One row per person.

PersonJobRoleBilling accessReview date
You (owner)Account controlOwnerYesEvery quarter
Office managerBackup contact, pays invoicesAdmin or billing roleYesEvery quarter
Marketing leadEdits and publishes pagesMember, editor or designerNoEvery quarter
Freelance writerDrafts copyContent editor, or comment-onlyNoEnd of project
Client contactApproves changesReviewer or viewerNoEvery contract renewal

Rules that go with the plan:

  • One named account per person. No shared logins. A shared login means you cannot tell who made a change.
  • At least two people who can recover the account. If the only owner leaves or loses a passkey, you lose the site. Ploy's docs say Members cannot reach its billing portal, and there is a Transfer Ownership option in the member menu.
  • Billing access goes to the fewest people possible.
  • Publish rights are separate from edit rights where the platform allows it. Where it does not, add a human approval step before anything goes live. AI-written pages need human review either way.
  • Use a company email. A personal Gmail address on an owner account becomes a problem the day that person leaves.

Risks and how to reduce them

  • Former staff and freelancers keep access. Make removal part of your exit checklist, and also remove them from connected tools such as CRMs, analytics and domain registrars.
  • The client is the owner of nothing. If you registered the domain and the account in your name, the client may be stuck if you disappear. Put ownership in the contract, as in contracts for website work.
  • The client edits too much. A content editor can still publish a false claim. Agree what they may change and what comes back to you.
  • Roles are broader than the label suggests. Ploy's Members can manage domains in the workspaces they can reach. Read each vendor's role table, not just the role name.
  • Seat costs creep. On Framer, extra editors are billed per month, so a freelancer you forget costs money every month. Review seats on a calendar date.
  • Admin sprawl. Many admins mean many people who can delete a workspace. Ploy blocks deleting a workspace that has its own paid plan or still serves a domain, but do not rely on that.
  • Connected tools hold their own access. A person removed from the site platform can still hold the keys to the CRM or the ad account. Audit those too. See data security questions to ask a platform.

A worked example with made-up numbers

A six-person agency runs 8 client sites on a platform where each client owns their own organization (the "client pays" model on Ploy). The agency owner is Owner on its own organization and is invited as Admin to each client organization. Two staff are Members on the agency organization. The client contacts are Owners of their own organizations and are told in the contract that the agency may stay on as Admin for the care plan.

In a quarterly review, the agency lists 11 people with access across the 8 clients and finds 3 who left the project months ago, one freelancer still an Admin and one client contact who left their company. It removes the 3, moves the freelancer to Member and asks the client to name a new owner. Nothing here is an incident, which is the point: the review catches problems that nobody would have noticed otherwise. These numbers are invented to show the method. Your own count will differ.

Test plan: prove the roles work before the project starts

  1. Invite a test email address at each role level you plan to use.
  2. Sign in as that person in a private browser window.
  3. Pass: they can do their job. Fail: they have to ask you for something they need weekly.
  4. Try three things they should not be able to do: open billing, delete a page or site, change a domain. Pass: all three are blocked. Fail: any works. If a Ploy Member can change a domain you meant to protect, limit them to chosen workspaces.
  5. Remove the test person. Pass: they lose access at once. Fail: the platform keeps a session or a connected tool still lets them in.
  6. Write down what you found in the role plan.

Who needs less of this

A solo owner with one site and no contractors needs one account with a strong password or passkey, a second recovery contact, and nothing else. If your platform includes invites only on paid plans, as Ploy does, do not pay for a plan just to add a reviewer. Send screenshots or a preview link instead.

How I'd approach this

I would start from the contract, not the settings screen. In week one, decide the model from the table above for each client, write the role plan, and put ownership and access removal into your terms. Day one: list every person with access to every site and tool. Day two: remove anyone who should not have it. Day three: set each remaining person to the lowest role that works, and add a second recovery contact. Day four: run the test plan. Day five: put a quarterly review in your calendar.

Decision rule: choose a platform whose roles match your clients. If clients need to edit alone, check for a client-style seat or a separate organization. If they only approve, a reviewer or viewer seat is enough. If you are weighing Ploy for this, check Ploy's plans and invite rules against your client count, and ask about limiting members to chosen workspaces before you sign anyone up. Skip it if you need white label, which its agencies docs do not describe. If your needs are more custom, Blur Studio builds the custom version: AI agents that use your business knowledge, CRM and calendar connections, finishing a half-built flow, and ongoing care. You can see what that includes.

You may also want building a client portal for your agency customers.

Questions people ask

What role should a client have on their website?

Match it to what they do. If they only approve pages, use a reviewer or viewer seat. If they update text and images, use a content editor style role. If you are handing the site over, put them in their own organization as owner. Give billing access only to the person who pays.

What can a Member do on Ploy?

Ploy's team docs describe Members as standard collaborators who can manage custom domains and path routing in the workspaces they can access, and its changelog says they can edit and publish content from the dashboard. Owners and admins keep people, plan and billing, workspace settings and deletions. See Ploy login and account setup.

Does Ploy charge per seat?

No seat-based pricing is described in Ploy's docs. Invites are not included on Free and are included on Starter, Pro and Enterprise with no stated limit on the number of people. Check Ploy's pricing page for your plan, and read Ploy pricing.

Can I limit a client to only their own workspace on Ploy?

Ploy's docs say limiting Members to chosen workspaces is turned on per account and available on request through sales@ploy.ai. Separate organizations give full isolation, and each organization has its own billing.

How much does a Framer editor seat cost?

As of November 2026, Framer's help page says workspaces are billed for members with edit access. On Basic and Pro the owner is free, extra editors are $20 per month, content editors are $10 per month and viewers are free. Check Framer's current page before you invite anyone.

How many free reviewer seats does Webflow give?

Webflow's seat help page says every workspace includes one full seat for the owner and 100 free reviewer seats, and you can buy more full and limited seats. Check Webflow's pricing page for seat prices.

How do I remove a team member safely?

Remove them from the platform the same day, then remove them from connected tools, shared inboxes, password managers and the domain registrar. Check that the person lost access in a private window. A quarterly access review catches anyone you missed.

Should I share one login with my team?

No. Use one named account per person. Shared logins hide who changed what and make removal harder. If a platform charges per seat, the cost of an extra seat is smaller than the cost of one bad edit you cannot trace.

More in this topic: Websites: seats, billing and hiring alternatives (4 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…