# IZT Blink: complete reference > IZT Blink is remote support and remote access for MSPs and help desks, from IZT Apps, available in the cloud or on-premises: attended Support for Windows PCs and Macs with a one-time code, and unattended Access to the Windows computers you manage, all from a web browser. Generated from the content registry of https://blink.izt.app, the IZT Blink marketing site. Facts checked against the product on 2026-11-13; content updated 2026-11-13. ## Product **Remote support and remote access.** Help the person in front of the screen with a one-time code, and reach the computers you manage whenever they are online. For: Managed service providers, help desks and IT teams who support people on Windows PCs and Macs, and who manage Windows computers for their customers. **Availability:** Available in the cloud or on-premises, from IZT Apps, with the same features either way. Talk to us about the option that fits. IZT Blink is remote support and remote access for help desks and MSPs, made by IZT Apps and available in the cloud or on-premises, with the same features either way. Support is attended help. The customer types a one-time code on your own Blink address, runs a small tool on their Windows PC or Mac, and you are in. Nothing stays installed: when the session ends, the tool closes. Access is unattended access to the Windows computers you manage. Install the Blink agent once with an enrollment key, by hand, from your RMM or straight from a support session, and connect whenever the computer is online. Technicians work in a web browser and install nothing. They see and control every monitor, chat with the person at the computer, send files, type passwords as keystrokes, open a remote terminal, and on Windows run as administrator or reboot into Safe Mode and carry on. In a support session the customer always knows: a banner on Windows, or a menu bar item on a Mac, names the technician, and the customer can end the session at any time. Every person signs in with their own account and always-on two-factor. Work is separated into organizations, one per customer, with roles, device groups, IP and country rules, owner alerts and an activity log. Two plans, Blink Core (cloud only) and Blink Pro (cloud or on-premises), priced per technician with unlimited Access devices. Blink Pro adds session recording, terminal history, session timeline and Blink Notify, which puts a message on the screens of your Access devices. The Blink View add-on lets the technician see through the customer’s phone camera. ## Two kinds of session ### Support (Attended Support) Attended help for someone at a Windows PC or a Mac: they type a one-time code, run a small tool, and you are in. Nothing stays installed. For: Windows PCs and Macs. - A one-time code the customer types on your own Blink address - A small tool that closes when the session ends, with nothing left installed - The customer sees who is helping them and can end the session at any time - A restart or a dropped connection does not mean a new code ### Access (Unattended Access) Unattended access to the Windows computers you manage: install the Blink agent once with an enrollment key and connect whenever the computer is online. For: Windows computers. - Install by hand, from the RMM you already use, or straight from a support session - Connect whenever the computer is online, whether or not anyone is there - Chat with the user first, then connect from the same conversation - Agents keep themselves up to date, with automatic rollback ## Supported systems | Who or what | Supported | | --- | --- | | Windows 10 or later, 64-bit (x64) | Support (attended) and Access (unattended) | | macOS 12.3 or later, Apple silicon or Intel | Support (attended), with two permissions granted by the person at the Mac | | Linux, iPhone, iPad, Android, ChromeOS | Not supported as computers you help | | Technicians | A web browser, with nothing to install | | Phones for Blink View | Safari on iPhone or iPad, Chrome on Android (other browsers may work) | | Network | Every connection starts from the computer being helped, so there is nothing to open on the customer’s firewall | ## The support code - **Format:** Nine digits by default. An administrator can choose a different number of digits, or letters and digits. Example: `418 205 937`. - **Validity:** An unused code expires 15 minutes after it is created. Each code works once. - **Typing it:** Spaces, dashes and upper or lower case do not matter, and look-alike letters are read as the right digits. - **Where it works:** A code works only on the Blink address that created it. - **Protection:** Codes are protected against guessing. - **The download:** The download already carries its code, so the customer normally does not type it twice. ## Glossary - **Support:** Attended help for someone at a Windows PC or a Mac. The customer lets the technician in with a one-time code, and nothing stays installed afterwards. - **Access:** Unattended access to the Windows computers you manage. The Blink agent is installed once, and you connect whenever the computer is online. - **Support code:** The one-time code the customer types to join a support session. Nine digits by default, it works once and an unused code expires 15 minutes after it is created. - **Join page:** The page on your Blink address titled “Join a support session”, where the customer types the code and downloads the right tool for their computer. - **Blink address:** The web address of your own Blink, in the cloud or on-premises. It serves both the customer join page and the technician console. Codes work only on the Blink address that created them. - **Support tool:** The small program the customer runs to join a support session: a Windows tool or a Mac app. It closes when the session ends, with nothing left installed. - **Access agent:** The Blink agent installed on a Windows computer for unattended Access. It runs in the background, starts with Windows and keeps itself up to date. - **Enrollment key:** A key that enrolls computers into one organization, and optionally one device group. Every key expires, can be limited to a number of uses, and can be revoked at any time. - **Organization:** A separate space, typically one per customer, with its own members, groups, enrollment keys, devices, sessions and recordings. - **Overview:** The all-organizations view of the console, for people who work across several organizations. - **Role:** A set of permissions given to a person. Owner is the only built-in role; Admin, Technician and Viewer are starter roles you can edit, and you can build your own. - **Group:** A set of devices in one organization, such as a site, a department or the servers. A role on a group limits someone to those devices. - **Console:** The technician’s side of Blink in a web browser: sessions, Access devices, people, roles and settings. - **Viewer:** The browser window where a technician sees and controls a computer, with tools for monitors, clipboard, files, chat, terminal and more. - **Banner:** The bar on each viewed screen of a Windows PC during a support session. It names the technician and has Chat, Send file, End and Hide. - **Menu bar item:** On a Mac in a support session, the menu bar item says who is viewing and offers Chat with technician and End session. - **Backstage:** Beta. A separate hidden desktop on a Windows Access device, so the technician can run admin tools while the user keeps working. - **Remote terminal:** A command window on the remote computer in its own browser window, without taking over the screen. - **Chat:** Text chat between the technician and the person at the computer, in Support and Access sessions and before connecting to an Access device. - **Secret message:** A view-once chat message for passwords and codes. It is shown for 30 seconds when revealed and never kept in history or recordings. - **Blink View:** An add-on that lets the technician see through the customer’s phone camera during a session. Camera only, in the phone’s web browser, with no app. - **Technician seat:** What each console user takes on your plan, including admins, owners and pending invites. Disabled users do not take a seat. - **Access device:** An enrolled computer on your plan. Revoked and uninstalled computers do not count. - **Blink Core:** The plan with everything for Support, Access and running your team: viewer tools, chat, terminal, organizations, roles, IP and country rules, activity log and session history. - **Blink Pro:** Blink Core plus session recording, terminal history, session timeline and Blink Notify. - **Blink Notify:** Part of Blink Pro. Puts a message, such as an outage notice, on the screens of everyone signed in on your Windows Access devices, and shows who has seen and acknowledged it. ## Numbers worth quoting | Value | Meaning | | --- | --- | | 15 min | how long an unused support code stays valid | | 2 min | how long a support session waits for a dropped computer to come back | | 4,096 characters | the most Type text sends in one go | | 64 KB | the most clipboard text shared in one go | | 1 GiB | largest file a customer can send to the technician | | 4,000 characters | longest chat message | | 30 seconds | how long a revealed secret message stays on screen | | 24 | RMM and deployment tools with step-by-step Access deployment guides | Not published: any price, saving or billing term other than those on the pricing page, or technician seats included in a plan; latency, frame rate, resolution, bandwidth or connect-time figures; availability or service-level promises; rate-limit, lockout, fleet-limit or ban figures, update check intervals or probation periods; customer counts, ratings or awards. ## How it works ### Attended Support: Help the person in front of the screen A one-time code, a small tool on their Windows PC or Mac, and you are in. When the session ends the tool closes and nothing stays installed. In short: 1. **Create a code.** Select Create code in the console and give the customer the code, or send the join link. On screen: “Create code”. 2. **They type it.** On your Blink address. The right tool downloads for their Windows PC or Mac. No account needed. On screen: “Join a support session”. 3. **They run the tool.** On Windows they open the download. On a Mac, the person at the Mac allows two permissions. 4. **Confirm and connect.** Check it is the right computer, then work from your browser. The customer sees who is helping. On screen: “Confirm and take control”. 5. **End.** Either side ends it. The tool closes and nothing stays installed. On screen: “End”. #### Create a code *Technician.* One click in the console gives you a code to read out or a link to send. 1. **Select Create code.** In Sessions, add a label if you like, such as the printer at the front desk. From the all-organizations Overview, choose the organization first. On screen: “Sessions”, “Create code”. 2. **Give the customer the code.** Read it out, or paste the join link into a chat or email. Each code works once and expires 15 minutes after it is created if unused. On screen: “Give the customer this code”, “Copy code”, “Copy join link”. #### The customer types the code *Customer.* They open your Blink address, type the code and get the right download for their computer. 1. **Type the code on your Blink address.** One field, and spaces, dashes and case do not matter. The page says up front that a banner stays on screen while the session is live and that closing the tool ends it. On screen: “Join a support session”, “Download the support tool”. 2. **The right tool for their computer.** A Windows PC gets the Windows tool and a Mac gets the Mac app. No account, nothing to set up. #### They run the tool *Customer.* On Windows they open the download. On a Mac they open the app and allow two permissions. 1. **Windows: open the download.** It normally carries its code, so there is nothing more to type, and no admin rights are needed. If Windows shows a warning: More info, then Run anyway. On screen: “More info”, “Run anyway”. 2. **Mac: open Blink and allow two permissions.** A guided window walks them through Screen and System Audio Recording and Accessibility, then says All set. Only the person at the Mac can grant them. On screen: “Open Settings”, “All set. Your technician can now help you.”. #### Confirm and connect *Technician.* Check it is the right computer, then work from your browser while the customer sees who is helping. 1. **Confirm the right computer.** Select View. The viewer asks Is this your customer’s computer? with the computer name, who is signed in and the system. Control starts only after Confirm and take control. On screen: “View”, “Is this your customer’s computer?”, “Confirm and take control”. 2. **Work from your browser.** See and control every monitor, with nothing to install on your side. 3. **The customer sees who is helping.** On Windows a banner on each viewed screen names the technician. On a Mac the menu bar item does. On screen: “Viewed by technician: John S.”. #### End the session *Either side.* Either side can end it, and nothing stays installed. 1. **The customer ends it at any time.** End on the banner or Exit in the tray on Windows, or End session in the menu bar on a Mac. On screen: “End”, “Exit”, “End session”. 2. **Or the technician ends it.** End in the viewer or the console. The tool closes and nothing stays installed. On screen: “End”. 3. **A dropped connection is not the end.** Blink waits up to 2 minutes for the computer to come back, and a restarted tool rejoins without a new code. On screen: “Customer reconnecting…”. ### Unattended Access: Reach the computers you manage Install the Blink agent once on a Windows computer with an enrollment key, and connect whenever it is online, whether or not anyone is there. In short: 1. **Enroll the computer.** Create an enrollment key, then run the installer that carries it, push it from your RMM, or select Install Access in a support session. On screen: “Enrollment keys”, “Install Access”. 2. **Connect any time.** The computer shows under Access. Chat first if you like, then connect whenever it is online. On screen: “Access”, “Connect”. 3. **End the session.** End in the viewer or in Sessions. The agent stays installed for next time. On screen: “End session”. #### Enroll the computer *Administrator.* Create an enrollment key, then install the agent by hand, from your RMM, or straight from a support session. 1. **Create an enrollment key.** One key per customer or rollout decides which organization, and which group, the computer joins. Give it a label, a use limit and an expiry. It is shown once, and Revoke stops it at once. On screen: “Label”, “Seed group”, “Max uses”, “Expires in days”. 2. **Install the agent.** Run the installer with your key built in, push the ready-made scripts silently from your RMM, or select Install Access in a support session. Windows 10 or later (64-bit), with administrator rights. On screen: “Download installer”, “Install Access”. Rolling out with your RMM: https://blink.izt.app/msp#rmm #### Connect any time *Technician.* The computer shows under Access. Ask first if you like, then connect whenever it is online. 1. **Find it under Access.** The computer shows under Access, online or offline. On screen: “Access”, “Online”, “Offline”. 2. **Chat first, or connect straight away.** Send Can I connect now? and select Connect in the chat panel, or select View on the device. Access sessions connect without a banner or approval prompt, so use them on computers you manage, in line with your agreements. On screen: “Can I connect now?”, “Connect”, “View”. #### End the session *Technician.* End it when you are done. The computer stays enrolled for next time. 1. **End in the viewer or in Sessions.** Select End, then End session, or End on the session’s row. Every technician viewing the device is disconnected. On screen: “End”, “End session”. 2. **Ready for next time.** The agent stays installed, so you can connect again whenever the computer is online. ### Three ways to install Access - **Installer with your key.** Download an installer with your enrollment key built in. Run it on the computer and it installs and enrolls with no questions. - **Scripted, or from your RMM.** Ready-made scripts install and enroll silently, are safe to run again, and report the result back. Step-by-step guides cover 24 RMM and deployment tools. https://blink.izt.app/features/rmm-deployment - **Install Access from a support session.** Helping someone on Windows already? Install Access turns that computer into an Access device, with no file to send and no key to create. https://blink.izt.app/features/install-from-support ### Support session states - **Waiting for customer.** The code is created and waiting for the customer. An unused code expires after 15 minutes. - **Agents connected.** The customer’s support tool is connected and technicians can view. - **Technicians viewing.** How many technicians are in the session right now. - **Customer reconnecting….** The connection dropped. Blink waits up to 2 minutes for the computer to come back. - **Ended.** Ended by the customer or a technician, or because the computer did not come back in time. ### What the customer sees - **Windows: a banner on each viewed screen.** It names the technician, for example Viewed by technician: John S., with Chat, Send file, End and Hide, and a Recording indicator when the session is recorded. It shows in the technician’s view and the recording too. - **Windows: a tray icon for the whole session.** Its tooltip says whether a technician is viewing and whether the session is recorded, even when the banner is hidden. Show banner brings it back, and Exit ends the session. - **Mac: a menu bar item.** It says who is viewing, with Chat with technician and End session, and Close command windows while a terminal is open. - **Command windows are visible.** When a technician opens a terminal in a support session, the customer sees who opened it and can close it at any time. - **End at any time.** The customer can end the support session at any time, for every technician. ## Features Status labels: shipping = Available; beta = Beta. Plan labels: core = Blink Core and Blink Pro; pro = Blink Pro only; addon = Add-on, sold separately. ### Attended Support A one-time code, a small tool, and you are helping. Nothing stays installed. #### One-time support codes Status: **Available** · For technicians · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/support-codes Create a code, read it out, and the customer is on their way. The technician selects Create code and the console shows Give the customer this code in large type, with Copy code and Copy join link. Codes are nine digits by default, each one works once, and an unused code expires 15 minutes after it is created. An optional label and group keep the session where it belongs. #### A join page on your own Blink address Status: **Available** · For your customers · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/join-page The customer types the code on your Blink address and gets the right download for their computer. The customer opens your Blink address and sees Join a support session with one code field. The page recognises the computer: a Mac gets the Mac app and a Windows PC gets the Windows tool. It tells the customer up front that a banner stays on screen, that each code works once, and that closing the tool ends the session. Errors are in plain language. #### Windows PCs and Macs Status: **Available** · For your customers · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/windows-and-mac Help people on Windows 10 or later and on macOS 12.3 or later. Support works on Windows 10 or later (64-bit) and on Macs with macOS 12.3 or later, Apple silicon or Intel. On Windows the tool runs with the customer’s own rights, so nobody needs an admin password to get started. #### Guided Mac setup Status: **Available** · For your customers · Sessions: Support · Computers: Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/mac-guided-setup A guided window walks the Mac user through the two permissions Blink needs. macOS asks the person at the Mac to allow Screen and System Audio Recording and Accessibility. Blink opens a guided window with an Open Settings button for each, updates as each switch goes on, and says All set when the technician can help. Only the person at the Mac can grant these permissions, and they can turn them off at any time. #### Nothing left installed Status: **Available** · For your customers · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/nothing-left-installed When the session ends, the tool closes and nothing stays installed. The support tool is for this one session only. Files the technician sent stay in the customer’s Downloads folder, where the customer can keep or delete them. #### Confirm the right computer Status: **Available** · For technicians · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/right-computer-check Before taking control, the technician checks it is the right computer. The viewer asks Is this your customer’s computer? and shows the computer name, who is signed in and the system. Mouse, keyboard, clipboard, files, Run as admin, terminal and secret messages start only after Confirm and take control. Seeing the screen and chatting work meanwhile, and each technician confirms for themselves. #### Picks up where it left off Status: **Available** · For technicians · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/session-resume A restart or a dropped connection does not mean a new code. If the customer’s computer drops off, Blink waits up to 2 minutes for it and the technician sees Customer reconnecting. If the tool restarts, for example to apply a Mac permission or to run as administrator, it rejoins the same session on the same computer and account without a new code. Closing the viewer tab does not end the session either. ### Unattended Access Install the agent once and reach the Windows computers you manage whenever they are online. #### Unattended Access for Windows Status: **Available** · For technicians · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/access-agent Connect to the Windows computers you manage whenever they are online. Install the Blink agent once and the computer shows under Access. It runs in the background, starts with Windows and restarts itself if it stops. Connect whenever the computer is online, whether or not anyone is there. Access sessions connect without a banner or an approval prompt, so use them on computers you manage, in line with your agreements. #### Enrollment keys Status: **Available** · For your team · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/enrollment-keys One key per customer or rollout puts each computer in the right place. An enrollment key enrolls computers into one organization and, if you like, one device group. Give it a label, a maximum number of uses and an expiry; every key expires. Revoke a key and installers carrying it stop working at once, while computers already enrolled carry on. The key is shown once. #### Deploy with your RMM Status: **Available** · For your team · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/rmm-deployment Roll Blink out with the RMM or deployment tool you already use. Ready-made scripts download, install and enroll the agent silently, are safe to run again, and report the result back to your tool with the reason if something fails. Step-by-step guides cover 24 RMM and deployment tools, and keep one key per customer in each tool’s per-customer field. These are guides and scripts, not native integrations. #### Install Access from a support session Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/install-from-support Turn a Windows computer you are already helping into an Access device. During a support session on Windows, Install Access in the viewer installs the agent with no file to send and no key to create. The viewer shows Installing, then Access installed, with a link to open the device in the console. It needs the support tool running as administrator, the Install Access permission and a free Access device. #### Device management Status: **Available** · For your team · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/device-management See every Access device, online or offline, and find the right one fast. The Access page shows devices, online, offline and updates available at a glance. Search by name, host name, system, agent version or tag; filter by status and group. Device details show status, system, last seen, boot mode, last reboot, BitLocker status, pending restarts, groups, tags, session history and chats. Revoke a lost or stolen computer and its access stops at once. #### Agents that update themselves Status: **Available** · For your team · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/agent-updates You never reinstall to update. Agents update and roll back on their own. Agents check that an update is signed by IZT, built for your Blink and newer before they take it. A new version runs on probation, and if it keeps failing the agent rolls back by itself. Updates wait while a remote terminal is open, and you can push one now from the console. #### Blink Notify Status: **Available** · For your team · Sessions: Access · Computers: Windows · Plan: Blink Pro only · Page: https://blink.izt.app/features/notify Put a message on the screens of your Access devices and see who acknowledged it. Send to all your devices, to organizations or to device groups, with a title and a plain-text message. Pick Info, Warning or Critical: the severity sets the buttons (Acknowledge + Close, Acknowledge only or Close only), whether the window stays on top, whether it comes back until acknowledged, and a sound. You can change each of these before you send. Everyone signed in on a device sees it on their own screen, and you see per device and per user who has seen it, acknowledged it or closed it. Send a follow-up, recall a message or give it longer. ### See and control Everything a technician needs, in a web browser. #### All in the browser Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/browser-console Technicians work in a web browser and install nothing. Start support codes, open Access devices, join sessions and run your team from the console in a web browser. The viewer’s toolbar shows only what the technician’s role and your plan allow. #### Every monitor Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/multi-monitor Switch between monitors, or pop them out to watch side by side. The viewer has a button for each monitor, and Pop out opens another monitor in its own window so you can watch several at once. Fullscreen gives one monitor the whole screen. #### Quality that adapts Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/auto-quality The picture adapts to the connection on its own. Quality starts on auto and adapts to the connection. A technician can choose low, standard or high when they want to. #### Remote control Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/remote-control Mouse and keyboard, as if you were sitting there. Click into the viewer to capture the keyboard; held keys are released when focus leaves, so nothing gets stuck. Technicians on a Mac get a button that sends the Windows or Ctrl key. In Access sessions, Ctrl+Alt+Del reaches the Windows sign-in screen. #### Shared clipboard Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/clipboard Copy text on one side and paste it on the other. Clipboard text goes both ways between the technician and the remote computer, up to 64 KB at a time. It carries text only. #### Type text Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/type-text Type passwords and long commands as real keystrokes. Type text sends a block of up to 4,096 characters as real keystrokes, for password fields and boxes that block pasting. Hide the characters, pick a speed, and stop at any time. The text is encrypted for the remote computer before it leaves the browser and is never stored or logged. #### Hear the computer Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/remote-audio Hear the remote computer’s sound in the viewer. The technician hears the remote computer’s system sound, following whichever output the customer uses. Sound goes one way only: from the computer to the technician. On a Mac it needs the Screen and System Audio Recording permission. #### Several technicians at once Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/multi-technician Bring in a colleague, each with their own role. Several technicians can share a session, each limited by their own role; someone with a view-only role sees View only. In Support the banner names everyone viewing. A technician can join a running Access session from Sessions. ### Fix it remotely Files, admin rights, a terminal and a restart, without a site visit. #### Send files Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/file-transfer Send files or drag them in, and every file is checked on arrival. Use Send file or drag and drop, with progress, speed and time left. Every file is checked on arrival so a damaged transfer is never saved. Files land in Downloads, in a Blink folder, and never overwrite anything. File transfer has no remote file browser: in Windows support sessions files come back only when the customer chooses Send file, and nothing is saved until the technician accepts it. #### Customers send files to you Status: **Available** · For your customers · Sessions: Support · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/customer-send-file On Windows, the customer sends you a file from the banner or tray. In a Windows support session the customer chooses Send file on the banner or in the tray. Nothing is saved until the technician selects Accept or Decline, and files that could run code show a warning first. Up to 1 GiB per file. #### Run as administrator Status: **Available** · For technicians · Sessions: Support · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/run-as-admin Relaunch the support tool with admin rights, and the session carries on. On Windows, Run as admin relaunches Blink with administrator rights, either with admin credentials or with the Windows prompt. The customer always clicks Yes. Credentials are encrypted for the customer’s computer before they leave the browser, used once and never stored. Afterwards the technician can handle admin prompts and open an administrator terminal. #### Remote terminal Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/remote-terminal A command window on the remote computer, without taking over the screen. Open PowerShell or Command Prompt on Windows, or the customer’s own shell on a Mac, in its own browser window. On Access devices choose full control or the signed-in user’s rights. In Support the customer sees who opened it and can close it at any time. Terminal rights are granted on purpose: only the Owner role has them out of the box. #### Reboot and Safe Mode Status: **Available** · For technicians · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/reboot-safe-mode Restart a Windows Access device, or reboot into Safe Mode with Networking, and carry on. Power offers Reboot or Reboot into Safe Mode with Networking. The viewer reconnects by itself when the device is back. In Safe Mode Blink connects so the work continues, and the next restart returns to normal Windows. Blink warns about BitLocker and pending updates before it restarts. #### Backstage desktop (beta) Status: **Beta** · For technicians · Sessions: Access · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/backstage Work on a separate desktop while the user keeps working. Backstage opens a separate hidden desktop on a Windows Access device, with its own taskbar and Start menu and eight admin tools pinned. Programs started there run alongside the user’s desktop, so the technician works while the user carries on. Some programs may not draw or respond reliably there. ### Talk to the person at the computer Chat, share a password safely, or see the problem through their phone. #### Chat Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/chat Chat during a session, or ask first and connect from the same conversation. Chat in Support and Access sessions, and before connecting to an Access device: ask Can I connect now?, then select Connect and the conversation carries on. The technician starts the chat; in Support the customer can open it too. Messages show Seen, a typing indicator, and are kept with the session. #### Secret messages Status: **Available** · For technicians · Sessions: Support, Access · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/secret-messages Share passwords and codes both ways, shown once and never kept. A secret message is revealed once, for 30 seconds, and an unopened one expires. It never appears in session history, recordings or logs; only when it was sent, viewed or expired is kept. The technician’s view and the recording show a grey Secret block instead. #### Blink View Status: **Available** · For technicians · Sessions: Support, Access · Plan: Add-on, sold separately · Page: https://blink.izt.app/features/blink-view See through the customer’s phone camera, in the phone’s browser. During a Support or Access session the technician can see through the customer’s phone camera: router lights, cables, printer labels. The customer joins in the phone’s web browser with a short code or a QR code; there is no app. It is camera only, and nothing is shown until the technician accepts. Blink View is an add-on, sold separately. ### Kept in the picture What the customer sees during a support session. #### Banner and menu bar Status: **Available** · For your customers · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/banner The customer always sees who is helping them. On Windows a banner on each viewed screen names the technician, with Chat, Send file, End and Hide, plus a Recording indicator when the session is recorded. The tray icon stays for the whole session. On a Mac the menu bar item says who is viewing, with Chat with technician and End session. #### End at any time Status: **Available** · For your customers · Sessions: Support · Computers: Windows, Mac · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/end-anytime The customer is always in control and can end the session at any time. End on any banner or Exit in the tray on Windows, or End session in the menu bar on a Mac, ends the session for every technician. Closing the chat window does not end anything. #### Your name on the banner Status: **Available** · For your team · Sessions: Support · Computers: Windows · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/technician-name Choose how technicians are named to customers, per organization. Show the first name and last initial, the full name, or your own text such as Technician. Set it for the whole instance and override it per organization; changes reach live sessions at once. It is never an email address, and hidden characters are stripped so the banner cannot be faked. ### Built for teams and MSPs Organizations, roles, always-on two-factor and the oversight owners need. #### Organizations Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/organizations One organization per customer, each kept apart. Each organization has its own members, groups, enrollment keys, devices, sessions and recordings. People cannot see another organization unless they are given access. Switch between organizations, or work across all of them from the Overview. #### Roles and groups Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/roles-and-groups Give each person exactly what they need, down to a group of devices. Owner is the only built-in role. Admin, Technician and Viewer are starter roles you can edit, and you can build your own for all organizations or one. Nobody can build a role stronger than their own. Groups are sets of devices, such as a site or the servers, and a role on a group limits someone to those devices. #### An account for every technician Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/technician-accounts Everyone signs in as themselves, so you always know who did what. Every console user has their own account. You create the user and send them a one-time invite link yourself. Nobody has access until they are given a role. Disable someone and they are signed out everywhere and their seat is freed. #### Always-on two-factor Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/two-factor Every sign-in needs a password and a passkey or authenticator code. Two-factor is always on and cannot be turned off. Use a passkey (fingerprint, face, screen lock or security key) or a code from an authenticator app, with recovery codes as a backup. Sign out of all devices in one step. #### High-risk confirmation Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/high-risk-confirmation Sensitive actions need a fresh passkey or code, so a stolen sign-in is not enough. Opening a terminal, a Safe Mode reboot, Install Access, revoking or deleting a device, and changes to roles, members, users and security settings ask for a fresh passkey or code. How long a confirmation lasts is up to you, and loosening it alerts the owners. #### IP and country rules Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/ip-country-rules Choose where the console can be used from, and where each organization’s devices may connect from. The console rule applies to every user, the Owner included. Each organization can have its own agent rule for its Access devices. Rules take IP ranges or countries. Blink stops you locking yourself out and previews which live connections a change would close. Customers joining Support are never restricted. #### Owner alerts and webhook Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/owner-alerts Owners hear about the changes that matter, in the console or in your own tools. Instance owners get alerts for new owners and role changes, sign-in resets, failed high-risk confirmations, blocked agents, fleet limits, device limits and security changes. One webhook sends each alert to a chat tool or monitoring system, and setting or removing it raises an alert too. #### Activity log Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/activity-log Who did what, newest first, per organization and across the instance. Activity shows when, who, what, the target and the details, for each organization and instance-wide. It covers sign-in and role changes, chat events (never their content), Blink View events, IP rule changes and diagnostics. Every alert is an activity record too. #### Fleet limits Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/fleet-limits Cap how many Access sessions, reboots and chats one person can start in an hour. Fleet limits apply per person across all organizations. Anything over the limit is refused and the owners are alerted, so a misused account cannot sweep through your fleet. ### On the record Session history on every plan; recordings, transcripts and timelines with Blink Pro. #### Session history Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/session-history A list of ended sessions: who, what, when and how long. Session history keeps the ended sessions of each organization, with who took part, which computer, when and for how long. Chats are kept with the session too. #### Session recording Status: **Available** · For your team · Sessions: Support, Access · Plan: Blink Pro only · Page: https://blink.izt.app/features/session-recording Sessions recorded automatically and played back in the browser. Each viewed monitor is recorded as its own video, with the computer’s sound. In Windows support sessions, the banner and tray show when the session is recorded. The player shows all monitors and sound on one timeline, with lanes for technicians and events, a Chat tab, Go live for a running session, and downloads per track. Secrets show only as a grey block. #### Terminal history Status: **Available** · For your team · Sessions: Support, Access · Plan: Blink Pro only · Page: https://blink.izt.app/features/terminal-history Searchable, replayable transcripts of every terminal. Every remote terminal is kept as a transcript you can search and replay. Transcripts stay even if the session recording is deleted. #### Session timeline Status: **Available** · For your team · Sessions: Support, Access · Plan: Blink Pro only · Page: https://blink.izt.app/features/session-timeline A detailed timeline and full log of every session. Each session gets a detailed timeline and a full session log. Logs record what happened, not what was typed or copied. #### Diagnostics you control Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/diagnostics Turn up logging when you need it, and send IZT only what you choose. Diagnostic mode turns up logging for up to 7 days and then switches itself off, with no visible change for your team or customers. Send diagnostics to IZT is push-only: IZT receives only what someone on your team chooses to send and cannot fetch anything, and sending gives IZT no access to your Blink. Recordings, chat, transcripts, clipboard, files, passwords and codes are never included. ### Your Blink, your way Where Blink runs and how it stays up to date. #### Cloud or on-premises Status: **Available** · For your team · Sessions: Support, Access · Plan: Cloud: Blink Core and Blink Pro. On-premises: Blink Pro only. · Page: https://blink.izt.app/features/cloud-or-on-premises Blink Core in the cloud; Blink Pro in the cloud or on-premises, with the same features either way. In the cloud, IZT runs Blink for you: your license is activated and your Blink address is set up and kept secure for you. On-premises, which is Blink Pro only, Blink runs on your own infrastructure, can work in closed networks with offline activation and updates, and you decide how long recordings are kept. Either way, one Blink address serves your customers and your technicians. #### Works through restrictive networks Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/restrictive-networks Nothing to open on the customer’s firewall. Every connection starts from the computer being helped, so the customer’s site opens nothing inbound and needs no VPN. Blink needs only a direct outbound secure connection to your Blink address, so it works through most restrictive firewalls. Networks that force traffic through a web proxy or inspect secure traffic need an exception for your Blink address. #### Never cut off Status: **Available** · For your team · Sessions: Support, Access · Plan: Included in Blink Core and Blink Pro · Page: https://blink.izt.app/features/never-cut-off Limits, and a license that has expired or lapsed, never drop a device that is already enrolled. At a limit, Blink refuses only new users or new enrollments; devices already enrolled keep working. After a downgrade nobody is locked out. If a license lapses, installed agents keep connecting and Support keeps working; only new agent builds and updates stop. ## For MSPs 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. ### One organization per customer - **Organization.** One per customer, with its own members, groups, keys, devices, sessions and recordings. Nobody sees another organization unless given access. - **Overview.** Work across all your organizations from one view, and pick the organization when you create a support code. - **Team.** Each organization’s members and their roles, always with at least one active Owner. - **Roles.** Owner, plus editable Admin, Technician and Viewer roles, and custom roles for all organizations or just one. - **Groups.** Sets of devices such as a site or the servers. A role on a group limits someone to those devices. - **Enrollment keys.** A key per customer or rollout enrolls each computer straight into the right organization and group. ### What MSPs get - **Customers kept apart.** One organization per customer, on every plan, with an Overview across them all. https://blink.izt.app/features/organizations - **Exactly the right access.** Roles and device groups decide who reaches which computers. Nobody can give more than they have. https://blink.izt.app/features/roles-and-groups - **Turn a call into a managed device.** Install Access from a support session, with no file to send and no key to create. https://blink.izt.app/features/install-from-support ### Deploy with the RMM you already use 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. 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. ### Switch from your old remote access tool 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 technicians’ names, your way.** First name and last initial, full name or your own text, for the whole instance or per organization. Never an email address. https://blink.izt.app/features/technician-name - **Your customer’s own IT staff, if you want.** Add them to their organization, and decide whether they may manage roles there themselves. https://blink.izt.app/features/roles-and-groups - **News for every customer at once.** With Blink Pro, Blink Notify puts an outage or maintenance notice on the screens of your customers’ Access devices, signed with their organization’s name. https://blink.izt.app/features/notify ## Plans and pricing ### Plans - Prices are in US dollars, per technician per month. Annual billing saves 17% compared with monthly billing. - Blink Core: $29 per technician per month billed annually, or $35 billed monthly. Cloud only. - Blink Pro: $39 per technician per month billed annually, or $47 billed monthly. Cloud or on-premises. - Unlimited Access devices on both plans. - Blink View add-on: $5 per technician per month, with Blink Core or Blink Pro. - On-premises is Blink Pro only. It is billed annually, needs at least 3 technicians and has a one-time $199 installation charge: IZT does the installation for you. - In the cloud, Blink Pro recording storage is $0.10 per GB per month. Larger team, or need a tailored license? Talk to us: https://blink.izt.app/contact #### Blink Core Price: $29 per technician per month billed annually, or $35 billed monthly. Where: Cloud only. Unlimited Access devices. Page: https://blink.izt.app/pricing#core Everything for Support, Access and running your team. Attended Support for Windows PCs and Macs, unattended Access to Windows computers, the full viewer, chat and secret messages, remote terminal, organizations, custom roles, IP and country rules, an activity log and session history. - Attended Support and unattended Access - Remote control, file transfer, clipboard and Type text - Remote terminal, run as administrator, reboot and Safe Mode - Chat and secret messages - Multiple organizations and custom roles - IP and country rules, owner alerts and activity log - Session history #### Blink Pro Price: $39 per technician per month billed annually, or $47 billed monthly. Where: Cloud or on-premises. Unlimited Access devices. Page: https://blink.izt.app/pricing#pro Blink Core, plus a full record of every session and Blink Notify. Everything in Blink Core, plus session recording, terminal history, session timeline and Blink Notify. - Everything in Blink Core - Session recording: sessions recorded automatically and played back in the browser - Terminal history: searchable, replayable transcripts of every terminal - Session timeline: a detailed timeline and full log of every session - Blink Notify: put a message on the screens of your Access devices and see who acknowledged it ### Priced per technician - **Technician seats.** Plans are priced per technician: one seat for each person who uses the console. Every user who is not disabled, including admins, owners and pending invites. Disabled users do not take a seat. Support sessions are not counted. - **Unlimited Access devices.** Enroll every Windows computer you look after for unattended Access. Both plans include unlimited Access devices. ### Compare the plans #### Where it runs and what is included | Capability | Blink Core | Blink Pro | Note | | --- | --- | --- | --- | | Cloud | Included | Included | | | On-premises | Not included | Included | See the on-premises terms | | Access devices | Unlimited | Unlimited | | #### Session modes | Capability | Blink Core | Blink Pro | Note | | --- | --- | --- | --- | | [Attended Support](https://blink.izt.app/features/support-codes) | Included | Included | Windows PCs and Macs | | [Unattended Access](https://blink.izt.app/features/access-agent) | Included | Included | Windows computers | | [Blink Notify](https://blink.izt.app/features/notify) | Not included | Included | Messages to Windows Access devices | #### Session capabilities | Capability | Blink Core | Blink Pro | Note | | --- | --- | --- | --- | | [Remote control](https://blink.izt.app/features/remote-control) | Included | Included | | | [File transfer](https://blink.izt.app/features/file-transfer) | Included | Included | | | [Clipboard sync](https://blink.izt.app/features/clipboard) | Included | Included | | | [Remote terminal](https://blink.izt.app/features/remote-terminal) | Included | Included | | | [Backstage](https://blink.izt.app/features/backstage) | Included | Included | Beta | | [Reboot and Safe Mode](https://blink.izt.app/features/reboot-safe-mode) | Included | Included | Shown as Power actions in your plan | | [Run as administrator](https://blink.izt.app/features/run-as-admin) | Included | Included | Shown as Elevation in your plan | | [Install Access from Support](https://blink.izt.app/features/install-from-support) | Included | Included | | | [Remote audio](https://blink.izt.app/features/remote-audio) | Included | Included | | | [Chat](https://blink.izt.app/features/chat) | Included | Included | | | [Secret messages](https://blink.izt.app/features/secret-messages) | Included | Included | | #### History | Capability | Blink Core | Blink Pro | Note | | --- | --- | --- | --- | | [Session history](https://blink.izt.app/features/session-history) | Included | Included | | | [Session recording](https://blink.izt.app/features/session-recording) | Not included | Included | | | [Terminal history](https://blink.izt.app/features/terminal-history) | Not included | Included | | | [Session timeline](https://blink.izt.app/features/session-timeline) | Not included | Included | | #### Administration | Capability | Blink Core | Blink Pro | Note | | --- | --- | --- | --- | | [Multiple organizations](https://blink.izt.app/features/organizations) | Included | Included | | | [Custom roles](https://blink.izt.app/features/roles-and-groups) | Included | Included | | | [Activity log](https://blink.izt.app/features/activity-log) | Included | Included | Shown as Audit log in your plan | | [Technician name on the banner](https://blink.izt.app/features/technician-name) | Included | Included | Shown as Tech name in your plan | | [IP and country rules](https://blink.izt.app/features/ip-country-rules) | Included | Included | | #### Add-ons | Capability | Blink Core | Blink Pro | Note | | --- | --- | --- | --- | | [Blink View](https://blink.izt.app/features/blink-view) | Add-on | Add-on | Sold separately | ### Add-on - **Blink View** ($5 per technician per month, with Blink Core or Blink Pro). See through the customer’s phone camera during a Support or Access session, in the phone’s web browser with no app. Camera only, and nothing is shown until the technician accepts. Works with Blink Core and Blink Pro. https://blink.izt.app/features/blink-view ### On-premises On-premises is Blink Pro only. It is billed annually, needs at least 3 technicians and has a one-time $199 installation charge: IZT does the installation for you. **Server requirements:** - A dedicated server or virtual machine running Debian 13 (x64), with nothing else on it. - Minimum, up to 10 technicians: 2 vCPU, 4 GB memory and a 64 GB SSD. - Recommended, up to 50 technicians: 4 vCPU, 8 GB memory and a 128 GB SSD. - Add recording storage on top: plan about 1 GB per recorded hour per monitor. - More than 50 technicians? Talk to us and we will size the server with you. In the documentation: https://docs.blink.izt.app/install/on-premises-server/#server-requirements ### How limits and licenses work - **Limits never lock anyone out.** Access devices are unlimited. At your technician seat limit only new users are refused: your team keeps working and no device is dropped. - **A downgrade keeps your records.** Nobody is locked out and no device is dropped. Existing recordings, transcripts and timelines stay playable, downloadable and deletable. - **Changes go through us.** To change plans or technician seats, contact us. The change arrives with your next license. - **Tailored licenses.** A license can be tailored to what you need, for example Attended Support only. - **A lapsed license never cuts you off.** Everything keeps working through a grace period. After that, installed agents keep connecting and Support keeps working; only new agent builds and updates stop. - **Cloud or on-premises.** Blink Core runs in the cloud. Blink Pro runs in the cloud or on-premises, with the same features either way. ## Security and privacy ### Your customer stays in control In a support session the customer starts it, sees who is helping and can end it at any time. - **The customer starts every support session.** Nothing connects until the customer types the code and opens the tool themselves. When it ends, nothing stays installed. - **The customer sees who is helping.** In a support session on Windows a banner on each viewed screen names the technician; on a Mac the menu bar item says who is viewing. The banner can never be made to claim nobody is viewing. - **End at any time.** End on any banner, Exit in the tray, or End session in the Mac menu bar ends the support session for every technician. - **Admin rights need the customer’s Yes.** Run as administrator on Windows always needs the customer to click Yes. Admin credentials are used once and never stored. - **Mac permissions stay with the person at the Mac.** Only the person at the Mac can grant Blink’s two permissions, and they can turn them off at any time. What your customer sees: https://blink.izt.app/join In the documentation: https://docs.blink.izt.app/use/what-customers-see/ ### What is recorded, and what is kept out A record of every session, with secret messages masked and typed or copied text kept out of the logs. - **Session history on every plan.** Every ended session is listed with who, what, when and how long. - **Recordings with Blink Pro.** With Blink Pro, sessions are recorded automatically. In Windows support sessions, the banner and tray show when the session is recorded. Terminal transcripts and a detailed session timeline come with it. - **Secret messages.** Passwords and codes can be sent as secret messages: revealed once, for 30 seconds, and never kept in history, recordings or logs. The screen and the recording show only a grey Secret block. - **Logs without the private parts.** Logs record what happened, not what was typed or copied. Chat events are logged, never their content. - **Push-only diagnostics.** IZT only ever receives what someone on your team sends. IZT cannot fetch anything from your Blink, and sending gives IZT no access to it. History and recording features: https://blink.izt.app/features#group-records ### Every person signs in as themselves Own accounts, two-factor that cannot be turned off, and fresh proof for anything risky. - **An account for every person.** Every console user has their own account, so every action is tied to a named person. Nobody has access until they are given a role, and Disable signs someone out everywhere. - **Two-factor, always on.** Every sign-in needs a password plus a passkey or a code from an authenticator app. It cannot be turned off, and passkeys cannot be phished. - **Fresh proof for high-risk actions.** Opening a terminal, a Safe Mode reboot, Install Access, revoking or deleting a device, and changes to roles, users and security settings ask for a fresh passkey or code, so a stolen sign-in alone cannot do them. In the documentation: https://docs.blink.izt.app/configure/sign-in-and-two-factor/ ### Exactly the access each person needs Roles, rules and alerts decide who reaches which computers, from where, and owners see what changes. - **Roles and groups.** Give each person exactly what they need, down to a group of devices. Nobody can build a role stronger than their own. - **Terminal rights are granted on purpose.** Remote terminal and Backstage with full control are never granted by ticking a whole area, nor by instance ownership alone. Only the Owner role has them out of the box. - **IP and country rules.** Limit where the console can be used from, for every user including the Owner, and where each organization’s Access devices may connect from. Customers joining Support are never restricted. - **Revoke a lost computer.** Revoke a lost or stolen computer and its credential stops working, its connection drops and open sessions end. - **Owner alerts.** Owners are alerted to new owners and role changes, sign-in resets, failed high-risk confirmations, blocked agents, reached limits and security changes that could silence alerts. - **An activity log.** Who did what, newest first, per organization and across the instance. Every alert is an activity record too. Organizations and roles for MSPs: https://blink.izt.app/msp In the documentation: https://docs.blink.izt.app/configure/roles/ ### You choose where it runs Talk to us about the option that fits your policies. - **Cloud or on-premises.** Same features either way. In the cloud, IZT runs Blink for you. On-premises is Blink Pro, billed annually: it can run in closed networks, and you decide how long recordings are kept. On-premises terms: https://blink.izt.app/pricing#on-premises In the documentation: https://docs.blink.izt.app/get-started/what-is-blink/ ### What the customer sees in a support session - **Windows: a banner on each viewed screen.** It names the technician, for example Viewed by technician: John S., with Chat, Send file, End and Hide, and a Recording indicator when the session is recorded. It shows in the technician’s view and the recording too. - **Windows: a tray icon for the whole session.** Its tooltip says whether a technician is viewing and whether the session is recorded, even when the banner is hidden. Show banner brings it back, and Exit ends the session. - **Mac: a menu bar item.** It says who is viewing, with Chat with technician and End session, and Close command windows while a terminal is open. - **Command windows are visible.** When a technician opens a terminal in a support session, the customer sees who opened it and can close it at any time. - **End at any time.** The customer can end the support session at any time, for every technician. ## For the customer with a code Open the link your technician sent you and type your code there. Codes work only on your technician’s own Blink page, not on this site. 1. **Open your technician’s Blink link.** On the computer that needs help, open the link your technician sent you, or the address they read out. The page is called Join a support session. On screen: “Join a support session”. 2. **Type your code.** Spaces, dashes and capital letters do not matter. Then select Download the support tool. On screen: “Download the support tool”. 3. **Your technician checks it is you.** Before taking control, your technician confirms it is the right computer. You see who is helping you for the whole session. Page for customers: https://blink.izt.app/join ## FAQ ### About Blink #### What is IZT Blink? Remote support and remote access for help desks and MSPs, made by IZT Apps, in the cloud or on-premises. Technicians work in a web browser. #### Who is Blink for? Managed service providers, help desks and internal IT teams, and the people they support. Blink for MSPs: https://blink.izt.app/msp #### What is the difference between Support and Access? Support is attended: the person at a Windows PC or Mac lets you in with a one-time code, and nothing stays installed. Access is unattended: you install the Blink agent once on a Windows computer you manage and connect whenever it is online. How it works: https://blink.izt.app/how-it-works #### Which computers can Blink support? Support works on Windows 10 or later (64-bit) and macOS 12.3 or later. Access works on Windows 10 or later (64-bit). What runs where: https://blink.izt.app/how-it-works#needs #### What do our technicians need? A web browser, with nothing to install, and their own account with two-factor. #### Does Blink work through firewalls? Yes. There is nothing to open on the customer’s firewall and no VPN. Networks that inspect secure traffic or force a web proxy need an exception for your Blink address. What runs where: https://blink.izt.app/how-it-works#needs ### For the people you support #### I have a code. Where do I type it? On the Blink page your technician sends you: codes only work there. The Have a code page shows what you will see on Windows and Mac and how to end. Have a code?: https://blink.izt.app/join #### My code doesn’t work. What now? Each code works once and expires 15 minutes after it is created, so ask your technician for a new one. Where to type it: https://blink.izt.app/join#where #### Where do files from my technician go? Into a folder called Blink in your Downloads folder. Blink never overwrites a file you already have. #### My technician asked to use my phone camera. Is that safe? That is Blink View. It runs in your phone’s web browser, with no app, and shows your technician only the camera, never your screen, photos or files. Either of you can end it. Blink View: https://blink.izt.app/features/blink-view ### Unattended Access #### How do I add a computer for unattended Access? Install the Blink agent with an enrollment key: by hand, from your RMM, or with Install Access during a support session. How Access works: https://blink.izt.app/how-it-works#access #### Can I deploy Blink with my RMM? Yes. Ready-made scripts and step-by-step guides cover 24 RMM and deployment tools. These are guides and scripts, not native integrations. Rolling out with your RMM: https://blink.izt.app/msp#rmm #### Does Access work on a Mac? No. Access is for Windows 10 or later (64-bit). Macs are supported for attended Support sessions. #### Does the user see when I connect through Access? No. Access sessions connect without a banner or approval prompt, so use Access on computers you manage, in line with your agreements. How Access works: https://blink.izt.app/how-it-works#access #### How do agents get updated? By themselves. Agents check each update before taking it and roll back on their own if a new version keeps failing. #### Can I restart a computer and keep working? Yes, on Windows Access devices. Reboot normally or into Safe Mode with Networking, and the viewer reconnects when the computer is back. #### What is Backstage? A hidden desktop on a Windows Access device, in Beta, where the technician works while the user keeps their own desktop. Backstage: https://blink.izt.app/features/backstage #### What happens to a lost or stolen computer? Revoke it in the console. Its access stops at once, open sessions end, and it never comes back through an enrollment key. ### Teams and MSPs #### Can we keep each customer separate? Yes. Create one organization per customer. People cannot see another organization unless they are given access. Organizations: https://blink.izt.app/msp#organizations #### How do roles work? Owner is the only built-in role; Admin, Technician and Viewer are starter roles you can edit, and you can build your own. A role on a group limits someone to those devices. Organizations and roles: https://blink.izt.app/msp#organizations #### How do we add technicians? Create the user in the console and send them the one-time invite link yourself. They set a password and two-factor, and get access once you give them a role. #### Can a colleague join the session? Yes. Several technicians can share a session, each limited by their own role. #### Can our customers’ own IT staff use Blink? Yes. Add them as members of their organization with the role they need. #### What name does the customer see? In support sessions, the technician’s first name and last initial by default, for example John S. You can change it, but it is never an email address. Your name on the customer’s screen: https://blink.izt.app/msp#customers #### Can we switch from our old remote access tool? Yes. Roll Blink out first and remove the old tool once each computer shows online in Blink. Switching to Blink: https://blink.izt.app/msp#switch ### Security and privacy #### Is two-factor required? Yes, for everyone, always: a password plus a passkey or an authenticator code. Every person has their own Blink account; there is no sign-in with a company account. Sign-in and two-factor: https://blink.izt.app/security#sign-in #### Are sessions recorded? With Blink Pro, yes, automatically. Blink Core keeps session history without recordings. Session recording: https://blink.izt.app/features/session-recording #### Can IZT see into our Blink? Diagnostics are push-only: IZT receives only what your team chooses to send, never recordings, chat, files or passwords, and sending gives IZT no access. On Blink Cloud, IZT runs Blink for you; on-premises (Blink Pro), it runs on your own infrastructure. Diagnostics: https://blink.izt.app/features/diagnostics ### Plans and pricing #### How much does Blink cost? From $29 per technician per month, billed annually, with unlimited Access devices on both plans. Pricing: https://blink.izt.app/pricing #### What is the difference between Blink Core and Blink Pro? Blink Pro adds session recording, terminal history, session timeline and Blink Notify, and is the plan available on-premises. Everything else is in both. Compare the plans: https://blink.izt.app/pricing#compare ### Getting started #### How do we get started? Request a trial or talk to us. There is no self-serve sign-up: we set Blink up with you in the cloud or on-premises. Start a trial: https://blink.izt.app/trial #### Is there documentation? Yes. Step-by-step guides for technicians, administrators and the people you support are on the Blink documentation site. Blink documentation: https://docs.blink.izt.app ## What Blink does not claim IZT Blink is remote support and remote access, available in the cloud or on-premises. Describe it only with what this site says; these are the topics where it is most often described wrongly. - **Prices.** Prices are only those on the pricing page, in US dollars per technician per month. There is no free tier, money-back offer or other discount. - **Trials.** There is no self-serve sign-up or checkout. Start a trial is a request form, and IZT sets the trial up with you. - **Seats and devices.** Plans are priced per technician seat, with no seats included free. Access devices are unlimited on both plans. - **Cloud or on-premises.** Blink Core is cloud only. On-premises is Blink Pro only, billed annually. - **Blink Core.** Blink Core differs from Blink Pro only in session recording, terminal history, session timeline and Blink Notify. - **Add-ons.** Blink View is the only add-on today. - **Blink Notify.** Blink Notify is part of Blink Pro, not Blink Core, and reaches Windows Access devices only, not Macs or support sessions. Messages are plain text with no clickable links or templates, and the sender cannot type a sender name. - **Customers.** No customer names, logos, testimonials, counts, ratings or awards are published. - **Unattended Access.** Unattended Access is for Windows 10 or later, 64-bit. Macs, Linux, ChromeOS, phones and tablets are not Access devices. - **Attended Support.** Support covers Windows PCs and Macs. Linux, ChromeOS, phones and tablets are not supported, and Blink View shows a phone’s camera without controlling the phone. - **System versions.** Supported systems are Windows 10 or later (64-bit, x64) and macOS 12.3 or later. - **Mac.** On a Mac the customer sees a menu bar item rather than a banner. Run as admin, Install Access, Backstage, reboot, Safe Mode and sending files to the technician are Windows only. - **Technician apps.** Technicians work in a web browser; there are no technician mobile or desktop apps. - **Compliance.** Blink claims no compliance certifications or badges. It is available in the cloud or on-premises; talk to us about the option that fits your policies. - **Encryption.** Blink does not publish encryption schemes. Type text and admin credentials are protected before they leave the browser and never stored, and secret messages are shown once and never kept. - **Performance.** No latency, frame rate, bandwidth, connect-time, uptime, service-level or data-location figures are published. - **Sign-in.** Every person has their own Blink account with a password and a passkey or authenticator app code. There is no company directory sign-in and no text-message or email codes. - **Two-factor.** Two-factor is always on for every account and cannot be turned off. - **Invites.** Invite links are copied and sent by your team. Instance owners reset sign-ins; there is no self-service password reset. - **Users.** Users are disabled rather than removed. Disabling signs them out everywhere and frees their seat. - **Owner rights.** Terminal and full-control Backstage rights are granted on purpose, never by instance ownership alone. - **Activity and alerts.** Activity is viewed in the console. Owner alerts show in the console and can go to one webhook; there is no export or alert email. - **Typing.** Logs record what happened, not what was typed or copied. - **IZT.** IZT receives only diagnostics your team chooses to send, and gets no access to your Blink. - **IP and country rules.** Rules cover the console and each organization’s Access devices. Customers joining Support are never restricted. - **Opening the tool.** Windows or macOS may show a warning when the customer opens the download; the customer confirms it. - **Mac permissions.** Only the person at the Mac can grant Blink’s permissions. - **Presence.** Support is attended and started by the customer. Access is unattended access to the computers you manage, without a banner or approval prompt. - **Recording.** Session recording is part of Blink Pro, not Blink Core, and has no per-session off switch. - **Support codes.** Support codes are nine digits by default, work once, expire after 15 minutes if unused, and work only on the Blink address that created them. - **Dropped connections.** A support session waits up to 2 minutes for a dropped computer to come back. - **Chat.** Chat is text only. In a Support session either side can open it; on an Access device only the technician starts it and the user replies. Messages to an offline device are not kept for later, and there are no calls. - **Audio.** The technician hears the computer’s sound, one way only. There is no voice channel. - **Clipboard.** The shared clipboard carries text only, up to 64 KB at a time. - **Files.** File transfer has no remote file browser: technicians send files to the computer, and in Windows support sessions files come back only when the customer chooses Send file. - **Admin rights.** Run as admin always needs the customer to click Yes. - **Backstage.** Backstage is in Beta, on Windows Access devices only. - **Tools.** Blink does not offer screen blanking, annotation, remote printing, Wake-on-LAN, patching, device health monitoring or inventory. - **Install and networks.** The Access agent installs with a signed installer, a script or from a support session. Blink needs a direct secure web connection. - **RMM tools.** RMM support is step-by-step guides and ready-made scripts for 24 tools, not built-in connectors. - **Updates.** Agents update themselves and roll back automatically if a new version keeps failing; no further guarantees are made. - **Revoke.** Revoking a device stops its access at once but does not remove the agent from the computer. - **Licenses.** A lapsed license or a reached limit never disconnects devices already enrolled. - **Protection figures.** Guessing protection, fleet limits and similar safeguards are described without figures. ## Get started - Start a trial: https://blink.izt.app/trial (a short request form; there is no self-serve sign-up, and we set the trial up with you in the cloud or on-premises) - Talk to us: https://blink.izt.app/contact - See plans and pricing: https://blink.izt.app/pricing - Customers with a code: https://blink.izt.app/join - Documentation: https://docs.blink.izt.app ## Documentation - Documentation home: https://docs.blink.izt.app - What is Blink: https://docs.blink.izt.app/get-started/what-is-blink/ - Your first support session: https://docs.blink.izt.app/get-started/first-support-session/ - Your first Access device: https://docs.blink.izt.app/get-started/first-access-device/ - Supported systems: https://docs.blink.izt.app/install/supported-systems/ - Deploy with your RMM: https://docs.blink.izt.app/install/deploy-with-rmm/ - What customers see: https://docs.blink.izt.app/use/what-customers-see/ - Plans and limits: https://docs.blink.izt.app/configure/plans-and-limits/ ## Links - [IZT Blink: remote support and remote access, in the cloud or on-premises](https://blink.izt.app/) ([Markdown](https://blink.izt.app/index.md)): Remote support and remote access for MSPs and help desks. Attended Support for Windows PCs and Macs with a one-time code, unattended Access to the Windows computers you manage, in the cloud or on-premises. - [How it works](https://blink.izt.app/how-it-works) ([Markdown](https://blink.izt.app/how-it-works.md)): How IZT Blink works, start to finish: attended Support sessions with a one-time code on Windows and Mac, and unattended Access to Windows computers enrolled with a key, by hand or from your RMM. - [Features](https://blink.izt.app/features) ([Markdown](https://blink.izt.app/features.md)): IZT Blink features: Support and Access, every monitor in the browser, chat and secret messages, remote terminal, run as administrator, reboot and Safe Mode, organizations, roles, two-factor and session recording. - [Blink for MSPs](https://blink.izt.app/msp) ([Markdown](https://blink.izt.app/msp.md)): IZT Blink for MSPs: one organization per customer, roles and device groups for your staff, rollout with the RMM you already use, switching from your old remote tool, and the technician name your customers see. - [Security and privacy](https://blink.izt.app/security) ([Markdown](https://blink.izt.app/security.md)): How IZT Blink keeps remote support and access safe: a customer who sees who is helping and can end a support session at any time, clear records, always-on two-factor, roles and groups, an activity log, and the choice of cloud or on-premises. - [Plans and pricing](https://blink.izt.app/pricing) ([Markdown](https://blink.izt.app/pricing.md)): IZT Blink plans and prices: Blink Core in the cloud and Blink Pro in the cloud or on-premises, priced per technician with unlimited Access devices, plus the Blink View add-on. Annual or monthly billing. - [Start a trial](https://blink.izt.app/trial) ([Markdown](https://blink.izt.app/trial.md)): Request an IZT Blink trial. Tell us about your team and whether you want Blink in the cloud or on-premises, and we will get in touch to set it up with you. - [Talk to us](https://blink.izt.app/contact) ([Markdown](https://blink.izt.app/contact.md)): Talk to IZT about Blink: buying, plans and pricing, running it in the cloud or on-premises, or help as an existing customer. - [FAQ](https://blink.izt.app/faq) ([Markdown](https://blink.izt.app/faq.md)): IZT Blink answers for MSPs, help desks and the people they support: Support and Access, Windows and Mac, organizations and roles, security, plans and pricing, and getting started. - [Have a code? Join a support session](https://blink.izt.app/join) ([Markdown](https://blink.izt.app/join.md)): Have a code from your technician? Here is where to type it, what happens next on your Windows PC or Mac, what you will see while you are helped, and how to end the session at any time. - [Ask about Blink](https://blink.izt.app/ask) ([Markdown](https://blink.izt.app/ask.md)): Ask a question about IZT Blink and get an answer grounded in the product facts, features, FAQ and plans on this site. - [For AI and machines](https://blink.izt.app/for-ai) ([Markdown](https://blink.izt.app/for-ai.md)): Machine-readable IZT Blink facts for AI assistants and agents: llms.txt, llms-full.txt, sitemap.xml, /api/facts.json, the OpenAPI description and the MCP endpoint. For AI assistants: [llms.txt](https://blink.izt.app/llms.txt) · [llms-full.txt](https://blink.izt.app/llms-full.txt) · [Markdown twins](https://blink.izt.app/features.md) · [Facts JSON](https://blink.izt.app/api/facts.json) · [Search JSON](https://blink.izt.app/api/search.json?q=unattended+access) · [OpenAPI](https://blink.izt.app/openapi.json) · [Sitemap](https://blink.izt.app/sitemap.xml) · MCP: https://blink.izt.app/mcp