> Internal, staff-only guidance. Do not direct customers to it. GeoIP settings are managed by Velaro staff.

What this covers

Velaro resolves a visitor's location from their IP address. Staff control how that lookup works globally and can give one customer site its own override (for example its own database file). Moshky can read and change both when the signed-in user is Velaro staff.

Global settings

geoip_settings_get shows the current global GeoIP settings: lookup mode, blob container and file names (country and ISP), whether fallback providers are used and which, cache lifetimes (hits, no-record results, failures) and the provider budgets.

geoip_settings_set changes only the fields you pass. Without confirmed=true it returns a before and after preview and saves nothing. After the staff member agrees, call it again with the same arguments and confirmed=true. The save is audit-logged with the previous values and returns an auditId. To undo, call geoip_settings_set with rollback_audit_id set to that auditId, preview, then confirmed=true; the recorded previous values are restored.

Per-site override

geoip_site_override_get (needs site_id) shows one site's override, or says the site has none and uses the global settings. geoip_site_override_set creates or changes the override (enabled, mode, blob container and names, secret names, MaxMind account id). geoip_site_override_delete removes it so the site uses the global settings. All three follow the same preview, confirmed=true, audit and rollback_audit_id flow. A deleted override is restored with geoip_site_override_set and the delete's auditId.

Secrets are names only

An override refers to secrets by Key Vault secret NAME, never by value. The name must match site-geoip- followed by 1 to 48 lowercase letters, digits or dashes (for example site-geoip-acme-license). Moshky rejects anything else, including any raw connection string or license key, and never shows or stores secret values. Create the secret in the vault first, then pass its name in connection_secret_name or license_secret_name.

When something goes wrong

If velaro-messaging cannot be reached or rejects the call, Moshky reports the error and status instead of showing empty or default values. Tell the staff member the change was not saved and retry or check messaging health.

Access

These tools need Velaro staff access and the Moshky write setting (EnableCopilotWrite) for set and delete. Reads need staff access only.