You will not receive any "Allow Notifications" prompts or requests if you are logged in as a WHMCS administrator and viewing a client's account. This applies whether you use the built-in "Login as Client" option or manually log into the client area while an administrator session remains active in the same browser. The system intentionally suppresses these prompts during administrative impersonation to keep client-specific permission flows isolated. To receive the prompts, you must completely log out of the WHMCS administrator area and authenticate directly with the client's own credentials. If prompts are still missing after a direct client login, open the browser's Developer Console to check for JavaScript errors and visit the Browser Notifications page via the shortcut menu in the client area.

Browser notifications in WHMCS let clients receive timely desktop alerts for invoices, support ticket replies, service status changes, and other account events without keeping a browser tab open. The feature depends on the W3C Notifications API, which requires explicit user consent on first use. Testing this consent flow is only reliable when the session matches a genuine client login. Administrator sessions bypass the permission request logic because they are not intended to alter or simulate end-user browser permissions. This design prevents accidental permission grants or denials that could affect administrative workflows or mix client data with admin browsers.

#Understanding the Administrator Session Limitation

WHMCS ties the notification permission prompt to pure client sessions for both security and technical reasons. When an administrator uses "Login as Client," the platform maintains an elevated session token that overrides or skips certain client-area JavaScript triggers responsible for calling Notification.requestPermission(). The same occurs if you log in as a client in one tab while your admin cookies are still present in the browser. This is not a bug but expected behavior. It ensures that only actual clients can set their own notification preferences and prevents administrative users from inadvertently registering push subscriptions under client identities. Recognizing this limitation saves time when debugging notification issues reported by your customers.

#Step-by-Step Guide to Logging In as a Client

  • Fully log out of the WHMCS administrator dashboard. Verify logout by confirming you are redirected to the standard login screen and that no admin navigation elements remain visible.
  • Clear any lingering session cookies if you suspect overlap. This can be done by closing all WHMCS-related tabs or using your browser's developer tools to clear storage for the domain.
  • Open the client login page in a fresh browser tab or window. Use the standard client-area URL and enter the client's email address and password exactly as the customer would.
  • After successful login, navigate to the account dashboard or any page configured to request notifications. The permission dialog should now appear if the browser has not previously stored a permission state for the site.

#Troubleshooting When Prompts Still Do Not Appear

If you have logged in directly as the client and still see no prompt, the browser may have cached a previous permission decision, a JavaScript error may be preventing the request, or the WHMCS template may not be firing the notification code on that page. The original guidance remains: open the Developer Console and look for errors. Common indicators include blocked service workers, mixed-content warnings, or permission-related exceptions. Additionally, confirm the site is loaded over HTTPS, as the Notifications API requires a secure context.

#Opening and Using the Developer Console

  • In Chrome or Edge press F12 or Ctrl+Shift+I. In Firefox use Ctrl+Shift+I or F12. Switch to the Console tab.
  • Reload the client-area page while watching for red error messages. Filter the console output by typing "notification" or "permission" in the filter box.
  • If the console is clean, the permission state may already be set to denied. Visit your browser's site settings to reset notification permissions for the WHMCS domain and try again.
javascript 
Notification.requestPermission().then(permission => {
  console.log('Notification permission:', permission);
});

// Run this snippet in the console while logged in as client to manually trigger the permission dialog

#Direct Access to the Browser Notifications Page

WHMCS provides a dedicated page for managing notification settings. After logging in directly as the client, locate the "Browser Notifications" link in the shortcut menu or navigation. Clicking it takes you to the interface that both displays current permission status and can trigger the Allow prompt if none has been issued. This page is the fastest way to verify functionality without relying on other triggers in the client area. Bookmark it for repeated testing.

The key takeaway is to always reproduce client notification flows from a clean, direct client login. Administrative impersonation will never surface the permission dialog, so relying on it leads to false negatives during setup or support. Combine direct logins with regular developer console checks and permission-state verification to maintain a reliable notification experience for all users. For additional client-area customization options, review your WHMCS template files and language overrides.