---
title: "A workspace per brand, a role for everyone"
description: "Organisations hold workspaces, workspaces hold templates and assets, and roles decide who can design, run or review."
url: https://kalpana.one/features/teams
---

# A workspace per brand, a role for everyone

Teams and workspaces. Organisations hold workspaces, workspaces hold templates and assets, and roles decide who can design, run or review.
Availability: live.

## Built for agencies and brand teams
Keep each client or brand in its own workspace, with its own name, logo, members, assets and templates.
- A workspace per brand or client
- Invitations by email
- Roles set per workspace

## Access that follows the role
Owners, Managers, Designers, Reviewers and Viewers each see and do only what their role allows, in the workspaces they belong to. API keys follow the same rules.
- Five roles, set per workspace
- Review-only access for clients
- API keys checked against their owner's role

## Capabilities
- Workspaces: One per brand or client, each with its own templates, fonts, assets and members.
- Roles: Owner, Manager, Designer, Reviewer and Viewer, set per workspace.
- Invitations: Bring in teammates and clients by email.
- Review-only access: Reviewers and Viewers check work without changing it.
- Scoped access: Members see only the workspaces they belong to.
- API keys: Create keys for the REST API on your organisation's API keys page. A key can only do what its owner's role allows.

## FAQ

**Can clients review without editing?**
Yes. Give them the Reviewer or Viewer role in their workspace.

**What can each role do?**
Owners have full access, including members and roles. Managers run production and batches. Designers create and manage templates and assets without running batches. Reviewers review content and outputs without making changes. Viewers have read-only access.

**Do API keys bypass roles?**
No. Requests made with a key are checked against its owner's role in each workspace.