Policy decides what finance agents can run
BotDojo keeps finance work inside configured connections, tool permissions, and action policy so routine work can run while sensitive actions stay governed.
Decide what agents can run automatically, what should ask, and which finance actions should never run.
Finance action policy
Routine reads and prep can run automatically while sensitive sends, CFO exports, and ERP write-backs ask or stop based on policy.
Routine automation remains enabled, but broad exports and ERP updates stay disabled until an admin changes policy.
Finance work prepared for action
Each workflow keeps the task, source material, generated artifacts, policy decisions, and monitorable output in one place.
Permissioned connections
Decide which finance systems, files, and tools a workspace can use.
Allow, ask, or deny
Allow safe reads, ask before sensitive sends or exports, and deny risky writes.
Sensitive action gates
Gate customer-facing, CFO package, external export, or ERP-impacting actions when policy requires it.
Task history
Keep prompts, source files, generated artifacts, and policy decisions attached to the work.
Monitorable output
Track artifacts, exceptions, workflow volume, token usage, and run cost by finance workflow.
Delegate finance workflows, not isolated questions
Give BotDojo a finance workflow and get back source-backed output that can run, ask, or stop based on policy.
Allow finance agents to read exports, summarize records, and prepare drafts automatically.
Route sensitive sends, broad exports, and ERP-impacting updates through policy.
Preserve policy history for sensitive tool use and generated finance artifacts.