Bring your whole team, keep one wallet

A shared password works for a week. Then someone renders a film for the wrong client, a freelancer still has access after the project ends, and nobody can say who approved the version that went live.

What agencies and marketing teams asked for was simple to say: let several people make films on one account, without giving each of them the keys to everything. One company pays, several people produce, and a client somewhere has to say yes before a film goes out.

Our first rule was that a solo maker should feel none of this. Every account already is a workspace of one. It has no members, nothing new appears on screen, and not a single extra database query runs on your films.

The workspace only shows itself when you invite someone. Because every existing film already belonged to its owner's workspace, nothing had to move on the day teams arrived: your films stayed exactly where they were, visible to exactly the same person.

A workspace has six roles, each with a clear job:

• owner and admin run the workspace and its members
• editor makes and changes films
• reviewer watches, comments and approves
• viewer watches and nothing more
• billing looks after the balance

Access narrows in three steps: the workspace, then a website, then a project. A freelancer can be an editor on one client's site and simply not see the others.

Every permission goes through one single decision in our code, can(actor, action, target). When it says no, it says why: either your role lacks that permission, and the answer names it, or the site is outside your scope. One place to read, a hundred checks holding it, and no guessing for the person who was refused.

A team shares one wallet. When a member renders a film, it is paid from the workspace owner's balance, which matches how agencies actually buy. The number of seats depends on the plan, and the pricing page has the current figures.

The owner can give each member a monthly cap. The cap is reserved when a render starts and settled to what it really used when it ends, and the cap and the balance move together in one step, so two films started at the same moment cannot both slip under the same limit. A member who reaches the cap gets a plain message saying so, never a mysterious failure.

Many people make their films through an AI assistant connected to PageToVid, so teams work there from day one. Every call a member's assistant makes passes the same gate, with a rule for each tool. A new tool starts closed to members until we decide what it should allow, and the gate works out which website a call is about from whatever it carries: a page address, a film, a show or a format.

A member picks which workspace they are working in, per request or once on their team page. Eleven new tools came with this release: invite, list, update and remove members; create a review link, request approval, approve or request changes; list and add comments; and read the activity log. Invitations arrive by email and are accepted by signing in with the invited address, or through the link itself. The assistants page shows how to connect one.

The person who says yes is often not a PageToVid user at all: a client, a manager, a legal reviewer. For them there is now a review page. You send a link, they open the film, and they leave comments pinned to the exact second they mean, signed with the name they type.

Links expire on their own, so one forwarded months later stops working. An editor can ask for approval, a reviewer approves or asks for changes, and every step lands in the activity log. When someone asks who signed off on this version, the answer is one click away.