IP Whitelisting
Overview
IP Whitelisting lets account admins restrict which IP addresses can reach Euno — without contacting Euno support. Two scopes are enforced independently:
Interactive
Human sign-ins to the Euno web app (SSO / browser sessions).
Non-Interactive
Machine-to-machine traffic: personal API keys, service accounts, ETL jobs, and CI pipelines.
Each scope has its own list of allowed IP ranges and its own Enforcetoggle. For example, you can restrict which cloud environments your API keys may be called from while leaving browser sign-in open, or the reverse.
IP Whitelisting is rolling out gradually. If you don't see it under Account Settings, ask your Euno contact to enable it for your account.
Prerequisites
Viewing the page requires access to Account Settings (any account member).
Adding, editing, or deleting ranges, and toggling enforcement, requires the Manage Security permission. This is assigned to the Account Admin persona by default.
Where to find it
Navigate to Account Settings → IP Whitelisting
Managing IP ranges
Each scope — Interactive (Human users) and Non-Interactive (M2M / API) — shows:
A status row with enforcement status (Active / Disabled), plus, for Interactive, your current IP address, or for Non-Interactive, allowed/blocked request counts from the last 24 hours.
A table of configured ranges: CIDR, label, (Non-Interactive only) last used, created date, and who created it.
Add a range
Click Add IP range.
Enter a CIDR or IP address — for example
203.0.113.0/24, or203.0.113.10/32for a single IP — and a Label (1–80 characters) to describe it.Click Save.
A given CIDR can only be added once per scope; adding a duplicate is rejected. There is no limit on the number of ranges per scope.
Edit or delete a range
Use the row actions next to a range to Edit label (the CIDR itself is immutable once saved — delete and re-add the range if it needs to change) or Delete (asks for confirmation first).
Search
Use the search box above each table to filter ranges by label or CIDR.
Turning enforcement on or off
Each scope has its own Enforce toggle.
Turning enforcement off applies immediately.
Turning enforcement on with no ranges configured for that scope is blocked, with the error "Cannot turn on enforcement while no ranges have been configured." Add at least one range first.
Turning on Interactive enforcement while your current IP isn't covered by any configured range prompts a confirmation, since doing so will sign you out of your current session. You can confirm anyway or cancel.
Turning on Non-Interactive enforcement while your current IP isn't covered prompts a similar confirmation, since it may immediately block API keys and service accounts calling from IPs that aren't allowlisted.
{% hint style="warning" %} When a scope is disabled, or has no ranges configured, traffic of that type is allowed from any source. {% endhint %}
Recent blocked attempts
Admins with the Manage Security permission see a Recent blocked attempts panel under the Non-Interactive section, listing the most recent requests rejected by that scope's enforcement: source IP, credential identifier (the API key or service account name — never the secret itself), endpoint, and timestamp. Use this to spot legitimate automation that needs a new range added.
Last updated