Deployment Overview for IT Teams

Introduction

This document provides IT teams with an overview of the key steps and considerations for deploying Hi Marley Connect within their organization. The extension is available on the Chrome Web Store and supports deployment on Google Chrome and Microsoft Edge. While individual users can install it manually, most organizations will require a centralized deployment method to ensure consistency and security.

Deployment Guides

For detailed deployment instructions, refer to the following:

• Deploying Hi Marley Connect Through Microsoft Intune (Google Chrome)
• Deploying Hi Marley Connect Using JamF Pro (MacOS Only)
• Deploying Hi Marley Connect Using Google Admin Console
• Deploying Hi Marley Connect Using SCCM (System Center Configuration Manager)

Key Deployment Considerations

Before deploying the extension, IT teams should assess the following:

1. Deployment Method:
   • Microsoft Intune: Recommended for Windows environments using Microsoft Endpoint Manager
   • Google Admin Console: Ideal for managing Chrome browsers in a Google Workspace environment
   • Group Policy (GPO) for Edge: Suitable for organizations using Windows Active Directory with Microsoft Edge
   • JamF Pro: Suitable for organizations using MacOS
   • SCCM: Ideal for organizations utilizing System Center Configuration Manager (now know as Microsoft Endpoint Configuration Manager - MECM)
   • Other MDM Solutions: If using an alternative Mobile Device Management (MDM) platform, ensure it supports browser policy configuration
2. Security and Compliance:
   • Review extension permissions and ensure they align with organizational security policies
   • Implement whitelisting rules to ensure Hi Marley Connect only scrapes specified URL's for policyholder phone numbers
3. Testing and Validation:
   • Conduct a pilot deployment on a small user group to identify potential compatibility issues
   • Validate that the extension functions as expected with existing security tools and browser configurations
   • Monitor for any performance impact or conflicts with other extensions
4. User Access and Support:
   • Determine whether users will have self-install permissions or if IT will manage the rollout entirely
   • Set up an internal support process for extension-related issues

Monitoring and Maintenance

• Regularly check for extension updates and ensure they are applied automatically
• Monitor user feedback and IT support tickets to address potential issues
• Review policy settings periodically to maintain compliance and security

Support and Feedback

• For any issues that may arise, please email [e-mail] for assistance
• Customers and IT teams are encouraged to reach out to their Customer Success Managers with any feedback or suggested improvements!