This is a comprehensive report on the ConnectWise Manage login ecosystem . This report covers the anatomy of the login process, security architectures, common troubleshooting scenarios, and administrative controls.
Report: The ConnectWise Manage Login Ecosystem Executive Summary The login process for ConnectWise Manage (formerly ConnectWise PSA) is the critical entry point for an organization’s operational data. Unlike simple static web logins, ConnectWise Manage employs a multi-faceted authentication system that supports internal users (staff), external users (clients via the Client Portal), and third-party integrations (API keys). With the shift toward ConnectWise Identity (Single Sign-On), the login landscape has moved from localized credential management to cloud-based Identity and Access Management (IAM).
1. Architecture of Login Access ConnectWise Manage does not have a single login door; it utilizes three distinct authentication pathways depending on the user type and intent. A. Internal User Login (Staff)
Purpose: Access for technicians, administrators, and finance staff. Current Standard: ConnectWise Identity (SSO). connectwise manage login
ConnectWise has migrated most users to "ConnectWise Identity," a centralized Identity Provider (IdP) based on Microsoft Azure AD B2C. This allows for One Single Sign-On across Manage, Automate, Sell, and Control.
Legacy Method: Direct username/password specific to the Manage instance (URL: https://[region].myconnectwise.net ). Two-Factor Authentication (2FA/MFA): Enforced by default within the ConnectWise Identity framework.
B. Client Portal Login (External)
Purpose: Access for customers to view tickets, invoices, and projects. Domain: https://[region].myconnectwise.net (Client Portal tab). Authentication:
Native: Username/password created within the Manage "Contacts" screen. Branding: Login screens can be customized with partner logos. Security: Often lacks the rigorous MFA requirements of internal users unless specifically configured or integrated with a partner's Azure AD via the Client Portal interface.
C. API Login (Integrations)
Purpose: Access for third-party tools (e.g., ConnectWise Automate, QuoteWerks, IT Glue) to interact with the Manage database. Authentication Method:
Public/Private Key Pairs: The standard secure method where an integration uses a Company ID, Public Key, and Private Key. Member Impersonation: Integrations often log in "as" a specific user member to inherit that user's security rights.