Approvals: web, e-mail and desktop notifications

When an AI calls a high-risk tool that the device's AI permissions do not allow on their own, WECOMMANDER does not run it. It stores the exact requested action as an approval request and tells the AI to try again once a person decides.

The flow

  1. The AI calls, for example, process_exec with a command. It gets approval_required and an approval_request_id.
  2. Admins and owners are notified. The request shows the device or server, the exact command, file, process or container, and whether it would run as root.
  3. A person approves or denies it.
  4. The AI repeats the same call. The gateway uses the approval once, signs it for that device, and the agent checks the signature before running.

What one approval allows

Where requests arrive

PlaceHow
Web dashboardAI → Approvals lists pending requests with Approve and Deny.
E-mailAdmins and owners get one e-mail per new request with a link to Approvals. The e-mail itself grants nothing; approving still needs your browser session.
WindowsThe Management Center shows each request as a Windows notification with Approve and Deny buttons, and can open its panel automatically. A test notification checks that Windows lets them through.
macOSmacOS notifications from the WECOMMANDER app, and the app's panel.
Linux desktopThe Linux Management Center's Approvals tab and notifications.

Connecting a Management Center

The desktop app signs in through the browser: you approve “Connect this Management Center” with an admin or owner account, and the app receives its own token; your password never enters it. That token can only list and decide approvals, read devices, manage autonomous mode and scheduled tasks; it cannot run device tools. Revoke a Management Center under Approvals, or sign out in the app.

Fewer approvals, safely