Teams & sharing
An organisation lets a team share newsrooms, styles and outputs. Set one up from Organization in the sidebar.
Sharing a newsroom
Section titled “Sharing a newsroom”Settings → Organization → Shared with, then pick an organisation. You’re asked to confirm:
Share this newsroom with Acme? Everyone in the organization will be able to see it, its run history, and its generated videos.
Un-sharing is the same control set back to Private (not shared).
Who can do what
Section titled “Who can do what”| Owner | Org admin | Member | |
|---|---|---|---|
| See a shared newsroom and its videos | ✓ | ✓ | ✓ |
| Edit its settings, series and style | ✓ | ✓ | |
| Delete it, or run its setup | ✓ |
Sharing styles: the part that catches people
Section titled “Sharing styles: the part that catches people”Brand kits, caption styles, script styles, layouts and the rest are shared separately from the newsroom that uses them, and the rules are deliberately asymmetric:
| Who | |
|---|---|
| Read: see it, and point a newsroom at it | Anyone in the organisation |
| Edit, delete, re-share | The person who created it, only |
Why importing exists
Section titled “Why importing exists”Scheduled runs execute as the newsroom’s owner. So a personal template resolves fine for its owner and reads as unset for a teammate looking at the same newsroom.
That’s why picking one of your own styles inside an organisation’s newsroom asks to import it first. Sharing is what makes it work for everyone, not just you.
Defaults stay personal
Section titled “Defaults stay personal”Marking a template as your default is your flag, not the organisation’s. Making one member’s default everyone’s would be a surprising amount of reach for a checkbox; teammates adopt a shared style by pointing their newsroom at it instead.
Videos and scripts
Section titled “Videos and scripts”Anything a shared newsroom produces is visible to the whole organisation, including its run history. Work you make in Studio outside a shared newsroom stays yours.