How to use bulk actions

    Overview

    The Bulk Actions feature allows Admin users to perform multiple customer account actions at once through a simple CSV upload.

    It’s designed to help Operations teams manage incidents such as suspected fraud or compromised accounts quickly and efficiently without needing assistance from Engineering or Development teams.

    Using this feature, Admins can lock or unlock multiple accounts, end all active login sessions, flag accounts for suspicious or compromised behaviour, and more all within the JLP Admin interface.

    Pre-Requisites

    Before performing a bulk action, ensure the following:

    • A valid CSV file containing existing encoded customer IDs (e.g. XXXX-XXXX-XXXX-XXXX)
    • Admin permissions with Bulk Action Import capability enabled
    • The following emails are enabled in your sandbox environment (for testing):
      • Account Locked
      • Account Unlocked
      • Customer Details Updated
      • Suspicious Activity

    Step-by-Step Guide

    1. Navigate to Bulk Actions

    Go to Admin → Operations → Bulk Actions.

    2. Select an action

    Choose from the available bulk actions, including:

    • Lock or unlock customer accounts
    • Activate or deactivate customer accounts
    • Remove bouncing email flag
    • Add bouncing email flag
    • Add suspicious account flag
    • Flag account for compromised credentials
    • End all active login sessions
    • Enable 2FA and end sessions
    • Remove trusted devices

    3. Upload your CSV file

    Upload a validated CSV file containing the encoded customer IDs.

    A sample file format is available in the pre-requisites.

    4. Optional settings

    • Tick “Send suspicious activity email” (available for specific actions).
    • Add an internal note to record the reason or context for the action.

    5. Run the import

    Click Import to begin processing.

    The job status will update to Complete or Complete with errors once the task finishes.

    6. Verify the results

    • Check a supporter account to confirm the action was successful.
    • If emails were triggered, verify them under Customer Correspondence.
    • Review Customer Events to confirm all notes and actions were logged correctly.

    Tips for Testing

    • Verify customer traits: Check the Account Traits & Related Actions section (e.g. Locked, 2FA enabled) to confirm updates.
    • Test session termination: For “End all active sessions,” ensure test accounts are logged in across multiple browsers to confirm proper logout.
    • Validate trusted device removal: Log into test accounts via web and mobile — both devices should appear as inactive after the bulk action.
    • CSV validation: Test invalid or duplicate IDs to confirm validation errors display correctly.

    Why It Matters

    The Bulk Actions feature helps Operations teams act swiftly during incidents, ensuring security while reducing manual workload. It provides:

    • Faster, more efficient incident response
    • Consistent account management across large datasets
    • Full visibility through customer event logs
    • Reduced reliance on development resources
    Was this article helpful?
    0 out of 0 found this helpful