Working with a Team

Organizations, workspaces, and how to bring your team into Ploy.

Ploy has two layers. Your organization is the home for your team and your money — it holds your members, their roles, and your billing. A workspace is where the work lives — sites, documents, assets, your brand design system, and integrations. Every workspace belongs to exactly one organization, and an organization can hold as many workspaces as you need.

The part that trips people up: sharing happens at the organization level. When you add someone to your organization, they get access to all of its workspaces — there's no way to share just one workspace on its own today. That's the key thing to keep in mind when you set Ploy up for a solo project, a whole company, or an agency managing many clients — more on it below.

Organizations vs. Workspaces

LayerWhat It Is
OrganizationThe home for people and billing — who is on your team, the roles they hold, and the plan you pay for. An organization owns one or more workspaces.
WorkspaceWhere the work lives — sites, documents, assets, your brand design system, and integrations. Everything in a workspace shares the same memory, brand, and context. Each workspace belongs to exactly one organization, and everyone in that organization can reach it.

Think of the organization as your company and its team roster, and each workspace as a project space that team can collaborate in. Create the organization first, then add workspaces under it.

How access works

Access is granted at the organization level:

  • You invite someone to the organization once and give them a role.
  • Once they're in, they can reach every workspace in that organization — access can't be scoped to a single workspace today.

Because sharing is all-or-nothing at the organization level, the way to keep a client, contractor, or team scoped to only certain sites is to put those sites in a separate organization and invite the person there instead. If everyone should see everything, one organization with multiple workspaces is all you need.

One workspace, or many? Managing multiple sites

A single workspace can hold more than one site — you're not limited to one. So when you have multiple sites, you get to choose: keep them together in one workspace, or split them into separate workspaces.

Keep sites in one workspace when…

  • They belong to the same brand or product and share a design system, assets, and integrations.
  • The same people work on all of them — there's no need to separate access.
  • You want everything for that brand in one place (e.g. a marketing site alongside a docs or careers microsite).

Use a separate workspace when…

  • The sites belong to different brands or clients that shouldn't share a design system or assets.
  • You want everything for that brand in one place, with shared memory and context so the AI always knows where changes belong.
  • You want clean separation for organization's sake, or the option to hand a workspace off to a client later.

Rule of thumb: when you're managing genuinely separate sites — different brands, different clients, or different teams — a new workspace is usually the best way to do it. Reach for multiple sites in one workspace only when they truly belong together.

Choosing a Structure

How you set things up depends on who you are:

You are…Recommended structure
A freelancer / soloA single personal organization with one or more workspaces. The org stays in the background — you just work in your workspace.
A companyOne organization for the company, with as many workspaces under it as you need (e.g. one per brand, product, or site). Team members are invited once to the org and can reach every workspace in it. If some sites need to be shared with different people, put those in a separate organization.
An agencyA parent organization with child organizations — typically one per client. Entitlements inherit from the parent, so plan features flow down to each client org.

Inviting Your Team

Team members are invited at the organization level, then given access to the workspaces they need.

  1. Open your Organization settings from the account menu.
  2. Go to the Members (People & Access) section.
  3. Click Invite and enter each person's email address.
  4. Assign them a role to control what they can see and do.
  5. They'll receive an email invitation — once accepted, they appear in your organization and can collaborate in every workspace under it.

Tip: Inviting someone to your organization shares every workspace in it with them. If you need to share only some sites, keep those in a separate organization.

Roles

When you invite someone, you assign them a role. The role decides how much they can change — not just the content, but the infrastructure your sites run on. Most people should be Members; reserve Admin for the few who manage your account and domains.

RoleWhat they can doBest for
MemberBuild, edit, and publish content on the sites and workspaces they're given access to — but cannot change infrastructure like custom domains, billing, or member access.Designers, writers, marketers, and contractors doing day-to-day work.
AdminEverything a Member can do, plus managing infrastructure — inviting and removing people, connecting custom domains, and adjusting account settings.Trusted teammates who understand your site and domain setup and can make informed decisions about it.

Rule of thumb: invite everyone as a Member by default, and only grant Admin to people who genuinely need to manage domains, billing, or who's on the team. It's the simplest way to keep your infrastructure safe.

Moving a Workspace Between Organizations

Need to move a workspace to a different organization — for example, handing an agency-built site over to the client's own org? You can transfer it:

  1. Make sure you're an admin of the destination organization.
  2. Open the workspace you want to move and go to its details / settings.
  3. Choose Transfer and select the destination organization.

The workspace — along with its sites, documents, and assets — moves under the new organization's people and billing.

What's Next?