Ploy for Agencies
Managing sites for multiple clients? Pick the setup that matches how you want billing, access, and ownership to work — then get every client live without waiting on us.
Everything in Ploy sits on two layers: organizations handle people, access, and billing, while workspaces hold the actual work — sites, domains, assets, and your brand design system. Agencies get to decide how to arrange those two layers around their clients. The big question is simple: who pays?
If you're new to these terms, read Working with a Team first — it covers organizations and workspaces in depth.
The two setups at a glance
| If you want… | Set it up as… | Who pays |
|---|---|---|
| To own billing across all your clients | One organization, one workspace per client | You (the agency) |
| Each client to pay for their own site | A separate organization per client | Each client |
You can also mix the two — keep some clients on your plan and split others onto their own orgs.
Setup 1 — You own billing (one org, many workspaces)
This is the simplest way to run an agency book of business. Create one organization for your agency, then add a separate workspace for each client under it.
- One plan covers everything. All your client workspaces live under a single subscription — you don't buy a new plan for every client you take on.
- Multiple custom domains on the same plan. Each client workspace connects its own custom domain, all under your one org and one bill.
- No extra subscriptions per client. Adding a client means adding a workspace, not another recurring charge.
- One place to manage. You control access, billing, and every client site from a single organization.
How to set it up
- Create (or use) your agency organization.
- Add a new workspace for each client — one workspace per client keeps their sites, assets, and brand cleanly separated.
- Build and publish each client's site in its workspace, and connect that client's custom domain.
- Invite teammates to the org once, then grant them access to just the client workspaces they work on.
Best for: agencies that bundle hosting and site management into their retainer and want a single, predictable bill.
Gating access per workspace
Even though everything lives under your one organization, access is granted per workspace — so each teammate or client only sees the workspaces you give them, and nothing else.
- Invite once, scope access. Members are invited to the organization a single time, then granted access to only the specific client workspaces they work on.
- Clients see only their own site. Give a client access to their workspace alone — they'll never see your other clients' sites, assets, or work.
- Contractors stay contained. Bring in a freelancer for one project and limit them to that single workspace.
- Roles control what they can do. Combine per-workspace access with roles to decide who can edit, publish, or just view.
To manage this, open your Organization settings → Members, then grant each person access to the workspaces they need. See Working with a Team for the full invite flow.
Setup 2 — Your client pays (separate organizations)
If you want the client to own their subscription and pay for their own site, the only way to do that is to set them up in their own organization. Billing lives at the organization level, so a separate bill means a separate org.
- The client owns the plan. Their organization carries its own subscription and payment method.
- Clean ownership. If you ever part ways, the site, domain, and billing already belong to the client — nothing to untangle.
- You can still collaborate. Get invited into the client's organization to keep building and managing their site.
Agencies running many client-owned orgs can use a parent organization with child organizations — typically one child org per client. Entitlements inherit from the parent, so plan features flow down to each client org while billing stays separate.
How to set it up
- Have the client create their own organization (or you create it and transfer ownership to them).
- The client adds a plan and payment method to their org.
- They invite you into the org so you can build and manage their site.
- Connect the client's custom domain in their workspace.
Best for: agencies that hand the site off to the client, or clients who require the subscription in their own name.
Handing a site over to a client
Started a client on your own org and now want to move them to their own billing? You can transfer a workspace to a different organization without rebuilding anything:
- Make sure you're an admin of the destination organization.
- Open the workspace you want to move and go to its details / settings.
- Choose Transfer and select the client's organization.
The workspace — with its sites, documents, and assets — moves under the new org's people and billing.
What's Next?
- Learn the layers — Working with a Team covers organizations vs. workspaces in detail.
- Connect client domains — See Custom Domains to point each client's domain at their site.
- Lock down access — Review Advanced Controls for your Organization.
- Get help — Check the FAQ & Troubleshooting page or email support@ploy.ai.

Best for: agencies that bundle hosting and site management into their retainer and want a single, predictable bill.