Studio
Keep every creative project, brand kit and version in one place.
One brand kit as your default, projects that move through a small set of real states with every step recorded, and media registered by reference so nothing is guessed at.
What Studio is
A brand kit holds your palette, fonts and voice guidelines; exactly one is the tenant default, so every project has one place to check what's on-brand.
A project moves through a small set of real states — draft, in review, approved — and every move is recorded, not implied by a filename.
Media is registered by reference: a link to a file you already host. There is no storage provider in this build, so nothing is uploaded here.
Plan and run approved pre-recorded webinar sessions from reference media: a webinar seals a version, requests approval, and only then can it be scheduled and delivered to the canonical Marketing event's registrants.
Work it supports today
Each of these starts on a real page in the product. Nothing here is planned or promised.
Set up your brand kit
A default brand kit with a palette, fonts and voice guidelines every project can check against.
- Open Studio, then Brand.
- Create your first brand kit — it becomes the default automatically.
- Add the media assets it references.
Start a project and take it to review
A project that has moved from draft to in review, with an approver's decision recorded on it.
- Open Projects and start one, from a template or from scratch.
- Work it while it's in draft.
- Send it to review when it's ready.
- An approver holding studio.approve decides it.
Register media you already host
A media asset listed for projects to reference, without uploading anything.
- Open Media.
- Add a link to a file you already host, and name its kind.
- See it listed and available to reference from a project.
By hand: send a project to review
Rowan Faast, an illustrator at Halden Rowe Joinery, finishes a webinar-production project and wants marketing's sign-off.
- Rowan opens Studio, then Projects, and opens the webinar project.
- It's in draft, so he requests review.
- The project moves to in review; an approver holding studio.approve decides it.
- Once approved, its state reads approved, with the earlier version kept.
Fictional names. Start here: /studio/projects
Or let Noc do it
Noc plans the steps, previews every effect, asks before anything irreversible, and hands back one receipt. Autopilot is off by default.
“Noc, cancel the generation request I no longer need, and move this project back to draft since the review didn't approve it.”
- Read the project's current state. Nothing is written.
- Cancel the generation request you asked for yourself. This is not undone, so Noc asks first.
- Move the project from in review back to draft. This can be undone, but Noc still previews the move and asks first.
- Before anything irreversible
- Before it cancels the request or moves the project, Noc previews the exact effect and asks for your confirmation first.
- What you get back
- One receipt for each step that ran, and one for the whole request, so you can see exactly what changed.
Capabilities this plan can use: 3. Each is registered, permission-bound and previewed.
What stays in your hands
Your permissions decide, every time
Reading needs studio.read; changing needs studio.write; deciding a review needs studio.approve. Noc carries your permissions and never more.
Approval stays a person's decision
Requesting and deciding a review happens on the project's own page; no template or capability approves a project on its own.
Nothing is generated in this build
A generation request records what was asked for; with no provider connected, it is cancelled or left as recorded, and no image, video or copy is ever fabricated.
A webinar plans and rehearses, it does not stream
Recording, media storage, external invitations and reminder delivery are all unavailable here. A live session is prepared and rehearsed, and its audio and video connect only through a streaming provider the operator has configured; without one, its transport stays blocked_no_provider. Live captions come from the presenter's browser only when the presenter turns them on, or, as optional Premium captions charged in Noc tokens, from server transcription the host chose and confirmed.
The honest states
What the product really shows when there is nothing yet, when it refuses, and where this build stops.
What you see first
A new workspace has no brand kit yet
There is no sample brand kit; the first one you create becomes the tenant default automatically.
When something is refused
A stage move outside the state machine is refused
Asking to move a project to a state its own machine doesn't allow is refused, with the reason, and nothing is written.
Not available in this build
No image, video or copy is generated by AI
With AI generation unavailable, a request becomes a stated refusal at once, and no asset is ever fabricated in its place.
Not available in this build
No webinar is ever actually streamed
Recording, media storage, external invitations and reminder delivery are unavailable; live audio and video connect only through a streaming provider the operator has configured, and nothing is recorded. Live captions come from the presenter's browser only when the presenter turns them on, or, as optional Premium captions charged in Noc tokens, from server transcription the host chose and confirmed; only their text is kept, never audio.
Not available in this build
Brand mentions come from a closed list of sources
Mentions are searched on Hacker News and Mastodon hashtags with no setup, and on Bluesky, X and Google News only through the workspace's own account, where the platform operator has turned on key custody. Reddit, LinkedIn, Facebook, Instagram, Threads, TikTok and Google News RSS are not watched, and nothing is ever posted.
Not available in this build
Only the free sources are ever checked on a schedule
Bluesky, X and Google News use the workspace's own accounts, so they are searched only when a member presses Check now. Where the platform operator has turned hourly checks on, a member can have a monitor check Hacker News and Mastodon up to once an hour (each hourly run checks at most 3 monitors of a workspace, so more take turns), and expired mentions are deleted in hourly batches, usually within about an hour of expiring (a busy hour can push some to the next). Otherwise every search waits for Check now, and expired mentions are deleted a batch at a time whenever anyone in the workspace opens Mentions or runs a check. A mention stops showing after its source's retention period either way.
Next
To see Studio you need a membership in a workspace. Acting needs the permissions your administrator grants.