Browser extension

Overview

The elba browser extension brings browser activity into the same workspace where your team manages SaaS security, employee risk, and automated security workflows. It gives administrators an additional source of context for understanding application usage, reviewing browser security signals, and following extension deployment across the organization.

The extension is designed for managed organizational use. After it is deployed, each user signs in to connect their browser session to the correct elba workspace.

What the extension adds to elba

Depending on the browser security features configured for your workspace, the extension can help you:

• Understand the web applications employees use, including previously unknown applications.
• Surface sensitive-data signals in supported AI application workflows.
• Inventory installed browser extensions and the permissions they request.
• Review relevant browser activity in elba's browser logs.
• Track extension enrollment and deployment status by user.
• Notify selected users when they still need to install the extension.

For a closer look at the available signals and administrative views, see Browser extension capabilities.

How it works

1. An administrator activates and configures Browser Security in elba.
2. The extension is distributed through an available enterprise deployment method or shared with users for manual installation.
3. Users sign in to associate the extension with their elba account and workspace.
4. The extension receives the workspace's browser security configuration and reports relevant security signals to elba.
5. Administrators review activity, deployment status, and follow-up actions from the elba dashboard.

The extension needs a valid signed-in session and a working connection to elba for network-backed features. If that connection is temporarily unavailable, the extension displays its connection state so the user knows that attention may be required.

Plan your rollout

Before deploying broadly:

1. Choose a small representative group of users and devices.
2. Select the deployment method that matches how those browsers are managed.
3. Confirm that users can install or receive the extension and sign in successfully.
4. Check that extension status and expected browser activity appear in elba.
5. Expand the assigned group after validating the pilot.

The elba Deployment Center provides the current values and downloadable artifacts for each supported method. Follow Deploy the browser extension rather than reusing values from an older rollout.

Next steps

• Review Browser extension capabilities.
• Follow Deploy the browser extension.
• Learn how Playbooks organize automated security workflows.
• Use Troubleshooting if installation or sign-in does not complete as expected.