TRANXACT.AI Help

Agentic AI: Tool Grants that hold, the publish prompt, versions and approvals that say who decided

A run is held to the tool grants of the agent version it uses. Fixed arguments win over the model’s, Only when is checked against the tool’s inputs, Calls per run is enforced, Agent and Tool are fixed once a grant exists, a change of grants offers Publish now, versions keep their grants and default model, and approvals show who decided and why.

Agentic AI › Build & Orchestrate › Build › Tool Grants, Agent Versions; Agentic AI › Running › Operate › Agent Approvals.

Tool Grants

  • Fixed arguments (JSON, e.g. {"business_unit_id": "<BU-01>"}) always win over anything the agent chooses for the same name, on every route a call takes.
  • Only when is a condition on what the call sends: one of the tool’s inputs, a comparison (=, <>, <, <=, >, >=) and a value, joined with and / or — for example <amount <= 5000> or <status = 'draft'>. It is checked on save against the tool’s inputs, and a call that does not send the name it tests is refused.
  • Calls per run is enforced for each grant in each run: further calls are refused, counted as Refused calls on the run, and the agent is told why. Empty: no limit of its own; 0: the tool cannot be called.
  • Agent and Tool are fixed once a grant exists; to grant another tool, add another grant.
  • Enabled: untick to withdraw a grant without deleting it — it stops at once, without a Publish. Always ask a person sends every call to Agent Approvals.
  • The grant’s record page shows its limits; History names the grant and its unit; a false yes/no reads “No”; a Yes/No column is filtered by typing Yes or No (true and false are no longer needed).

Publish now or later

  • A run uses the grants its agent’s version was published with. A grant added or changed after publish waits for the next Publish; one switched off or deleted stops at once; and where both exist the stricter terms apply.
  • Saving or deleting a grant asks “Changed since publish”: Publish now publishes a new version through the agent’s own Publish (note “Tool grants changed”); Later leaves it, and the Tool Grants list (Since publish) and the agent’s page go on saying Changed since publish. Somebody who may not change agents is told to ask someone who may.
  • A draft being tried uses the live grants.

Agent Versions

  • Each version shows what it was told (Instructions, Opening instruction) and Tool grants at publish, so a decision months old is read against what was allowed then.
  • A version keeps the company default engine and model it was published with; Agent Versions says “Not set (company default: <model>)” with the Engine.

Agent Approvals

  • Titled “<agent> wants to call the <tool> tool (<code>)”, with the arguments masked. Raised by is whoever started the run.
  • Approve approves at the press. Approver, Decided and Note show who decided, when and why; a declined call is counted as refused on the run.

Elsewhere

  • A record opened from anywhere uses the one Edit form for that record; the record page’s Copy form includes Organizational unit.
  • A workflow’s success rate no longer counts runs waiting for approval as failures.
  • Copy of an agent on an engine this installation cannot run starts at the company default; an Edit that keeps the stored engine and model saves.

How to reuse: agent, tool, unit and condition values in angle brackets are examples; your own appear in their place.