Ask AI

Getting Started: MSP Onboarding Guide

This guide walks you through configuring your Managed Service Provider (MSP) environment in the Evo Portal. After completing these steps, your MSP will be ready to administer Evo Security services for customers.

Evo Portal Setup

This guide walks you through the initial setup of Evo including initial Partner Portal access via a “break glass” super user account, the integration of our MSP’s own external directory like Microsoft Entra ID or Active Directory, and the invitation and setup of your MSP’s internal users.

After completing these steps, you will have your MSP users in the Evo Portal so that they can administer Evo and your MSP environment will be setup so that you can test or deploy Evo products to your MSP’s internal environment.

Initial Account Setup & Portal Access

The very first account that you create in the Evo Partner Portal will be your Super Admin (a.k.a., “break glass”) account.

You will use this account to integrate your MSP’s directory to Evo and import users from there, which will be granted appropriate Portal permissions and used for day-to-day Portal logins and Evo administration.

Make sure that you have your Evo Portal URL, which was assigned during account provisioning. It will be something like yourMSP.evosecurity.com.

  1. Open your Evo welcome email and complete the password reset workflow to create your Super Admin (”break glass”) account.
      • Note: We recommend using a dedicated email address such as a Shared Mailbox or Distribution Group (not a personal account) for the Super Admin account. This account will only be used during the initial setup to invite additional users via personal, dedicated addresses. Once that is done, we recommend storing the credentials for the Super Admin account securely and not using it outside of a need for emergency access.
  1. Sign in to the Evo Partner Portal with your Super Admin credentials.

Connect Your MSP Directory

Evo must be connected to your MSP’s directory to synchronize users. Initially, you may only want to sync users who will administer Evo (e.g., MSP technicians.)

Additional users can be synced later, which you will want to do in order to use Evo services like MFA for your MSP. You can use groups to easily define and modify which users should be synced from your directory into Evo.

  1. Pick your MSP tenant from the top of the left-nav bar and go to Identities > Directories.
  1. Leave the existing default Evo Cloud Directory as a Service entry alone and intact.
      • Note: Since all Evo Portal users must be in a Directory, we create a default Evo Cloud Directory as a Service instance to house the Super Admin account independently from your third-party directory and other users.
  1. Integrate your MSP’s third-party directory by following the appropriate guide below. If you don’t have a third-party directory, you can use the Evo Cloud Directory as a Service option to directly create the users in Evo.

Invite Your Team

Having imported users from your third-party directory in the previous step, you will now invite any/all of those users who will administer Evo or use products like End User Elevation, Technician Elevation, etc. as a technician into the Evo Partner Portal and assign them appropriate permissions.

Allocate Licenses

Licenses should be allocated to your MSP users based on the products they will use. See our How Do I Manage My User Licenses? article for more detailed information.

  1. In the upper left corner, navigate to Evo Admin > Licensing & Billing.
  1. Scroll down and Expand the > next to your Tenant in the Tenant License Settings section.
  1. Allocate licenses to your tenant below for technicians or end users.

Configure Users for Access to Evo Partner Portal

  1. Ensure that users are syncing from your directory as expected under Identities > Users under your Tenant.
  1. Click on the username to open their full profile.
  1. To grant portal management privileges, click Convert to Admin in the upper right of the screen.
    1. Note: Users need to have the “Convert to Admin” step below completed before they will be able to log into the Evo Partner Portal. Without that, they are “regular users” who can be setup to use things like MFA or Helpdesk Verification as end-users but they cannot login to administer Evo itself or use those features from the “technician” perspective. In this context converting them to “Admin” does not imply that they will have global admin rights in Evo, it is simply the ability to log into the Partner Portal.
  1. Configure account options by toggling settings from red to green:
      • Zendesk Link - This creates a user in Evo’s Zendesk for opening Helpdesk tickets
      • MFA Status
      • User Status
      • License Type
  1. Click Welcome Email (bottom left) to send the setup email to the user.

Complete this process for each user that will administer Evo into the Portal - including yourself!

Configure Roles and Permissions

  1. Navigate to Global > Evo Admin > Permissions.
  1. On Roles Tab, Create a New role (e.g., “Full Access Admin”).
  1. Select users or group and required permissions (use Select All for full access).
  1. For users with limited responsibilities, create separate roles with restricted permissions (e.g., exclude billing or password management.)
    1. Note: Once you have created your own account, set it up via the Welcome Email, and assigned it that Full Access Admin role, you may log out of the Super Admin account and use your own account going forward.

Configure Key Integrations

At this point, we recommend setting up PSA and/or documentation integrations such as ConnectWise or IT Glue if you plan to integrate them to Evo. This will allow the creation and linking of Evo Tenants to the correct entities in those external systems.

Create Tenants

At this point, you are ready to provision customers under Evo Admin > Tenants > Add New Tenant and follow the setup wizard.

Next Steps

Your MSP environment is now onboarded to Evo Security and ready to manage customer tenants.

From here, you can proceed to setup our individual products:

 
Did this answer your question?
😞
😐
🤩