---
title: "Agencies"
description: "Give each client a workspace with its own templates and members, a role for everyone from designers to reviewers, and credits shared across the organisation."
url: https://kalpana.one/use-cases/agencies
---

# Agencies

Run every client's creative production from one account. Give each client a workspace with its own templates and members, a role for everyone from designers to reviewers, and credits shared across the organisation.
Audience: Creative and performance agencies.

## The problem
Clients pay for ideas. The production eats the margin. Every size, every product, every market, for every client: the work after the idea is where agency hours go.

## Steps
1. A workspace per client: Each client gets its own templates, fonts, assets and members.
2. Designers stay in Figma: Approved frames go straight to the client's workspace, ready to bind to data.
3. Managers run production: Fill the client's product sheet, fix photos, preview every row and generate the campaign pack.
4. Clients review: Invite clients as Reviewers or Viewers to see outputs without changing anything.

## Deliverables
- A workspace per client
- Five roles, set per workspace
- Email invitations for your team and clients
- Shared credits with usage by workspace
- API keys for your own tools

## FAQ

**Do our clients' marketing teams need Figma?**
No. Your designers send frames from Figma with the plugin. Account managers fill rows, preview and generate in Kalpana, and clients review the results there.

**Can I keep clients separate?**
Yes. Each client can have its own workspace with its own members, assets, templates and data. Members only see the workspaces they belong to.

**Can clients review without editing?**
Yes. The Reviewer role can review content and outputs without making changes, and the Viewer role is read-only.

**Can designers run batches?**
Not with the Designer role. Designers create and manage templates and assets; Managers and Owners run the batches. Give each person the role that fits.

**Can we connect Kalpana to our own tools?**
Yes. Create a key on your organisation's API keys page and call the REST API, or connect an AI agent through MCP. A key can only do what its owner's role allows in each workspace.

## Individual workspace for each client

Keep each client in its own workspace, with their brand fonts, templates and assets. Your team works across the workspaces they are invited to, and nothing leaks between clients.

## A role for everyone

Roles are set per workspace, so the same person can manage one client and only review another.

- **Owner.** Full access, including members and roles.
- **Manager.** Runs production: templates, assets, batches and outputs.
- **Designer.** Creates and manages templates and assets, without running batches.
- **Reviewer.** Reviews content and outputs without making changes.
- **Viewer.** Read-only access.

## One account, clear usage

Credits are shared across your organisation, and usage is shown by workspace, so you can see what each client's production costs and plan your billing.

## Plug in your own workflow

Create API keys to run batches from your own tools through the REST API, or let an AI agent run them through MCP. Keys act with their owner's roles, so they never reach further than the person who made them.