SentinelLolge logo

SentinelLolge

Security, Built-In

Loading open with sentinellolge page

Use case / Drive opening

Open protected files from your Cloud Storage

Protected files stored in Google Drive open directly in SentinelLolge. Clients choose Open with SentinelLolge on the file, sign in with the Google account that has access to it, and unlock it in a secure viewer where decryption happens on their device.

Opens from Google Drive

Right-click a protected file in Drive, choose Open with SentinelLolge, and continue with the Google account that has access to it.

Decrypts on your device

The file password is still required, and the unlocked content never leaves the browser. Protected files are never uploaded to SentinelLolge.

Handles large and strict files

Large exports open in one step with their companion attached automatically, and strict controls such as expiry and unlock limits stay enforced.

How this workflow works

Practical guidance for Open with SentinelLolge

How Open with SentinelLolge works

The recipient finds the protected file (.html or .zip) in Google Drive and chooses Open with SentinelLolge from the right-click menu → Preview → SentinelLolge. The secure viewer asks them to continue with the Google account that has access to the file they want to open with SentinelLolge, loads the encrypted file from Drive, and shows the unlock page. If a large export came with a companion file, selecting both files before choosing Open with keeps the handoff to a single step, and files the app can already reach have their companion attached automatically. From there the experience matches opening a local protected file: enter the password, preview the content, and use only the actions the sender allowed.

Why opening happens in a separate secure viewer

Cloud storage previews run inside a restricted frame that cannot reliably unlock protected files, especially strict exports and large exports with a companion file. The secure viewer therefore runs on a dedicated page that stores no account data, so the protected file opens with full unlock, preview, and strict-check support instead of the limits of a storage preview. The separation also keeps the main SentinelLolge account sessions away from the opened file. Passwords and unlocked content stay in the browser throughout.

What stays enforced, and what is coming next

Opening from Drive does not loosen the protection. Download settings, read-only presentation, expiry windows, incorrect-attempt limits, and strict unlock checks behave exactly as the sender configured them. Recipients do not need a SentinelLolge account for ordinary protected files, only the Google account that can access the Drive file and the file password from the sender. Google Drive is supported now, and OneDrive and Dropbox will be supported soon. Files kept outside cloud storage can still be opened by dropping them into the same secure viewer.

Related pages

Continue through the SentinelLolge crawl path

Frequently asked questions

Open protected files from your Cloud Storage FAQ

How do I open a protected file from Google Drive?

In Google Drive, right-click the protected file → menu → Preview → SentinelLolge. Continue with the Google account that has access to the file, then enter the file password in the secure viewer to unlock it.

Do recipients need a SentinelLolge account to open from Drive?

No. Ordinary protected files need no SentinelLolge account. Recipients only need the Google account that can access the Drive file and the file password from the sender.

What if the export came with a companion file or a zip?

Select both the protected file and its companion file in Drive before choosing Open with SentinelLolge. When the companion sits next to the file and the app can reach it, it is attached automatically. Zipped exports open the same way through the secure viewer.

Is OneDrive or Dropbox supported?

Not yet. Google Drive is supported now, and OneDrive and Dropbox support is coming soon. Local files can already be opened by dropping them into the secure viewer.

This HTML exists as a branded search-friendly fallback while the Flutter app loads. The visible structure preserves current public content for crawlers without depending only on Flutter-rendered text nodes, and it now includes keyword-targeted guide routes as dedicated HTML templates.