Understand your plan and its limits

Your Blink license carries your plan: which Blink features your server offers, how many technician seats it has, and how many Access devices can enroll. IZT sets the plan when it issues the license. You see it on Instance › License, next to the license status. See Check and renew your license for the rest of that page.

Blink Core and Blink Pro

The Plan row on the License card names your plan: Blink Core or Blink Pro. If your license includes add-ons, they follow the plan name, joined with a plus sign.

Blink Pro is Blink Core plus three features that keep a record of each session:

Feature	Blink Core	Blink Pro
Session recording: record new sessions (video and audio)		✓
Terminal history: keep transcripts of new terminals		✓
Session timeline: a detailed timeline and session log for new sessions		✓
Everything else listed below	✓	✓

Below the card details, the License page lists every feature by group, ticked when your plan includes it and greyed out with a dash when it does not:

• Session modes: Unattended Access, Attended Support.
• Session capabilities: Remote control, File transfer, Clipboard sync, Remote terminal, Backstage, Power actions, Elevation, Install Access from Support, Remote audio, Chat, Secret messages.
• History: Session history, Session timeline, Session recording, Terminal history.
• Administration: Multiple organizations, Custom roles, Audit log, Tech name, IP and country rules.

The Limits, Technician seats and Access devices, appear as rows on the card itself.

Chat and Secret messages are part of both Blink Core and Blink Pro. Secret messages need Chat as well. If your License page does not tick them, contact IZT. See Chat with the customer.

A license can also leave out one of the session modes, for example a plan with Attended Support only and no Unattended Access. The checklist always shows what your own license includes.

Technician seats

Every user account takes a technician seat: administrators and pending invites included. Disabled users do not take a seat.

• At the limit, creating a user is refused, and so is enabling a disabled user: the user stays disabled.
• If you can see the license, the Users page header shows how many seats are in use, for example 8 of 10 seats. When every seat is taken, New user is greyed out.
• To free a seat, disable or delete a user you no longer need. See Add and manage users.

The Technician seats row on the License card shows the same count, for example 8 of 10, or a number with (unlimited) when your plan has no limit.

Access devices

Every enrolled Access device counts against the Access devices limit, unless it is revoked or uninstalled.

At the limit, Blink refuses:

• a new enrollment,
• an uninstalled device enrolling again,
• Un-revoke on a revoked device.

Devices already enrolled keep working: Blink never drops a device because of the limit. Enrollment keys are not devices, so you can still create keys at the limit.

When an enrollment is refused at the limit, instance owners get an alert, Device limit reached, at most once an hour. On the computer, the Access agent install stops with exit code 20 and the message This Blink plan’s device limit is reached. Ask your administrator. See Install the Access agent on Windows.

To free a device, revoke or delete one you no longer need. See Manage Access devices.

When something is not in your plan

Blink hides or marks what your plan does not include:

• Whole sections disappear when there is nothing left to do in them. Enrollment is gone from the sidebar without Unattended Access, and Activity without Audit log.
• A callout names the missing feature on the page it affects, for example Not included in your plan: Session recording, with a line on what that means.
• A pill replaces a button, for example Custom roles: not in your plan in place of New role.

If an action reaches the server anyway, the console shows the server’s answer:

Message	Meaning
Your plan does not include feature. What it does. For example: Your plan does not include Session recording. Record new sessions (video and audio).	The feature is not in your plan.
Your plan includes N technician seats and M are in use. Technician seats: ask your provider to raise the limit.	Every technician seat is taken.
Your plan includes N Access devices and M are in use. Access devices: ask your provider to raise the limit.	The Access device limit is reached.

A permission that needs a feature your plan lacks does nothing while the plan lacks it. The person keeps the permission, and it works again once the feature is back in the plan. See Roles and permissions.

Without a valid license, either before activation or when the license shows Not valid, nothing in the plan is available: the console marks everything as not in your plan, and Support codes, enrollment and new users are refused. See Activate your license.

When you change plans

To change plans, or to add technician seats or Access devices, contact IZT. The new plan arrives with your next license: through automatic renewal, when an instance owner selects Renew now, or through the offline renewal exchange. See Check and renew your license.

When the plan changes:

• Sessions in progress keep what they started with until they end. New sessions, and new viewer connections, follow the new plan.
• Each session keeps the record it started with. A session started without recording or a timeline stays without one after an upgrade, and a session started with them keeps them after a downgrade.
• Existing recordings, terminal transcripts and timelines stay. You can still play, download and delete them after a downgrade.
• Over the limit after a downgrade, nobody is locked out and no device is dropped. A banner tells everyone who can see the license, for example 12 users for 10 technician seats: new users are refused until you are under the limit. or 60 Access devices for 50: new enrollments are refused until you are under the limit. New users or enrollments are refused until you are back under the limit.

Who can see the plan

The License page, and with it the plan, seat and device counts, needs the View license permission. Instance owners have it. Anyone else gets it from an instance role given for all organizations on the Users page; none of the starter roles includes it. See Instance roles and organization roles.

When Blink was upgraded to a version with plans, every role that had the Instance settings permission was given View license as well.