Have a code? Talk to us Start a trial

Blink for MSPs

One Blink for every customer you look after

An organization per customer, staff who reach exactly the computers they should, rollout with the RMM you already use, and your technicians named your way on the customer’s screen in support sessions.

Start a trial

Priced per technician, with unlimited Access devices on both plans. What your technicians can do in a session is on the features page, and how Blink keeps customers safe is on security.

Organization modelOne Blink holds an organization for each customer. Inside Customer B, devices sit in two groups, Head office and Servers. A technician with the Technician role on the Head office group reaches only the Head office devices.Your BlinkCustomer AOrganizationGroups, devicesCustomer BOrganizationCustomer COrganizationGroups, devicesHead officeGroupServersGroupJSJohn S.Technician roleLimited to theHead office devices
Illustration. Sets of devices such as a site or the servers. A role on a group limits someone to those devices.

Organizations and teams

One organization per customer

Each customer gets its own space, your staff get roles and device groups, and you work across all of it from one place.

  1. Organization

    One per customer, with its own members, groups, keys, devices, sessions and recordings. Nobody sees another organization unless given access.

  2. Overview

    Work across all your organizations from one view, and pick the organization when you create a support code.

  3. Team

    Each organization’s members and their roles, always with at least one active Owner.

  4. Roles

    Owner, plus editable Admin, Technician and Viewer roles, and custom roles for all organizations or just one.

  5. Groups

    Sets of devices such as a site or the servers. A role on a group limits someone to those devices.

  6. Enrollment keys

    A key per customer or rollout enrolls each computer straight into the right organization and group.

Organizations in the docs

Deployment

Deploy with the RMM you already use

Roll Access out to every customer’s Windows computers from the tool your team already works in.

Step-by-step guides and ready-made scripts, not native integrations. The scripts install and enroll silently, are safe to run again and report back to your tool, with one enrollment key per customer in the tool’s per-customer field.

Deployment guides

Guides for these tools

  • NinjaOne
  • Datto RMM
  • N-able N-central
  • N-able N-sight RMM
  • ConnectWise RMM
  • ConnectWise Automate
  • Kaseya VSA 10
  • Kaseya VSA 9
  • Kaseya 365 (through Datto RMM or Kaseya VSA)
  • Atera
  • Syncro
  • SuperOps
  • Action1
  • Level
  • Tactical RMM
  • Pulseway
  • LogMeIn Resolve
  • ManageEngine Endpoint Central
  • Automox
  • JumpCloud
  • ImmyBot
  • Microsoft Intune
  • Microsoft Configuration Manager
  • Group Policy
  • PDQ Deploy
  • PDQ Connect

Switching

Switch from your old remote access tool

In this order, so you never lose a computer along the way.

  1. Tell your security tools

    Allow Blink by its publisher, IZT Apps, Inc.

  2. Roll Blink out

    Push the agent with your RMM, or install it through your old tool.

  3. Check each computer is online

    Watch every computer appear under Access in Blink.

  4. Then remove the old tool

    Only after a computer shows online, so you never lose access.

Your customers’ side

Your team, as your customers see it

Choose how your technicians are named on the customer’s screen in support sessions, and whether their own IT staff join in.

Bring every customer into one Blink

Tell us how many technicians and customers you look after.

Start a trial Talk to us