What is the Push browser extension and what does it do? (For admins)

Why do I need to install the browser extension?

The Push browser extension gives you visibility of what SaaS platforms your employees are accessing via their browser and how securely they are interacting with them. 

By collecting this data, you are able to see via the Push platform:

  • What SaaS platforms your employees are logging into using usernames and passwords.

  • Whether they are using strong passwords.

  • Whether they are sharing passwords between SaaS accounts.

You can also use Push's in-browser prompts feature, currently available in early access as part of Push Labs, to nudge employees to change weak passwords at the moment of login.

In the future, you will be able to see:

  • Whether your employees are using passwords that have been exposed in a data breach, a feature powered by Have I Been Pwnd.

  • Whether employees are using a password manager.

  • You'll also be able to configure a list of custom terms to restrict from use in passwords, such as common company or team names that are easily guessable.

Based on the information the Push browser extension collects, you can identify security issues that present a risk to your business and guide your employees to fix them using the ChatOps feature.

How does the browser extension work?

Once installed, the extension sits in the background of your employees’ browsers and collects the following data:

Browser information:

  • The name of the browser.

  • The version of the browser.

  • The OS name.

  • The version of the Push browser extension installed.

When logins occur into SaaS applications using corporate accounts, the following is collected:

  • The platform URL.

  • The account username.

  • A shortened salted hash of the password is stored locally in the browser - but not sent anywhere.

  • If the password is shared with any other accounts by the user. This check is performed locally within the browser and no comparisons are done server-side.

  • Whether the password was entered manually or auto-filled/pasted.

When an employee visits an OAuth consent screen for a Microsoft 365 or Google Workspace app integration page, the extension collects basic telemetry about the integration that Push uses to research it, such as establishing whether it has a verified publisher. The data the extension collects in this case is:

  • The platform the app was observed on.

  • The app identifier.

  • The grant type requested.

  • The reply URL.

  • The scopes requested.

The browser extension also collects anonymized performance and error tracking data using Sentry.

Here are some examples of how the browser extension collects data:

Browser data:


Login data:


Privacy and security 

The browser extension is configured to only monitor logins into work applications where your employees are using their work email address. Logins using personal email addresses are not monitored by the browser extension.

If your employees want to ensure even further privacy, they can create a separate work profile in their browser and install the extension there. This allows them to separate their browsing for work and personal use. The extension will never send their passwords anywhere.

For more details about how the Push extension securely tracks reused passwords, refer to this related knowledge article.

Version updates 

When new versions of the Push browser extension are released, it is automatically updated without any actions being required of you or your employees.