Managing and Securing Your Connected Devices: Step-by-Step Guide

Your Connected Devices page gives you powerful tools to manage account security across all your devices. This comprehensive guide walks you through every aspect of device management, from basic viewing to advanced security practices. Whether you’re securing your account after suspicious activity or simply cleaning up old sessions, this guide covers everything you need to know.

Accessing the Connected Devices Page #

The Connected Devices feature is located in your Security settings. Here’s how to access it:

1. Log into your SMS and WhatsApp messaging account
2. Navigate to the Security section (typically found in your account menu or settings)
3. Click on the Connected Devices tab

You’ll immediately see a list of all devices currently authenticated to your account, displayed as easy-to-read cards with all relevant information.

Understanding the Device List Layout #

The Connected Devices page displays each active session as a separate card. Here’s what you’ll see:

Current Device Badge: Your current device is highlighted with a “This device” badge, making it easy to identify which session you’re actively using.

Device Cards: Each card shows:

• Platform icon (Desktop, iOS, or Android)
• Device name and type
• Operating system and browser details
• Geographic location
• IP address
• Login method (UI or API)
• Login timestamp
• Last activity status
• Logout button for that specific device

Visual Organization: Cards are organized in a grid layout, making it easy to scan through all your active sessions. The current device card is typically highlighted or bordered differently to stand out.

Viewing Device Details #

Before taking any action, review the details for each device:

Quick Scan Method: Start with a quick visual scan:

• Count how many devices are active
• Identify which ones you recognize
• Note any unfamiliar device names or locations
• Check the “Last Activity” status for each

Detailed Review Method: For each device, review:

1. Device Name: Does this match a device you own or use?
2. Platform: Is this a platform you use (Desktop, iOS, Android)?
3. Location: Is this a location where you or authorized users have accessed the account?
4. Login Time: Does this match when you or your team logged in?
5. Last Activity: Is this session currently active or dormant?
6. Login Method: If it shows “API” and you don’t use API access, investigate further

Correlation Analysis: Compare the information across all fields. A device might look suspicious based on location alone, but if the device name, platform, and login time all match your known activities, it’s likely legitimate. Conversely, if multiple pieces of information don’t match, it’s worth investigating.

Logging Out Individual Devices #

Logging out a specific device terminates that session immediately while leaving all other sessions active. This is useful when you want to remove access from one device without affecting others.

Step-by-Step: Logout a Single Device #

1. Identify the Device: Review the device information to ensure you’re selecting the correct session
2. Click Logout: Find the logout button on the device card you want to terminate
3. Confirm Action: A confirmation dialog will appear asking you to confirm
4. Review Confirmation: The dialog shows which device will be logged out
5. Complete Logout: Click “Yes, logout” to confirm or “Cancel” to abort

What Happens: Once confirmed:

• The selected session is immediately terminated
• That device will need to log in again to access your account
• All other devices remain active and unaffected
• If it’s a mobile app session, a push notification is sent to terminate the app session
• You’ll see a success message confirming the logout

Best Use Cases for Single Device Logout:

• Removing access from a specific device you no longer use
• Logging out a device you suspect might be compromised
• Terminating access from a shared or public computer
• Cleaning up sessions from old devices you’ve replaced
• Removing access from a team member’s device when they no longer need it

Important Considerations #

Current Device Protection: You cannot logout your current device from the Connected Devices page (this prevents you from accidentally locking yourself out). If you need to logout your current device, simply close your browser or use the standard logout option from your account menu.

Mobile App Synchronization: When you logout a mobile app session, the app receives a push notification and automatically terminates its session. The user will see a message indicating they’ve been logged out and will need to log in again.

No Warning on Target Device: The device being logged out does not receive advance warning. The session is terminated immediately, which might interrupt someone who is actively using that device. For team accounts, communicate with team members before logging out their sessions.

Immediate Effect: The logout takes effect immediately. There’s no delay or grace period. Make sure you really want to logout the selected device before confirming.

Logging Out All Other Devices #

The “Logout All Other Devices” feature is your one-click security reset button. It terminates every active session except your current one, giving you a clean slate of active sessions.

Step-by-Step: Logout All Other Devices #

1. Verify Your Current Device: Confirm that the device showing “This device” badge is the one you want to keep active
2. Click “Logout All Other Devices”: This button is typically located at the top of the device list
3. Read the Explanation: The interface explains that your current device will remain logged in while all others are logged out
4. Confirm Action: A confirmation dialog appears summarizing what will happen
5. Complete Logout: Click “Yes, logout all” to confirm or “Cancel” to abort

What Happens: Once confirmed:

• All sessions except your current device are immediately terminated
• All other devices will need to log in again to access your account
• Mobile apps receive push notifications and terminate their sessions
• You’ll see a success message showing how many devices were logged out
• Your current device remains fully functional

Best Use Cases for Logout All Other Devices:

