Which account and entity hold the permission
A permission attaches to whoever the supplier contracted with. That is usually an account and an entity, and both are chosen by whoever signed up, often with a corporate card and no thought about either. As of 2026-09-12.
| Fact | What it can decide |
|---|---|
| Which legal entity holds the subscription | Whether a territorial condition is satisfied |
| Which account exported a file | Which grant was in force, on per-seat products |
| Whether a contractor used their own account | Whether anything can be passed to the client |
| Who can still log in | Whether the history is retrievable at all |
Inclusion rule. Facts about accounts and entities that published permissions turn on, and that nobody records unless asked to. Order. From the fact that decides a licence condition to the one that decides whether evidence survives.
1The entity question is invisible until it is expensive
Where a licence is limited by territory, the operative fact is usually where the licensee is established rather than where a campaign runs. With offices in several countries, that depends on which entity holds the account.
Nobody makes that decision deliberately. It is made by whichever team signed up first, and it is worth confirming before a licence with a territorial condition goes into a pipeline.
2Contractors are the common failure
A freelancer generating on their own subscription is passing on a permission they hold, and most documents say nothing about whether that is allowed. The work ships and the chain has an undocumented link.
It surfaces when the contract ends: the brand holds an asset whose permission lives in somebody else's account. Fixing it at the briefing stage costs one sentence in a purchase order.
3Access is part of the record
An account nobody can log into takes its history with it. Generation histories, version trails and export dates are all inside the supplier's product until somebody exports them.
That argues for keeping deliverables and their metadata outside the tool, and for knowing who holds the credentials before a project rather than when a question arrives.
4Where the vendor statements are kept
The mechanics above apply to anyone. What a given vendor has committed to in writing is held on the register instead, each line with the plan page it came from and the date it was checked.
An explainer, not an entry in the register. Vendor statements are held, with their sources, on commercial use, and nothing on this page is legal advice. Related: Input logs, Briefing a freelancer.
5From the making side
Alongside the terms behind “Which account”, SceneMixer's guides describe the work itself this way:
The final cut ends on an end card: your main image plus four lines — Brand, Product name, Tagline, Call to action. The first two are read from your photo and your brief; the tagline and call to action are written with the script.
SceneMixer, The End Card (read 2026-10-13)
The music runs across the end card and comes to an end with the film.
SceneMixer, Where the Music in an Ad Video Comes From — “Does the end card have music?” (read 2026-10-13)