PhishClean for TeamsHelp

Open your admin link

This page opens from the private admin link you saved when you started your pilot. Lost it? Write to us from your admin email and we'll send a new one. No pilot yet? Start one.

Thanks, your payment went through. Your plan updates here within a minute or two.
Your pilot has ended. Protected browsers have dropped to PhishClean's free plan. Subscribe below to turn every check back on.
Status
Browsers protected
checked in during the last 30 days
Seats

Subscribe

Choose a plan and the number of people to cover (minimum 5). You can change seats later.

Request an invoice

Billing

Change number of seats

Your organisation key

Put this in browser policy on every managed machine. It only adds browsers to your plan; it can't read or change anything. If it leaks, rotate it and update the policy.

Deploy to your browsers

Force-install PhishClean and set orgKey. Optional: add trustedDomains for your own sign-in and internal sites. Within minutes the popup on a managed browser reads "Team, ".

  1. In the Google Admin console go to Devices → Chrome → Apps & extensions → Users & browsers and pick the organisational unit.
  2. Click + → Add Chrome app or extension by ID, enter kloceclooedmphmnnpgoekolaggejgca, from the Chrome Web Store.
  3. Set Installation policy to Force install.
  4. In Policy for extensions, paste:

Applies to managed Chrome browsers (Chrome Browser Cloud Management) and to users signed in with your Workspace accounts.

  1. Download the registry file below. It force-installs PhishClean in Chrome and Edge and sets your key for both.
  2. Group Policy: deploy it with a GPO (Computer Configuration → Preferences → Windows Settings → Registry), or import it on a single PC by double-clicking it.
  3. Intune: Devices → Scripts and remediations → Platform scripts → Add (Windows 10 and later), upload the PowerShell script below, run it in the system context.
  4. Restart the browser, or open chrome://policy / edge://policy and click Reload policies.

What the file sets:

  1. In your MDM (Jamf, Kandji, Intune for macOS...), create a configuration profile with a custom settings payload.
  2. Chrome, preference domain com.google.Chrome: set ExtensionInstallForcelist to the array below.
  3. Chrome, preference domain com.google.Chrome.extensions.kloceclooedmphmnnpgoekolaggejgca: set orgKey (string) to your key.
  4. Edge: the same with com.microsoft.Edge and com.microsoft.Edge.extensions.jeilenifcaoenlglebpmmphbfmbfkgbj.
  1. Add this to policies.json (in the Firefox install's distribution folder), or set the same values with Firefox's Group Policy templates.
  2. If you already have a policies.json, merge the ExtensionSettings and 3rdparty sections into it.

Admin email: . Keep this page's link private: anyone with it can manage your plan.