Login Requests

The Requests Page manages OAuth login requests submitted by customers from client PCs. It is the central location for reviewing, approving, and rejecting login attempts.

Pending Tab

The Pending tab displays all requests that are waiting for admin or cashier action. Each pending request shows:

• Provider icon -- identifies which OAuth provider the customer used (Google, Facebook, Apple, X, or Discord).
• Member avatar -- the profile picture retrieved from the OAuth provider, if available.
• Customer name and email -- the name and email address associated with the customer's OAuth account.
• Timestamp -- when the login request was submitted.

Actions

Two actions are available for each pending request:

• Approve -- grants the login request. An optional auto-login toggle is available; when enabled, approving the request automatically starts a session on the client PC without further action.
• Reject -- denies the login request. The customer is notified on the client that their request was not approved.

Pending Count Badge

A badge displaying the number of pending requests appears in the sidebar navigation, providing at-a-glance visibility of requests awaiting action.

History Tab

The History tab shows previously processed requests, including:

• Whether the request was approved or rejected.
• The admin or cashier who handled the request.
• Timestamps for both the original request and the resolution.

Notifications

When a new OAuth login request arrives, the server displays a notification with an audible alert to ensure the cashier is aware of the pending request. This prevents customers from waiting unnecessarily at the client PC.

Real-Time Updates

The Requests Page receives updates in real-time via the TCP event stream. New requests appear immediately without requiring a page refresh and status changes (approval or rejection from another terminal) are reflected instantly.