# What IZT Blink is

IZT Blink is remote support for help desks, IT teams and managed service providers. Your technicians work from a browser. The people and computers they help are on Windows or Mac.

Blink does two jobs:

| | Support | Access |
| --- | --- | --- |
| **What it is** | Attended help. Someone at the computer asks for help and lets you in. | Unattended access to computers you manage, whether or not anyone is there. |
| **How it starts** | You create a Support code in the console. The customer enters it on your Blink address and runs the small support tool it downloads. | You install the Blink agent once on the computer with an enrollment key. From then on it shows in the console under **Access**. |
| **What stays on the computer** | Nothing is installed. Closing the tool ends the session. | The agent stays installed and starts with Windows. |
| **Platforms** | Windows and Mac | Windows |

## What every session gets

- **Screen and control.** You see every monitor of the remote computer in your browser and use its mouse and keyboard. Clipboard, file transfer and typing text into password fields are built into the viewer.
- **Transparency for the customer.** During a Support session on Windows, a banner on each screen you watch says a technician is viewing it, shows a **Recording** indicator, and has an **End** button. On a Mac, Blink shows in the menu bar, where the customer can choose **End session**.
- **A recording** (Blink Pro). Every monitor you watch is recorded automatically, with the session's audio as a separate file. You can watch a recording while the session is still running.
- **A log** (Blink Pro). Every session has its own timeline and session log, open from the session's row in the console.
- **A check before control.** In a Support session, the viewer first shows you the computer's name, the signed-in user and the system, and asks **Is this your customer's computer?** Your mouse, keyboard, clipboard and files reach it only after you click **Confirm and take control**.

## Plans

Blink comes in two plans, **Blink Core** and **Blink Pro**. Blink Pro adds session recording, terminal history and the session timeline. Your plan also sets how many technician seats and Access devices you have. See [Understand your plan and its limits](/configure/plans-and-limits/).

With the Blink View add-on, a customer can also show you their phone camera from a web page on the phone during a session. See [See the customer's phone camera with Blink View](/use/blink-view/).

## Organizations, teams and roles

Blink keeps work separated by **organization**: one per customer, each with its own team, groups and devices. People sign in with their own Blink account, always with two-factor authentication. What each person can do is set by **roles**, given for a whole organization or for one group of devices.

## Cloud or on-premises

Blink is available in the cloud or on-premises. Either way, you reach it at **your Blink address**, for example `https://yourname.onblink.cloud`. That one address serves:

- the **join page**, at the address itself and at `/join`, where customers enter a Support code,
- the **technician console**, where your team signs in at `/login`.

The two differ only in setup:

- **Blink Cloud.** IZT runs Blink for you. You get an email with a setup link, and your license is activated for you once setup is done.
- **On-premises.** Blink runs on your own server. You activate the license yourself, online with an activation code or offline with a license file.

## Next

- [Set up Blink and sign in for the first time](/get-started/first-sign-in/)
- [Run your first Support session](/get-started/first-support-session/)