Sep 22, 2026
Spend Attributed to Whoever Triggered It, Active Days, and Named API Keys
Spend is attributed to the person who triggered it, whatever triggered it: the web app, an API key, a schedule or a run acting on someone’s behalf. Reports count active days rather than only spend, and every row says which region it came from.
Who triggered it
Spend follows the trigger: Workflow spend is attributed to the user who triggered the run, so a bill can be read back to the people behind it rather than to the workflow alone.
Named API keys: A user’s spend splits per API key and the keys are named, so machine traffic is legible instead of appearing as one anonymous total.
Trigger source, labelled and filterable: Usage rows carry the channel that started them, the Workflows report filters and facets on trigger source, and the Users view exposes channel and API key attribution.
Automated work points at a person: A row created by automation, a recalculation driven by a structure change, and a row written on someone’s behalf are each attributed to the person or the automation behind them, resolved through sticky, input and owner fallbacks rather than left blank.
Field calculations counted: A user’s field calculations sit beside their chat counts, and the Users report sorts on them.
Active days, not just spend
Active days per member: The Users activity series carries each member’s active days and the Overview ranks top users by them, so someone who uses V7 Go daily without spending much is visible.
Every action counts: Any recorded action counts toward an active day, and readers and chat senders count as active users on a workflow, not only the people who run it.
Workflows with activity and no spend: A workflow people are using without generating spend appears in the list rather than falling out of it.
Reading a report
Every row says where it came from: The Workflows, Chats and Hubs views show each row’s region.
Hub spend, split your way: The Hubs spend series splits by workspace or by hub.
Creation dates on the dimensions: Workflow, hub and user dimensions carry a created_at, so age can be read alongside usage.
Reports open on the last 30 days: Organization reports default to a 30 day window instead of an arbitrary one.
Chat and files
Hand over a file it asked for: When a run asks for a file, you can provide it in the conversation rather than restarting with the file attached.
Drag files into a hub folder: Files and folders can be dragged into Hub folders directly.
Tool errors reach you intact: An MCP tool error passes its detail through to the chat result rather than arriving as a bare failure.
Fixes and interface
Workflow property drag targets: Dragging a property lands where you aimed it.
Read-only configuration history scrolls: A past configuration can be scrolled through rather than clipped.
Steadier Python runs: Duplicate file mounting in a Python run is fixed, and callers are told that V7Go is already defined.
A skip link and a main landmark: The workspace shell carries a main landmark and a skip link, so keyboard and screen reader users can get past the navigation.
Bounded JSON previews: A large JSON preview tile renders within bounds instead of taking the page with it.
