Notifications and security

Overview

The Notifications and Security sections of Settings let you control two things: which platform emails Ken sends to you, and which devices are currently signed in to your account.

Notifications - Found inside the Profile settings page at /settings/profile. Scroll to the bottom of the page to reach the Notifications section. Toggles here control whether Ken sends you an email when a specific event happens (for example, when a new positive reply arrives or a campaign starts sending).

Security - A dedicated page at /settings/security, accessible from the Settings sidebar under "Security". It shows every active device session, lets you sign out individual devices or all others at once, links to password management, and provides the option to permanently delete your account.

Before you start

• Any signed-in workspace member can view the Security page and manage their own sessions.
• Any signed-in user can manage their own notification preferences on the Profile page.
• Billing-related alerts (payment failures, account suspension warnings, trial-end notices) are mandatory and are not shown as toggles. They are always on.

How to manage notifications

1. Open Settings from the sidebar.
2. Click Profile in the settings navigation.
3. Scroll to the Notifications section near the bottom of the page.
4. Each available notification type is listed with a name and a short description. Use the toggle on the right to turn it on or off.
5. The change saves immediately - there is no Save button in this section.

If the section shows "Could not load notification settings. Please try again later." reload the page and try again. If it shows "No notifications available." the workspace has no configurable notification events at this time.

Notification events

The list of toggles is driven by the backend. New event types appear automatically without a frontend release. At launch, the configurable events are:

• Positive reply - Email you when a lead is classified as a positive reply.
• Campaign launched - Email you when a campaign begins sending.

Billing lifecycle alerts (payment failed, account suspended, resource removal warning, trial ending) are always delivered regardless of your preferences and do not appear in this list.

How to manage active devices and sessions

1. Open Settings from the sidebar.
2. Click Security in the settings navigation.
3. The Active Devices section lists every device currently signed in. Each row shows the browser and device type, the last active time, and the approximate location (city and country).
4. Your current session is marked with a This device badge.
5. To sign out a specific device, click the sign-out icon on that row. A "Device signed out" confirmation appears.
6. To sign out every other device at once, click Sign out all others at the top right of the Active Devices section. Only your current session remains.

How to change your password

The Security page includes a Change Password button under the "Change Password" heading. Clicking it takes you to Profile Settings, where the password field lives.

How to delete your account

The Delete Account section is at the bottom of the Security page.

1. Click Delete Account.
2. Read the warning. Deletion removes your profile, settings, and all associated data and cannot be undone.
3. Type DELETE into the confirmation field.
4. Click Delete Account to confirm. You are signed out and redirected to the home page.

How it works

Notifications

Each notification type is stored in the backend as an event entry with a default enabled/disabled state. When you load the Profile page, the frontend fetches your personal preferences merged with the event catalog in a single API call. Your stored override takes precedence; if you have never toggled an event, the platform default applies.

All configurable notifications ship with their default set to off - no one receives notification emails they did not opt into. When you toggle a preference, the change is saved immediately and applied to future dispatches.

Delivery uses a deduplication system: the backend reserves a log entry before sending each notification. If two processes try to send the same event to the same user at the same time, only one succeeds. A prior failed delivery can be retried, but a successfully sent notification is never resent for the same event occurrence.

Session management

Sessions are managed through Clerk, the authentication provider. The Active Devices list shows only sessions with an active status. When you revoke a session, the server verifies that the target session belongs to your user account before revoking it - you cannot sign out another user's session even if you know their session ID. Revoking your current session from this page is blocked; sign out via the account menu instead.

Security model

Several layers protect the settings area from unauthorized access:

• Company-level settings re-verify your admin role on the server for every mutation, independent of what the UI shows.
• The workspace you are scoped to is carried in a signed cookie that is bound to your user ID. A stolen cookie cannot be replayed by a different user.
• State-changing API routes check the Origin header and reject requests from origins not in the platform allowlist. A missing Origin header is treated as a failure, not a bypass.

Troubleshooting and debugging

Notification toggles show "Could not load notification settings."

• Likely cause: A transient API failure on the /v1/notifications/preferences endpoint.
• What to check: Reload the page. If the error persists, check whether the backend is reachable and the user's JWT is valid.
• If the section loads but shows all toggles as off, the user's preferences were intentionally reset to off at the feature rollout. The user needs to turn on the toggles they want.

A notification email was sent even though the toggle is off.

• Likely cause: Billing lifecycle notifications (billing_* event keys) are mandatory and bypass user preferences. They are not shown in the UI.
• What to check: Identify the event key in the notification email footer. If it starts with billing_, it is expected behavior.
• If the event key is not a billing event, check whether the preference row in notification_preference matches the user's intended setting and whether the dispatch log shows a Sent status for an event that predates the toggle change.

A notification email was sent twice for the same event.

• Likely cause: This should not be possible under normal circumstances. The backend uses a unique database constraint on (event_key, dedupe_key, user_id) to prevent double-send.
• What to check: Look at notification_log for duplicate rows on the same dedupe key. If both rows show Sent, the dedupe key itself differed between the two dispatches, which means the event was dispatched twice with different identifiers - a backend issue, not a preferences issue.

The Active Devices list is empty or shows "No active sessions found."

• Likely cause: All sessions for the user are in a non-active status (expired or revoked), or the Clerk session list call failed.
• What to check: The list only shows sessions with status === 'active'. If a user was recently signed out globally, all sessions may have been revoked. Ask the user to sign in again.

"Failed to load sessions" toast on the Security page.

• Likely cause: A transient Clerk API error.
• What to check: Reload the page. If it recurs, check Clerk service status.

"You do not have access to revoke this session." error.

• Likely cause: The session ID being revoked does not belong to the signed-in user.
• This is a security guard, not a bug. It fires if a crafted request targets a foreign session.

"Cannot revoke current session" error.

• Expected behavior. A user cannot revoke the session they are currently using from the Security page. Direct them to use the sign-out option in the account menu.

Delete Account button is disabled or the confirmation does not unlock.

• The Delete Account button in the confirmation dialog only becomes active when the confirmation field contains exactly DELETE (uppercase, no spaces). Remind the user to type it precisely.

FAQ

Are notification emails opt-in or opt-out by default? All configurable notifications (positive replies, campaign launched) default to off. You must enable them before Ken sends you those emails. Billing alerts are always on regardless of your preferences.

Can I unsubscribe from billing emails? No. Payment failure notices, suspension warnings, and trial-end reminders are mandatory and cannot be disabled from the settings page.

Can an admin change another user's notification preferences? No. Notification preferences are scoped to the signed-in user via their login token. There is no way to read or change another user's preferences from the UI or the API.

Can I sign out all my sessions at once, including the one I'm using now? "Sign out all others" keeps your current session active and revokes everything else. To sign out your current session as well, use the sign-out option in the account menu and then return to Settings to revoke any remaining sessions.

What data is deleted when I delete my account? Account deletion removes your profile information, your personal settings and preferences, and all data associated with your user account. It cannot be undone. Workspace-level data (campaigns, contacts, inboxes) is not affected unless you are the sole member.

Does revoking a session on the Security page sign the person out immediately? Yes. The session is revoked server-side via Clerk as soon as you confirm. Any request made on that device after revocation will be treated as unauthenticated and the user will be redirected to sign in.

Related articles

• Managing users
• Profile settings
• Billing and plans