Studio is the creative production side of BoostEcom: turning a brand system into concepts, concepts into assets, assets through QC, and QC'd assets into a delivery the brand actually receives.
It maps onto the objects you already have: an organization is the agency, a store is a client brand, a member is a person on the team. There is no second product and no second tenancy.
The chain
Prospect → Client (brand system, Go/No-Go)
→ Concept (avatar, angle, awareness, hooks)
→ Asset (production)
→ QC (checklist, rejection reasons)
→ Drop (delivery)
Each stage has a screen under /<org>/~/studio/:
pipeline, clients, concepts, qc, cockpit. Every one is gated
by permission, so opening the Studio lands you on the first section you
actually own rather than on a wall.
Permissions are not automatic
No non-owner role baseline carries studio.*. An organization that does
no creative work should not hand creative powers to its members just by
virtue of membership.
They arrive two ways: an explicit per-member allow, or a role
preset.
| Preset | Does what | |---|---| | Sales | Qualifies, contacts and closes brands; hands a won prospect to onboarding | | Client Ops | Turns a won prospect into a brand production can work on — brand system, assets, claims, scope | | Creative strategy | Turns the brand system into validated concepts | | Production / QA | Produces approved concepts, runs QC, delivers the drop |
A member can hold several; the permissions are the union.
See Organizations & roles for how presets sit on top of the role baseline.
The Go/No-Go score
A brand is not accepted into production on a feeling. The score is recalculated, never typed in, from eleven conditions, which is what makes it a gate rather than a field somebody fills in to unblock themselves.
Delivering to a brand
A drop is delivered at /drop/<token>, a public URL with no
session. That is deliberate and worth understanding: a brand buying
creative production is not a member of any organization, so the token
is the access control. It is 192 bits, only resolves published
drops, and can be rotated or revoked, which invalidates the old link.
The page is noindex, excluded from the sitemap, and disallowed in
robots.txt.
A brand that is a store in your organization also finds its drops at
/<org>/<store>/studio, read-only, so nobody has to hunt for a link
in an old email.
Studio versus agency permissions
Two namespaces, one boundary. studio.* is the production, and it
is what the platform sells to a merchant, so the org owner holds all of
it. agency.* is the business of running the platform: prospecting,
Go/No-Go gates, production verdicts, per-brand margin. Those seven are
the only family excluded from the owner short-circuit and absent from
every baseline.