Search
Search Blink
Features, plans, FAQ and security details, straight from the facts this site is built on.
7 results for unattended access
Security 7
- Security
Clones do not inherit access
Cloned disks and virtual machines do not inherit access, and the console flags a possible clone.
/security#top
- Security
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.
/security#sign-in
- Security
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 cann…
/security#sign-in
- Security
Organizations kept apart
One organization per customer. People cannot see another organization unless they are given access.
/security#top
- Security
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.
/security#access-control
- Security
Fleet limits
Cap how many Access sessions, reboots and chats one person can start in an hour. Over the limit is refused and the owners are alerted.
/security#top
- Security
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.
/security#records
Prefer a direct answer? Ask Blink: “unattended access”