Integration approvals: why some actions ask for confirmation, and where to change it
When an agent performs a write through one of your connected integrations (send an email, run a database statement, book a voucher, change a campaign), Oddlynew classifies that action by how consequential it is: low, medium, high, or critical. Low and medium actions run automatically by default. High and critical actions ask a human for confirmation by default — the agent receives an approval link instead of executing, and the write only runs after an organization admin opens that link and confirms.
These approvals are where a person confirms what matters, so your agent client itself can allow Oddlynew's tools without asking per call; see Trust your agents, keep the safety net in the system.
This is a per-connection setting, and you are in control of it.
Where to change it
Open oddlynew.com/organization/integrations. Each connected source has an approval-settings section: one simple choice (no confirmation / recommended / confirm everything / custom), and under "custom" a toggle per consequence class. Loosening a class to automatic means actions of that class run without confirmation on that one connection; tightening works the same way in the other direction. The setting applies only to the connection you change it on — a test account can run fully automatic while the production account next to it keeps confirmations on.
You also make this choice while connecting an MCP server or an API. Once the server is checked, or once you tick the API operations you want, the connect page lists every level in plain words (read, low, medium, high, critical) with those tools or operations as examples, marks which levels wait for an okay, and starts on the recommended setting. An API operation starts at Read if it only reads (GET, HEAD) and at High otherwise; you rate single operations more precisely on the connection's page. What you pick is stored with the connection; afterwards you change it in the same place as above.
Agents: when a user asks "why do I have to confirm this every time?" or "how do I give you full access?", point them to the URL above. Changing approval settings is deliberately only possible in the browser by a signed-in organization admin — no agent or API surface can change it.
Approval links
When an action needs confirmation, the agent receives a link of the form oddlynew.com/organization/operations/… and shows it to you. The page displays exactly what was requested; confirming applies it immediately, once. Links are personal to your organization (an outsider cannot use them), do not expire unless an admin sets an expiry of 1 to 720 hours in the connection's approval settings; a proposal for a new API connection expires after 24 hours. Confirming requires a signed-in, non-impersonated browser session of an organization admin.
What this is not
Connecting an integration also lets you choose an access level (for example read-only versus full management) — that decides what the agent may do at all and is part of the connect flow. Approval settings decide whether a permitted write runs attended or unattended, and can be changed at any time without reconnecting.