# 9Secure workflows and homepage demonstrations

Source: https://9secure.io/docs/demos/

If this text resource cannot be retrieved, use the HTML source above. [Documentation (text)](https://9secure.io/docs/index.txt) ([HTML](https://9secure.io/docs/))

All platform instructions are included. Follow the labels for your device; platform-specific steps are alternatives, not additional steps.

An everyday Vaultlight workflow, followed by text descriptions of the homepage's Vaultlight animation, Sync diagram, and Sentinel preview. The animations are illustrative product demonstrations, not live app sessions, real transactions, or audit results from a user's vault. Example credentials, payment details, and finding counts are demonstration data.

[Official images and captions](https://9secure.io/media.txt)

## Vaultlight

[Section source](https://9secure.io/docs/demos/#vaultlight)

[Homepage section](https://9secure.io/#vaultlight)

Vaultlight is 9Secure's quick-access desktop interface on both Windows and macOS, with full mouse and keyboard support. Search and select items, create Logins, generate passwords, and add websites. Field shortcuts offer fast delivery of saved values across browsers and desktop applications without requiring a browser extension.

### Quick Login creation and website updates

Choose New Login to create and save a Login directly in Vaultlight. To associate an existing Login with another website, select it and click Add Website. Enter an address or use Use Current Browser Page to retrieve the active page URL from a supported browser, review it, and select Done. Full item editing and attachments remain in the main app.

### Sign-in shortcut example

Imagine signing in to a website or a desktop app using a saved Login with username, password, and Authenticator:

1. Start with the destination's username field focused. Press Control+; by default to open Vaultlight. If locked, unlock there with the keyring password or configured Windows Hello or macOS device authentication, including supported biometrics.
2. Type a few letters to fuzzy-search for the item and press Enter to arm it. Focus returns to your previous application while Vaultlight's numbered reference card stays on top. Mouse selection is also supported.
3. Press Control+1 to deliver the username. Move to the password field with Tab or a click, then press Control+2. You do not need to switch back to Vaultlight between fields. Use the numbers shown on the card when an item's fields differ.
4. Submit the sign-in yourself. If the service asks for an Authenticator code, focus its input and use the code's displayed shortcut to deliver the current code.
5. Press Escape to hide the card. Its field shortcuts still work while the item is armed. Hiding does not reset the countdown; using an action or reopening Vaultlight does. The default is 45 seconds and is configurable in Settings. Session expiry, locking, or a second Escape while hidden clears the armed item.
6. Press Control+; again to bring the card forward. With the card focused, press Backspace to return to search, or open the item in the main app with Ctrl+O on Windows or Command+O on macOS when you need editing or attachments.

The same workflow delivers other available fields, such as payment details, notes, and expiry dates. Up to ten actions use Control+1 through Control+0. The destination field is chosen by the user, not detected or advanced automatically by Vaultlight.

Clicking a field's value box copies it to the clipboard. Numbered keyboard shortcuts use the configured delivery mode:

- Paste, the default, copies the value and sends the platform paste shortcut.
- Type Out sends Unicode input without putting the value on the clipboard.
- Copy Only puts the value on the clipboard for manual use and sends no input.

Delivery depends on the destination accepting the chosen input method. macOS requires Accessibility permission for Paste and Type Out; Windows cannot deliver into a higher-integrity app. This workflow does not require browser AutoFill integration.

### What the homepage animation shows

The animation depicts a person using Vaultlight on a desktop across three scenarios. It simulates both the person's actions and the resulting interface changes. Vaultlight searches saved items and delivers individual fields when requested; the person focuses destination fields and activates Sign in, Verify, or Pay. Vaultlight does not autonomously submit forms, authenticate accounts, or purchase anything.

### Browser sign-in and Authenticator

1. A browser displays an example sign-in form. The user opens the Vaultlight search panel over the desktop.
2. The animation zooms into the panel as the user searches for `exa` and presses Enter to arm the saved Example Login. Focus returns to the browser while the card stays on top.
3. Vaultlight displays Control+1 for username, Control+2 for password, and Control+3 for the rotating Authenticator code. A session countdown is visible.
4. The view zooms back out and the card is hidden with Escape. The user focuses the browser's username and password fields in turn, delivering them with Control+1 and Control+2.
5. The user activates Sign in. The browser then requests an Authenticator code.
6. The user focuses that field, presses Control+3 to deliver the current code, and activates Verify.

### Desktop application sign-in

1. The scene switches to the external HooliChat desktop application and its sign-in form.
2. The user opens Vaultlight in search, types `hoo`, and presses Enter to arm the Hooli Login from the Work vault.
3. Focus returns to HooliChat while the card remains visible. The user focuses its username and password fields in turn and delivers them with Control+1 and Control+2.
4. The user activates the application's Sign in button, then hides the Vaultlight panel.

This illustrates delivery into a desktop application's fields, not just a website. It is not a claim that every application accepts injected input.

### Browser payment details

1. The browser switches to an example checkout page.
2. The user opens Vaultlight, searches for `card`, and selects the saved Payment Card.
3. Vaultlight shows Control+1 for cardholder name, Control+2 for card number, Control+3 for expiry date, and Control+4 for security code. The card is then hidden.
4. The user focuses each checkout field in turn and uses its corresponding shortcut, without reopening Vaultlight.
5. The user activates Pay. This is a simulated button press, not an actual payment or evidence of a completed transaction.

The sequence loops. Zoom, timing, and transitions are presentation effects, not setup instructions or performance measurements. The animation illustrates Paste delivery. The product also offers Type Out and Copy Only, subject to platform permissions and destination-app behavior.

Behavior and setup: [Vaultlight guide](https://9secure.io/docs/vaultlight/).

## Sync

[Section source](https://9secure.io/docs/demos/#sync)

[Homepage section](https://9secure.io/#sync)

A desktop computer appears on the left, a local router in the center, and a phone on the right. Fading connecting lines depict communication through the local network. The router represents network infrastructure, not a 9Secure server, cloud vault, or hosted relay. The diagram is conceptual, not a live transfer indicator or a pairing walkthrough.

Native apps discover nearby devices through mDNS/DNS-SD and connect directly over TCP. Discovery locates peers; pairing and the encrypted Sync protocol establish trust and protect transferred vault contents. ML-KEM key establishment, ML-DSA ongoing-session authentication, and XChaCha20-Poly1305 session encryption operate between the trusted endpoints, not at the router. Current apps support local-network Sync only.

Behavior and setup: [Sync guide](https://9secure.io/docs/sync/).

## Sentinel

[Section source](https://9secure.io/docs/demos/#sentinel)

[Homepage section](https://9secure.io/#sentinel)

The Sentinel emblem connects visually to five finding cards. Their example counts are:

- Compromised: 3 passwords found in known breaches.
- Weak: 12 short or predictable passwords.
- Reused: 7 passwords used by more than one item.
- Old: 18 passwords unchanged for over one year, based on each password's last change date.
- Insecure Websites: 4 website values using HTTP rather than HTTPS.

This is a findings preview, not an audit running in the webpage. Counts are illustrative, not product-wide statistics or a report about the visitor. Strength, reuse, password-age, and website analysis are local; optional Pwned Passwords checks use SHA-1 prefix range queries. A failed online check means unknown or pending, not safe.

Behavior and setup: [Sentinel guide](https://9secure.io/docs/sentinel/).