Skip to content

Human approvals

In Settings → Options, the Approval before sensitive actions switch turns on Hermes’s native authorisation requests. The owner, an administrator or an external expert can change this setting; only the owner and administrators then answer the requests. When it is off, do not count on an approval before every action. Even when on, this mechanism follows the engine’s own checks and does not guarantee a request for every tool or send.

When a native request exists, it appears in the thread and in the approvals. Review the action, its scope and, where available, the exact command. Also check the recipients, amounts and files involved.

Decline rejects the request. Allow once authorises this run only. When the engine offers them, the neighbouring arrow gives For this conversation and Always for this type, which have a wider scope: do not use them for a review of every operation. To correct the action, decline it and ask for a new draft; a native approval is not a general-purpose editor.

After an uncertain network response, check the status before taking any new action. The absence of a displayed request proves neither an authorisation nor an execution.

Managed email is restricted to your contacts and the direction allowed for each, but an authorised send does not always create an approval. Another connection may follow a different path. To require a review of every message, use a draft-and-human-send process or a service whose control has been verified. Remove any autonomous send access that could bypass it.

See Transparency and sensitive uses to define the scope and test the controls with fictitious data.