In Agency you prepare how you present yourself, organize each client's access and read their reports. Each client is an existing brand, with its projects, footage and identity. You do not need to duplicate the videos. Email contacts belong to that same brand.
Prepare the first client
- Save your agency's display name and the email where you want to receive replies. Messages go out from a verified EditorBrain address, with your display name; not from your own mail domain.
- Select or create the client's brand. Its logo and colors are reused in reviews. The preview lets you check that presentation.
- In Team, invite the editor to the brands they will work on. If they will generate assets, give them a credit limit.
- Prepare a review of the video. Share it explicitly when you want the client to see it; uploading a sample does not share it automatically.
- Create the brand portal and copy its link for the recipient you named.
Your agent still follows the same editing preferences. The plan does not force you to always use a template and it does not change what you already approved.
See what needs attention
The Agency project board gathers each client's work status. You can filter by brand and open the project that needs attention. This lookup is read-only: it does not share versions, resolve comments or send email.
- Open comments: review conversations that are still open.
- Pending changes: editorial corrections on the project that are not handled yet.
- Client approval: an approval recorded on the shared version shown; it does not automatically approve production.
- Current final: production approval still belongs to the current file and context. If it cannot be checked, it shows as unknown.
These signals are read separately. Closing a comment does not prove the video changed; approving a sample does not turn another version into the final. The summary covers the projects on the visible page, not the whole account.
You can ask: "Review the Norte brand's projects and tell me which ones have pending corrections; do not send or change anything." The agent uses editorbrain agency operations --brand ID or MCP agency_status with view: {section: "operations", brandId: "ID"}. It returns 5 projects per page, with a maximum of 5; continue with nextCursor and the same filters when there are more.
Three ways to review
| Access | What the client sees | Identity |
|---|---|---|
| Team invitation | Shared versions of their project | Their account with a verified email |
| Private review link | One specific review | The name and email they declare, without verification |
| Client portal | Active shared reviews of their brand | Access by holding the private link |
The portal groups a project's active shared versions. It does not contain the private history, all of your originals or expired versions. It does not promise notices to anonymous clients when something new is published. Keep its link private; if you rotate or turn it off, open sessions from that portal stop working. A review link obtained separately has its own revocation. Files already downloaded cannot be taken back.
Approvals are recorded on a specific version and keep their origin. A guest signature is not a verified identity and does not automatically approve the final production.
Email to the client
This expansion is prepared as a candidate; whether you can use it depends on the active version of the service. In Agency you choose your workspace's existing logo, the accent, the light or dark logo panel, the signature and the language. You can adjust the subject and introduction of invitations, reviews and deliveries, and check the preview before you save. ES/EN changes the default text; your subjects, introductions, signatures and notes are used as you wrote them, with no automatic translation per contact. Saving settings does not send email.
- Choose the brand and register the authorized contact's name and email. It stays pending; this step does not write to them or invite them to the team.
- Review the invitation and ask for it to be sent. The recipient explicitly confirms that they want the notices. Opening the email does not subscribe them and does not approve videos.
- With the contact confirmed, choose the exact review, check the recipient and the message, and send it when you decide. A delivery needs the current approved final file; a sample or a render link is not enough.
The contact opens that version in the existing viewer, without creating an account or seeing all of your originals. They can unsubscribe. Revoking the contact, withdrawing the review or moving the project to another brand closes the access that came from it; a private link obtained separately keeps its own revocation.
You can send yourself a test to the verified email of your own account, after you review and confirm the send. The test does not accept another address. Notices are individual: there is no bulk send, CC/BCC or open tracking.
The history distinguishes the real send status. Accepted by the provider does not mean delivered to the mailbox. If the result is uncertain, it is not resent by itself. The pending queue can wait and retry a temporary limit the provider confirmed, keeping the same authorized send and checking its context. Retrying a failed receipt requires an explicit action and evidence that the provider did not accept the message. Changing settings, creating a review or approving a video does not send email automatically.
Credits and team
Agency includes up to 15 invited editors, besides the owner. Reviewers do not use those seats. The same person assigned to several brands counts once; pending editor invitations count too.
The editor limit and the brand limit are caps on the shared balance. They do not add credits and they do not multiply the balance per client. An editor limit of zero blocks spending, but keeps the work allowed on their projects. A brand limit of zero blocks generation for that brand; removing it removes that cap.
Monthly caps follow the UTC calendar. Buying credits does not raise a cap. If you downgrade, existing brand caps stay visible and the owner can remove them explicitly. They are not removed by themselves, so you keep control of spending. A generation still needs its authorized budget.
Reports
Choose a brand and a month to download approvals or usage. The approval history keeps who approved at that moment; when an old record has no brand evidence, it is marked unknown.
The credit report covers Tempo, Prism, Vox and Aura. It is not an invoice for your clients and it is not a cost calculation for external providers. Approval CSVs contain personal data: share them only with the people who should have them.
Ask the agent
Review my agency and help me prepare the portal for the Norte brand. Show me what you will review and what access the client will have before you share it.
With the CLI: editorbrain help agencia shows the commands. With MCP: get_task_guide with the topic agencia returns the guide and the available tools. The agent can configure the agency, read reports and share the portal when you ask and its connection allows it. It can also prepare and show an email preview, register contacts and send the specific message you requested. Saved configuration does not authorize new sends.
MCP connected over OAuth allows editing reads and writes; it does not grant collaborator administration. If your connection reports canManageTeam: false, manage members and permissions from Team. Connections with an existing owner credential have additional administrative tools. Do not share keys in the chat to turn them on.
Brand and domain
Agency reviews show the client's brand and your agency name without the EditorBrain logo. The web address stays on EditorBrain until a custom domain is configured and active. The page shows the real availability; checking its status does not turn services on or configure DNS automatically. The display name and reply email do not change the verified sending address. Templates and notices do not turn on a custom portal or mail domain.
See also projects and teams, reviews and plans and credits.