How to enable device management alerts on Kraken exchange?

Device Management Alert Configuration

1. Log into your Kraken account using two-factor authentication to ensure session integrity before accessing security settings.

2. Navigate to the Security tab located under the main account dropdown menu in the top-right corner of the Kraken interface.

3. Locate and click on the “Device Management” subsection, where all registered devices—including browsers, mobile apps, and API clients—are listed with timestamps and geolocation metadata.

4. Select the specific device for which alerts should be activated; each device entry includes a toggle labeled “Notify on login” that must be switched to enabled status.

5. Confirm the change by entering your two-factor authentication code when prompted; no email or SMS confirmation is required beyond this step.

Supported Alert Delivery Channels

1. Email notifications are dispatched immediately upon new device sign-in if the associated email address is verified and not suppressed in notification preferences.

2. Push notifications appear within the official Kraken mobile application when the app is installed, background-enabled, and linked to the same account credentials.

3. In-app banners display at the top of the dashboard during active sessions whenever a new device initiates authentication from an unrecognized IP or location.

4. No SMS-based alerts are offered for device management events; Kraken exclusively uses encrypted email channels and authenticated push infrastructure.

Session Context Requirements

1. Device alerts only trigger when login attempts originate from previously unregistered user agents or operating system fingerprints.

2. Repeated logins from the same browser instance on a known device do not generate alerts unless the session has expired for over 90 days.

3. Alerts are suppressed if the login occurs from an IP address previously whitelisted in the account’s Trusted IPs list under Advanced Security settings.

4. Geolocation anomalies—such as sign-ins from countries with no historical activity—force immediate alert dispatch regardless of other contextual factors.

Alert Suppression Rules

1. Users cannot disable alerts for devices flagged as “critical access” in enterprise-tier accounts governed by Kraken Pro Business policies.

2. Alerts tied to hardware wallet integrations (e.g., Ledger or Trezor) bypass standard notification logic and route directly to the designated admin email defined in the organization profile.

3. API key usage does not trigger device alerts unless the key is associated with a newly registered client ID that lacks prior authorization history.

4. Browser-based sign-ins using Kraken’s embedded WebAuthn flow omit device alerts if the authenticator has been previously attested and bound to the account.

Frequently Asked Questions

Q1: Do device management alerts work for API-only accounts without UI access?Yes. Alerts activate for any authentication event tied to the account’s API key, provided the request originates from an untrusted origin or carries an unrecognized client signature.

Q2: Can I receive alerts in multiple languages?No. All device management alerts are delivered exclusively in English, regardless of the user’s interface language selection or regional settings.

Q3: Is there a delay between login and alert delivery?Alerts are generated and dispatched within 800 milliseconds of successful authentication completion; no queueing or batching applies to this event type.

Q4: What happens if my email provider blocks Kraken’s alert messages?Kraken does not retry failed email deliveries. Users must verify their email domain’s SPF, DKIM, and DMARC configurations to prevent filtering; push notifications serve as the sole fallback channel.