CapaAgency playbook
Set up a client project, give everyone the right role and one key per site, and hand it over cleanly.
This page is for agencies and freelancers who build on Capa for clients. It puts the pieces from the rest of the docs in the order you need them.
One project per client
Make a separate project for each client. Each gets its own content, media, keys, members and plan, and nothing crosses between them.
Name the project after the client, and set its URL to match before you share any links. Changing the URL later breaks links. See Manage projects.
Build it
- Model the content. Sketch it with the client first: once entries exist, changing a field means converting what is stored. See Build a model.
- Design the editor. Group fields into cards the client's team will understand: "Details", "SEO", "Publishing". See Layout builder.
- Arrange the sidebar. Make a team workspace with a folder per area of the site, and pin the models and entries editors open every day. Make it the project's default. See Workspaces.
- Fill in real content before the handover, so the client starts from a working site.
Give everyone the right role
| Person | Role |
|---|---|
| Your developers | Developer |
| The client's lead, who will own the project | Admin, then owner at handover |
| The client's writers and marketers | Content |
| Stakeholders who only review | Viewer |
Content editors can publish and delete entries, but cannot change models, keys or members. See the full table in Members and roles.
One key per site and integration
Make a key for each thing that reads the project, named after it:
| Key name | Environment | Grants |
|---|---|---|
Website | Production | Read only |
Website preview | Draft | Read only, server-side only |
Mobile app | Production | Read only, with allowed origins if it runs in a browser |
One key per site means you can rotate or deactivate one without touching the others, and Last used tells you which are still in use. Keys belong to the project, not to the person who made them. See Keys.
Keep secrets in the client's hosting, not in your own tools.
Hand it over
- Transfer ownership to the client's lead: Settings > Members, their menu, Transfer ownership. Only the owner can do this, and you stay in the project as an admin.
- Hand over the keys. Give the client the place their secrets live. Rotate any key whose secret passed through your own machines or chat: Developers > Keys, the key's menu, Rotate.
- Walk the editors through it. Send them Your first day.
After the handover
When your work ends, the client's owner or an admin can remove your agency's people, or change them to Viewer for support. Keys keep working: they belong to the project.
Checklist
- Project created, named, URL set
- Models built and fields final
- Layouts designed, default workspace set
- Client team invited with the right roles
- One key per site, named after it
- Ownership transferred
- Keys that left the client's hands rotated
- Editors sent the first-day guide