One website, one media bank for everyone on it

Since October, several people can work on the same website. An owner invites managers by email, each manager gets shared access with their own credits, and every film is linked to the website it shows. A manager sees the site's films, and the owner sees the films managers made on it.

The media bank had not followed yet. It still read one thing only: the account that created each item. So two people working on the same site each held half of its materials. One person's captures, generated images and music beds were invisible to the other.

The rule we set ourselves was short: everyone with access to a website has all of its assets and films at hand. An asset belongs to a website, and to the person who made it.

A media bank is not one screen. The same items are read from many places, and a change that touches only the visible page leaves the others behind. We changed the rule at every door:

• the bank page, and the pickers in the film editor;
• the assistant's view, so Claude or ChatGPT working for a manager through list_assets sees the site's whole bank;
• references, when a scene points at an image or an object already in the bank;
• the music beds you can choose for a film;
• what a scene reads about the asset it shows;
• the planner's reusable site images, the pictures of a website it can place in a new film.

That last door matters most for quality. A film planned for the owner can now use a capture a manager made last week, instead of shooting it again or settling for a designed card.

Sharing what people can see is not the same as sharing what they can change, so we kept the two apart on purpose.

Reading follows the website. For someone with shared access, the bank holds their own items plus every item on a website shared with them, as owner or manager. For a member of a team workspace, it holds their own items plus the owner's items on the sites the workspace covers.

Changing stays with the person who made the item. Tagging an asset, changing how it is shared or deleting it is still reserved for its creator. A small “shared” badge marks everything else. Nobody deletes a colleague's capture by accident, and nobody has to ask for a file they can already use.

A sharing rule is easy to get quietly wrong. A missing item does not look like an error; it looks like an empty bank. So we wrote the test around people rather than pages.

It builds a small make-believe team of members and websites, then checks the bank from each point of view: the owner, a manager, a team member, and someone with no access at all. It walks through every door listed above.

It also checks what must not move. Tags, sharing and deletion still refuse anyone but an item's creator, whoever else can now see it. A change that widens reading should never widen writing along with it.

Most of what goes into a PageToVid film comes from a website: its pages, its screenshots, its colours, its product images. The account is who pays and decides; the website is what the film is about.

Films have followed the website from the start, and now the materials that make them follow it too. A team builds one bank per site over time, and every new film starts from everything anyone has already gathered. The second film on a site is easier than the first, and the tenth easier still.

If you work on a site with others, the team features are described on /features, and you can start the next film at /new.