• After changing your password and wanting to ensure old sessions are terminated
• When you suspect your account may have been compromised
• After losing a device and wanting to secure your account immediately
• When starting fresh with device management
• After security incidents or suspected unauthorized access
• Regular security maintenance to clean up accumulated sessions

Strategic Use of Bulk Logout #

After Password Changes: Always logout all other devices after changing your password. This ensures that even if someone had your old password, their sessions are terminated.

Security Incidents: If you notice suspicious activity or suspect a breach, logout all other devices immediately. This stops any potential unauthorized access while you investigate further.

Device Loss: If you lose a phone, tablet, or laptop, logout all other devices immediately. Even if the device is locked, terminating sessions adds an extra layer of security.

Regular Maintenance: Consider logging out all other devices monthly or quarterly as a security best practice. This clears out forgotten sessions and gives you a fresh start.

Team Changes: When team members leave or access needs to be revoked, logout all other devices to ensure only current team members can re-authenticate with updated credentials.

Understanding Session Termination #

When you logout a device, several things happen behind the scenes:

Immediate Effects #

Authentication Invalidated: The session token for that device is immediately marked as invalid. Any attempt to use that session will fail.

Server-Side Termination: The server-side session is terminated, so even if the device still has cached credentials, they won’t work.

Database Update: The session is marked as inactive in the system, and it will no longer appear in your Connected Devices list.

Device-Side Effects #

Web Sessions: For web browser sessions, the next time the browser makes a request, it will receive an authentication error and the user will need to log in again.

Mobile Apps: Mobile apps receive push notifications when their sessions are terminated. The app automatically logs the user out and may display a message explaining why.

API Sessions: API sessions are immediately invalidated. Any API calls using that session token will receive authentication errors.

What Users Experience #

When a session is terminated:

• If the user is actively using the device, they may see an error message or be redirected to the login page
• If the device is idle, they’ll discover the logout the next time they try to use the account
• Mobile app users receive a notification explaining they’ve been logged out
• The user will need to log in again with valid credentials to regain access

Managing Sessions for Team Accounts #

If multiple team members access your account, device management requires coordination:

Communication Before Logout #

Before logging out team member devices:

• Notify team members that you’ll be logging out their devices
• Explain the reason (security maintenance, password change, etc.)
• Provide a timeframe so they can prepare
• Ensure they have current login credentials

Identifying Team Member Devices #

Use device information to identify which sessions belong to which team members:

• Device names often include the owner’s name or identifier
• Locations can indicate which team member (if they work from different locations)
• Login times help correlate with team member schedules
• Platform types might indicate team member preferences (e.g., one uses iPhone, another uses Android)

Best Practices for Team Accounts #

Regular Reviews: Schedule regular reviews of connected devices with your team:

• Identify all active sessions together
• Confirm which devices belong to which team members
• Decide together which sessions should remain active
• Establish guidelines for device management

Documentation: Maintain a simple list of authorized devices:

• Device names and owners
• Expected locations
• Platform types
• Purpose (daily use, backup, specific projects, etc.)

Access Policies: Establish clear policies:

• When team members should logout devices
• How often device lists should be reviewed
• Who has authority to logout devices
• Procedures for onboarding and offboarding team members

Password Management: Coordinate password changes:

• When passwords change, logout all other devices as a standard practice
• Ensure all team members have updated credentials before changing passwords
• Use the “Logout All Other Devices” feature after password changes

Security Scenarios and Responses #

Understanding how to respond to different security situations helps you use the Connected Devices feature effectively:

Scenario 1: Unfamiliar Device or Location #

Situation: You see a device you don’t recognize or a location you haven’t visited.

Response Steps:

1. Review all device information (name, platform, OS, browser, login time)
2. Check if the information matches any of your devices or team members’ devices
3. Consider legitimate explanations (VPN, mobile network routing, team member travel)
4. If still suspicious, logout that device immediately
5. Change your password as a precaution
6. Review your account activity for any unauthorized actions

Scenario 2: Lost or Stolen Device #

Situation: You’ve lost a phone, tablet, or laptop that has access to your account.

Response Steps:

1. Immediately logout all other devices to secure your account
2. If possible, logout the specific lost device (if you can still identify it in the list)
3. Change your password immediately
4. Review your Connected Devices list to ensure the lost device is no longer active
5. Monitor your account for suspicious activity
6. Consider enabling additional security measures (2FA, IP whitelisting)

Scenario 3: Suspected Account Compromise #

Situation: You notice unusual account activity or suspect unauthorized access.

Response Steps:

1. Immediately logout all other devices
2. Change your password to a strong, unique password
3. Review all device information to identify the source of compromise
4. Check account activity logs if available
5. Enable additional security features (2FA, IP restrictions)
6. Monitor the account closely for continued suspicious activity
7. Contact support if the issue persists

Scenario 4: Forgotten Public Computer Login #

Situation: You realize you forgot to logout from a public or shared computer.

Response Steps:

1. Open Connected Devices from your mobile phone or another device
2. Identify the public computer session (usually by location or device name)
3. Logout that specific session immediately
4. Verify the session no longer appears in your device list
5. If you can’t identify it clearly, logout all other devices as a precaution

