Protected Content lets administrators add an extra security layer to Hub pages and files. Users must authenticate before accessing protected content, and optionally must meet a minimum device OS version requirement.
How does Protected Content work? An Organization Admin sets an org-wide policy in the Admin portal, then marks individual Hub pages or files as protected. When a user opens protected content, Blink checks their device against the policy before allowing access.
✅ In short
• Set the policy once in the Admin portal under Content Security
• Mark individual Hub pages or files as protected via their ··· menu
• Users are prompted to authenticate before opening protected content
• Protected content is not accessible in Kiosk mode
⚠️ Organization Admins only. Setting up the Protected Content policy and marking content as protected requires Organization Admin access.
🛡️ How do I set up the Protected Content policy?
This covers the org-wide policy. Individual pieces of content are protected in the next section.
Go to the Org Setup section of the Admin portal.
Scroll down to Protected Hub content policy in the Content Security section.
Click Change.
A panel opens where you can configure what users must do to open protected content.
Passcode and Biometrics - users must confirm their identity via fingerprint or facial recognition, or another secure form of mobile authentication.
Minimum OS Version - enter minimum versions for iOS and Android SDK, including the Android Security Patch. When a user opens protected content, Blink checks their device OS against these values. Refer to apilevels.com for an up-to-date list of Android versions and SDK levels. The image below shows the format Blink accepts.
Click Update.
🔒 How do I protect individual Hub content?
Locate the content in Hub admin and click the ··· menu.
Turn on Protect File.
Click Share or Update.
The content is now protected by your org policy.
📱 What does the user experience look like?
Protected content in the Hub is marked with a Protected label.
When a user opens protected content, they may be prompted to:
Update their OS - if their device is running an older version than the minimum set by your organization, they will be asked to update before they can proceed.
Secure their device - if no security is set up on their device, they will be asked to add a passcode or biometric before they can proceed.
🤔 Having trouble accessing protected content? Speak to your manager or IT team.
❓ FAQs
If I share protected content to the Feed, does it stay protected?
If I share protected content to the Feed, does it stay protected?
Yes. Protected content previews are hidden on the Feed. Users will see an attachment and must authenticate to view the content.
Can users access protected content in Kiosk mode?
Can users access protected content in Kiosk mode?
No. Kiosk mode devices cannot confirm user identity, so protected content is not visible in Kiosk mode. If the Kiosk device is also running an outdated OS, it will be blocked on both grounds.
Does Protected Content work on desktop?
Does Protected Content work on desktop?
No. Protected Content applies only when accessing Hub content via a mobile device.
🚀 What's next?
Set up biometrics or passcode - Using biometrics and passcodes to secure Blink
Require staff to acknowledge content - Mandatory Reads
Understand admin roles - Roles and Permissions