Every booking means admin work
Someone makes the folder, the project, the invites and the share links — by hand, for every client.
Every booking becomes a client folder with the right people in it. Producers deliver, clients review and download, and nobody swaps email addresses.
Someone makes the folder, the project, the invites and the share links — by hand, for every client.
Once a link goes out by email, contact details travel with it, and the agency is out of the conversation.
To know what is waiting on whom, someone clicks through project after project.
Set it up once. After that, a new client is a folder, a project and two invitations — created the moment they pay.
Your booking form, calendar or shop fires the hand-off — Typeform, Calendly, Stripe, anything Make or Zapier can hear.
Through the API or your AI assistant: find the client’s folder or create it, then a project for this order inside it.
The producer joins as a member, the client as a guest — one invitation each, safe to repeat.
The client plays, comments on the exact second and downloads the final files. Nobody on your team had to touch it.
What lands in Pibox
Flip them once for the whole team. They hold in every project, for every producer and every client.
Members see names, not e-mail addresses. You choose if that ever changes.
Hide the project chat from guests: clients see the files and the notes on them, nothing else.
Producers can’t add people to a project; your admins decide who is in.
The structure stays yours — one folder per client, projects inside.
Let producers move a file to “Waiting for review”, or keep statuses to admins.
Allow guests to download originals, so delivery happens where the review did.
The public API covers the whole set-up: find or create the client folder, create the project, invite people with the role they need. OAuth 2 works from Make, Zapier, n8n or your own code.
# 1 · the client's folder (search first, create if missing)
POST /api/v2/groups/search { "query": "Ana Ruiz" }
POST /api/v2/teams/{team_id}/groups
# 2 · a project for this order
POST /api/v2/groups/{group_id}/projects
# 3 · the people, each with their role
POST /api/v2/projects/{project_id}/members
{ "email": "marco@…", "role": "member" }
{ "email": "ana@…", "role": "guest" }Guests in a project do — they get the project, the notes and downloads, so access is tied to a person. For a quick listen, a review link needs no account at all: the client types a name to leave a note.
Not through Pibox: members see names rather than e-mail addresses, the project chat can be hidden from guests, and only admins invite. What people do outside Pibox is up to your agreements with them.
Anything that speaks HTTP and OAuth 2 — Make, Zapier, n8n or your own code. The public API covers teams, client folders (groups), projects and invitations; an AI assistant can drive the same API through the Pibox MCP server.
You pay for your own seats — admins and producers. Clients join as guests and don’t take a paid seat.
Pibox is ISO 27001 certified, projects are private by default, and links can expire. Single sign-on is available for larger teams.

“Pibox is a huge success for both our producers and composers. It saves days of back and forth!”
Damien ChockSenior Director at Universal Music Publishing GroupFree to start. Your clients never need an account to listen.