Scenario 5: Too Many Active Sessions #

Situation: Your device list shows many sessions, and you’re not sure which ones are legitimate.

Response Steps:

1. Review each device carefully, correlating all information
2. Identify sessions from devices you no longer use
3. Logout old or unused devices individually
4. If uncertain, logout all other devices and start fresh
5. Only log back in on devices you actively use
6. Establish a routine to review and clean up sessions regularly

Scenario 6: Team Member Device Management #

Situation: A team member has left or no longer needs account access.

Response Steps:

1. Identify all sessions belonging to that team member
2. Logout those specific sessions
3. Change shared passwords if applicable
4. Update access credentials if the team member had API access
5. Review remaining sessions to ensure only authorized devices remain
6. Communicate with remaining team members about the changes

Mobile App Integration #

The Connected Devices feature works seamlessly with mobile applications:

How Mobile Sessions Appear #

Mobile app sessions appear in your Connected Devices list just like web sessions:

• Platform shows as “iOS” or “Android”
• Device name typically comes from the device’s system settings
• Location is determined by the IP address of the mobile network or Wi-Fi connection
• Login method shows as “UI” for app logins
• Last activity updates as you use the app

Mobile App Logout Process #

When you logout a mobile app session:

1. The Connected Devices page terminates the server-side session
2. A push notification is sent to the mobile device
3. The app receives the notification and automatically logs out
4. The user sees a message in the app indicating they’ve been logged out
5. The session disappears from your Connected Devices list

Logging Out from Mobile Apps #

You can also manage sessions directly from mobile apps if your app includes this feature. The process is similar to the web interface, but optimized for mobile screens.

Cross-Platform Synchronization #

The Connected Devices feature maintains synchronization between web and mobile:

• Logging out a web session doesn’t automatically logout mobile apps (unless it’s the same session)
• Logging out a mobile app session from the web interface immediately affects the app
• Each platform (web vs. mobile) maintains independent sessions
• You can have both web and mobile sessions active simultaneously

Troubleshooting Common Issues #

Issue: Can’t See the Connected Devices Page #

Possible Causes:

• Your account might not have access to this feature
• Browser cache issues
• JavaScript disabled in your browser

Solutions:

• Clear your browser cache and reload the page
• Try a different browser
• Ensure JavaScript is enabled
• Contact support if the feature should be available but isn’t showing

Issue: Device Still Shows as Active After Logout #

Possible Causes:

• Browser cache showing stale information
• Delay in session propagation
• The device is actively re-authenticating

Solutions:

• Refresh the Connected Devices page
• Wait a few seconds and check again
• If it persists, the device might have automatically logged back in
• Try logging out all other devices as a more forceful approach

Issue: Can’t Identify Which Device to Logout #

Possible Causes:

• Multiple similar devices
• Generic device names
• Unclear location information

Solutions:

• Review login times to correlate with your activities
• Check IP addresses if you know your network details
• Use the “Logout All Other Devices” feature and start fresh
• Logout suspicious sessions individually and monitor if new ones appear

Issue: Accidentally Logged Out Important Device #

Possible Causes:

• Misidentified device
• Confirmed logout without careful review

Solutions:

• The user of that device can simply log back in
• No permanent damage is done – sessions can be re-established
• For team accounts, notify the affected team member
• Use this as a learning experience to be more careful next time

Issue: Mobile App Not Receiving Logout Notification #

Possible Causes:

• Push notifications disabled for the app
• Device offline when logout occurred
• App not running in background

Solutions:

• The session is still terminated server-side
• When the app next connects, it will discover the logout
• The user will need to log in again when they next open the app
• Ensure push notifications are enabled for better immediate synchronization

Best Practices Summary #

To get the most from your Connected Devices feature:

Regular Reviews: Check your Connected Devices page regularly (weekly or monthly) to maintain awareness of all active sessions.

After Password Changes: Always logout all other devices after changing your password to ensure old sessions don’t remain active.

After Device Loss: Immediately logout all other devices if you lose a phone, tablet, or computer.

Team Coordination: For team accounts, communicate with team members before logging out their devices.

Correlation Analysis: When reviewing devices, correlate all information (name, location, platform, time) rather than focusing on single pieces of data.

When in Doubt: If you’re unsure about a session, it’s safer to logout it. Legitimate users can always log back in, but leaving a compromised session active is a security risk.

Documentation: Keep a simple list of your known devices to make it easier to spot unfamiliar sessions.

Use Bulk Logout Strategically: The “Logout All Other Devices” feature is powerful – use it after security incidents, password changes, or for regular security maintenance.

Next Steps #

Now that you understand how to manage your connected devices:

• Review your current Connected Devices list
• Logout any sessions you no longer need
• Establish a routine for regular device reviews
• Share this knowledge with team members if you manage a team account

For more information about understanding the device information displayed, see our guide on “Understanding Your Connected Devices: A Complete Guide to Device Information and Session Details.“