Data Rooms and usage controls

Agents and credits guide

Use this guide to understand how Data Rooms provide agent context and how DynamicMail credits track software usage for agent and workspace activity.

Data Rooms Agent tasks Non-cash credits

Credits are software usage units. Agent runs should be reviewed in the workspace before relying on outputs for sensitive decisions.

Step 1 Open Data Rooms and Running Agent Tasks The agent surfaces start from a selected data room where Running Agent Tasks already exposes Manage Agents, Build Agent, and Run Task.

Open Data Rooms first and then use the Running Agent Tasks panel.

  • Manage Agents opens the existing tenant agent management surface;
  • Build Agent uses the already wired builder path;
  • Run Task starts the task in the data room that is currently selected.
Step 2 Use the data room context File selection, uploads, links, members, and data sources provide the context that the agent run works from.

Data Rooms is the room context where documents, links, and follow-up agent threads stay grouped together.

  • documents can be previewed through the existing PDF or DOCX quick preview surfaces;
  • room-scoped tools and data sources stay around the task;
  • the follow-up chat continues in the same run when there is already an active thread.
Step 3 Credits are software usage units, not money Credits are used for platform usage and already appear as Available, Reserved, Last run, and This month.

The current credit controls describe usage inside DynamicMail rather than cash or stored value.

  • Credits are software usage units only for DynamicMail services.
  • they are not cash, stored value, or a deposit balance;
  • the Purchase credits surface and the credits panel show the current usage state without describing a banking or wallet product.
Step 4 Invite grants, admin grants, and purchase readiness Credits can come from invite activation, a manual admin grant, or the existing purchase surface when that flow is used.

Credits can be added through invite activation, admin grants, or purchase flows when those options are available for the tenant.

  • onboarding can add initial software usage credits when the invite policy allows it;
  • the tenant management surface includes a manual grant flow that adds credits after the tenant claims the emailed link;
  • the billing surface already exposes Purchase credits as the next step for purchase readiness and follow-up.
Step 5 Track usage and keep review boundaries clear Credit panels and agent status show operating state while admins remain responsible for sensitive decisions.

This public guidance stays with what is already visible in the UI and leaves more sensitive decisions to admin review, KYC, or support when needed.

  • credit panels expose Available, Reserved, Last run, and This month;
  • agent status, plan mode, and follow-up make the run visible but do not replace admin review;
  • use support or manual review when a workflow affects accounting, compliance, or external parties.