Agents sometimes need a secret to do their work — for example, an access token for an external service or a key for a third-party API. Agent credentials are how a worker asks a person for that secret, receives it in encrypted form, uses it for a bounded period, and has it withdrawn afterwards.
A Customer is the central entity in the FAR module. It represents a financial relationship with a party — the entity you invoice, collect payment from, and manage receivables for. Every customer references a party in the PRM (Party Relationship Management) module, linking the accounts-receivable record to the broader party identity.
Not every change should be merged without a human looking at it first. Human-in-the-loop (HITL) adds approval gates to the agent workflow — high-risk work items pause after the merge request is created and wait for a human to review and approve before proceeding.
An instance transaction represents an approval or rejection action on a sharing instance. When shared data requires explicit consent or verification — from the data provider or another party — the system creates a transaction that must be resolved before the instance can proceed.