A workflow can stop at a person before a step runs, and what they are approving is frozen at the moment the request is raised. Recipients are set when the workflow is authored and checked again at publish.
Publishing rejects a change that weakens a gate which already exists.
The person who started a run cannot approve their own step.
An approval that goes unanswered expires and fails the step rather than letting the work continue.
An administrator can reassign a pending approval, one for one, and the reassignment is recorded.
Connections are scoped to a department
A connection is owned by the organization, granted to a department, and bound into a workflow through a typed slot. Publishing freezes which connection a slot points at, while the grant behind it stays live.
Revoking a department's grant stops workflows that were published months earlier, with no republish needed.
A binding that is missing, revoked or of the wrong type refuses the step instead of falling back to something else.
Credentials are decrypted for a single call and never reach the agent or the builder.
Knowledge bases, with a sensitive tier
Documents are parsed with their tables and layout intact, split into passages, enriched with the context they came from and embedded, so an agent can search them and cite where an answer came from.
Search combines meaning-based and keyword matching, then merges the two rankings.
A knowledge base can be marked sensitive: the builder cannot read it while authoring.
Publishing a workflow that reaches a sensitive knowledge base requires explicit authorization.