For agencies
Built for agencies running more than one client
BittuAI keeps every client's assets, team, and approvals separate inside one workspace, so growing from one account to fifty doesn't mean growing a pile of spreadsheets and shared drives alongside it.
This workspace runs on the same Social Hub, Studio, and Signature foundation every BittuAI customer uses — agencies get a multi-client structure layered on top.
Every client has their own place.
Agency workspace
Your client accounts
Northstar
Brand kit ready
Bloomfield
Assets organized
Marlow
Team assigned
Illustrative client workspace
Structure
How your workspace is structured
Every client is a Domain, every platform under it is a Channel, every run of content is a Campaign, and every deliverable is a content item underneath that — click a node below to expand it.
Getting started
Onboarding a new client
The same five steps every time, so a new account is never a one-off scramble:
- 1
Create Client
Add the client as its own space in your workspace.
- 2
Brand Kit
Set their colors, fonts, logo, and tone-of-voice once.
- 3
Invite Contacts
Bring in the client's own reviewers and approvers.
- 4
Create Campaign
Set up the first run of content with a Content Package.
- 5
Assign Team
Put the right editors and account managers on the account.
Access control
Roles that match how an agency actually works
The workspace owner has full control. Every other team member gets exactly the capabilities you choose to grant them, enforced at the database level per person — not boxed into a handful of fixed roles:
| Role | What they can do |
|---|---|
| Owneragency_owner | Full control of the workspace: billing, team members, and every client and campaign in it. |
| Team membersteam_member | Every other teammate gets exactly the capabilities you grant them — any mix of viewing, editing content, approving deliverables, managing channels, managing clients, managing portal access, managing API keys, managing team, and managing billing. No one is boxed into a fixed Account Manager/Editor/Viewer role — access is capability-by-capability, per person, and can be changed any time. |
Approvals
A lifecycle clients can actually follow
Every video moves through the same stages, visible to whoever has access:
Clients only ever see a deliverable once it reaches client review, with a clean way to approve, request changes, or reject — no more approvals buried in an email thread.
One workspace, every client under control
Run every client without the spreadsheet sprawl
Brand isolation keeps client assets from ever crossing over, role-based access keeps your team's permissions matched to their job, and a client-visible approval portal with a full audit trail means nobody has to ask "which version did they approve, again?"