Security FAQ for i3CONNECT displays

These FAQ are useful when your i3CONNECT display is used by multiple people (classrooms, meeting rooms, training spaces) and you want to keep settings, accounts, and shared content protected without making the display harder to use.

Frequently Asked Questions

How do I control who can change display settings?

• Set an Admin settings PIN so only authorised people can change sensitive display settings. → Admin settings PIN

• Use Restricted Mode for public spaces and unsupervised rooms to limit access to settings entirely. → Restricted Mode

• More complex settings require the right access level. If you can't reach a setting you expect, verify you're signed in with an administrator profile.

How do user profiles and passwords work?

• i3CONNECT supports segmented user profiles: administrators, ordinary users, and guest users.

• Administrator and ordinary user profiles are protected by usernames and passwords (guest access is not).

• Use User Profiles for Regular Users to keep settings and personal data separated per person. → User Profiles for Regular Users

• Use Guest Mode for shared rooms so temporary users don't leave behind files, logins, browsing history, cache, or Studio settings. → Guest Mode for shared rooms

• Log out after every session (especially in shared rooms) to remove guest data and lock profile data. → Log out after every session

• If staff are changing settings they shouldn't, move them to a lower-rights profile and restrict administrator access.

How are updates managed, and who can change what?

• i3CONNECT displays ship with factory-installed firmware and software inspected and approved by i3CONNECT Quality Assurance in Europe.

• Updates and upgrades happen automatically, reducing the risk of unsafe changes. Keep firmware up to date for the latest fixes and security improvements.

• If you need tighter change control (e.g. approval windows), align with your internal IT policy. If your environment blocks updates, contact i3CONNECT support.

• Register displays in i3CONNECT Cortex so IT can manage security settings and updates at scale. → Register displays in Cortex

• How-to: Why you should install the latest firmware · Update during installation (OTA)

What does the Setup Wizard cover?

• The Setup Wizard handles non-technical first-time setup: language, time, network, enrolment, and basic preferences.

• Users can define UI preferences such as quick launch buttons and theme.

Is any personal data stored on the display?

• No personal user data is stored on the display.

• Whiteboard and annotation screenshots can be shared locally and/or stored on protected network storage if your organisation chooses.

• Locally shared screenshots expire after 4 hours and are removed from the system.

• No hidden "backdoor" communication or test routines are implemented.

How are data, passwords, and backups encrypted?

• External network communication is encrypted (e.g. HTTPS/TLS) using 256-bit AES.

• User passwords are not stored in a machine-readable format.

• Backups are stored encrypted.

• User data is not accessible to unauthorised third parties.

• If your security team needs deeper detail (cipher suites, endpoints, retention, logging), request the relevant security documentation from i3CONNECT support.

Where is data hosted, and which third-party services are used?

(current at time of publication)

• Cloud hosting is based on Amazon Web Services (AWS), hosted in an Amazon data center in Ireland.

• Only a limited number of people have access to the infrastructure, with no means to download, decrypt, or read sensitive information on the server.

• Internal IT security policy applies a zero-trust approach: strict access management shields environments, databases, and infrastructure from unauthorised access.

• For remote connectivity and mailing: Twilio and Sendgrid (no user data stored there).

• For identity management (Cortex user profiles, Whiteboard cloud credentials): http://auth0.com .

What are the firewall requirements?

• Check firewall requirements early to prevent connectivity issues. → Firewall requirements

Security FAQ with how-to links