Teammates can now make films right on the website

When we built teams, we built them where our busiest makers worked: inside AI assistants, through our connector. A member's requests ran in the owner's workspace, and every tool checked their role and their monthly spending cap.

The website never heard about it. Every page looked up films by the signed-in person's own account. A member could make a film for the team from a chat, open the website, and find nothing. The rules existed; they simply stopped at one door.

The change starts with a question every page now asks before anything else: who is acting right now, and for whom? When a member picks the team's workspace, the server first checks that the membership is active, then remembers the choice for that browser. A stale or invalid choice is never an error; it quietly brings you back to your own account.

This choice is kept apart from the one your assistant uses. You can work in the team's workspace on the website while your assistant stays in your personal one, or the other way round, and the two never fight.

From that single answer, everything else follows. The dashboard, the sites list, the editor and the film page show the owner's films, limited to the sites the member may see. A small bar at the top says whose workspace you are in, your role, and your own cap.

Reading films is the easy half. The careful half is spending: a member's render is paid from the team's balance, yet it must also respect the member's own monthly cap. Every paid action now follows the same three steps.

• Before the work starts, the amount is reserved against the member's cap.
• The work runs: a render, a re-render, a caption resync, an AI image, a pack of films.
• Afterwards the reservation is settled to what was really used, and the spend is written to the team's activity log under the member's name.

That way a member can never overshoot their cap halfway through a render, and the owner can always see who spent what.

A good permission system is mostly about what you do not show. The film page now hides the buttons a role cannot use, instead of letting someone click and fail. Deleting a film is for owners and admins. Members see their own cap, never the owner's balance.

The settings that change what the owner pays for stay with the owner: the brand kit, the plan, recurring shows and connections. The team page now acts on the chosen workspace, so an admin can manage the team from the website as well. Your personal media library stays personal. The plans that include teams are on pricing.

A rule like this is only as strong as the next page someone writes. So we added a test that sweeps every project route and fails if it finds one that looks films up by the signed-in person's own account, the old way. A second test runs over real requests against a local server and walks through each role: what it can open, change and spend.

The principle we wrote down is short: the website and the assistant must always agree. Any new page that reads or spends on a film goes through the same helpers, or the build says no.

If you work with others, you can now pick up where a teammate left off, whichever door they used. Start a film in Claude, review it on the website, hand it to a colleague who prefers clicking to chatting. The same films, the same roles, the same caps, everywhere.

If you mostly work through an assistant, nothing changes for you, except that your colleagues can finally see your work. You can connect an assistant from /assistants.