Deploying the extension manually
This page includes:
About deploying the extension manually
Manual vs Managed deployments
The extension can be deployed either manually, or by using a UEM solution - for managed deployment:
-
Manual deployment: Manual deployment is recommended for PoC deployments only. The deployment is performed primarily by the end-user - whose browser will be protected by the extension. Details about manual deployment are included on this page.
For information about how to deploy the extension using scripts - without a UEM, see Deploying the extension using scripts.
-
Managed deployment: The deployment is performed via a UEM solution, such as Intune, Google Workspace, JumpCloud, or Jamf.
For details on the managed deployment procedures, see Deploying the extension [Managed deployment].
Additional information
-
After initial installation, the extension is periodically automatically updated - as required.
-
For details on installation requirements for the extension, see Installation requirements.
-
An organization token is not required.
-
Unattended activation is not available.
-
User authentication is usually performed via an email verification code, but SAML authentication can also be configured.
Important:
|
More about manual deployment
The manual deployment methods are typically useful in smaller organizations and PoC evaluations.
-
The manual deployment methods require co-operation and input from end-users. The end-users must deploy the extension on all browser profiles that they want to protect [see Deploying the extension manually below]. The end-users must also manually sign-in to the extension in each of these profiles - to activate the extension.
-
The manual deployment methods may be used for contractors that are required to use the extension. In such scenarios, you can configure conditional access so that users will need to have the extension installed in order to be able to access specified websites. For details, see Conditional Access Integration.
-
For commercial applications [not PoC], it is recommended that you use a managed deployment option [or deployment using scripts] to deploy Advanced Browser Security - and not a manual deployment method.
Multiple browser profiles
The manual extension deployment methods deploy the extension on the active browser profile only. The extension isn't deployed on other non-active profiles. For full protection of any device, make sure to repeat the end-user portions of the extension deployment procedures [below] on all browser profiles that you want to protect.
If a browser profile is added in the future, that profile won't be automatically protected by the extension. The extension must be manually added to the new profile using the procedures described below.
To mitigate the complexity of managing multiple profiles, you can use a managed deployment method to deploy the extension on the device level. This will add the extension to all browser profiles of all users of the device. See Deploying the extension [Managed deployment].
Note: If a user has multiple protected browser profiles, information for all protected browser profiles will appear under the same user [email address] in the Users page in the Advanced Browser Security console [and in other places inside the console].
Manual deployment methods
The extension can be deployed manually using the following methods:
Manual deployment - using email invitations
Type of deployment |
Browsers |
Operating Systems |
|
---|---|---|---|
Manual deployment - using email invitations ![]() ![]() You can use email invitations to manually deploy the extension to browsers. You use the Advanced Browser Security console to send the email invitations to the end-users. The invitations will invite the end-users to install the extension and to then sign-in to the extension [to activate the extension]. You can send invitations to multiple users at the same time. This simplified user/extension onboarding mechanism is typically useful in smaller organizations and PoC evaluations.
Step 1: Performed by an admin user
Step 2: Performed by the end-users After the end-users receive the invitation email, they will need to:
Repeat Step 2 for each browser profile that the end-user wants to protect.
|
|
|
Manual deployment - using a store link [Safari]
Type of deployment |
Browsers |
Operating Systems |
|
---|---|---|---|
Manual deployment - using a store link [Safari] ![]() ![]() End-users can manually add the extension to Safari browsers. This simplified user onboarding mechanism is typically useful in smaller organizations and PoC evaluations.
Step 1: Add new users
Step 2: Get and distribute a link to the extension in the Mac App Store
Step 3: Performed by the end-users Users will need to:
Step 4 Repeat Step 3 for each browser profile that the end-user wants to protect.
|
|
|
Extension deployment status
The orange "Advanced Browser Security" icon on the right of the browser toolbar indicates if the extension has been installed, and if the extension has been activated:
The extension has been deployed - but not yet activated |
|
The extension has been deployed - and activated |
|
See also: