Browser Extension Enterprise Deployment | Overview

Summary

The CerteroX Browser Extension can now be deployed without your users ever seeing a client key. The key is delivered by enterprise policy or MDM, and where it arrives that way the field is pre-filled and hidden, so signing in is nothing more than entering an email address.

Why it Matters

Asking every user to paste a 36-character key into a browser extension is the kind of small friction that quietly caps a rollout. Some people mistype it, some never get round to it, and support absorbs the difference. The consequence of this means your discovery data is incomplete for reasons that have nothing to do with the product.

Delivering the key by policy removes that step entirely. The extension arrives configured, and the user does the one thing only they can do, identify themselves.

How the Key Is Delivered

What Your Users See

• With a policy-supplied key: the client key field is pre-filled and hidden. The user enters their email address only, receives a code, and signs in.

• Without a policy: the client key field is visible and required, the user is guided to manual entry with an auto-formatting UUID template, which reduces most user transcription errors.

Good to Know

• The companion app displays the full client key. Treat it as sensitive: it identifies your tenant. Share it only with Certero support, and never record it in a ticket, screenshot or defect log in full.

• If the client key field is visible when you expected it to be hidden, the policy has not reached that device. That is a deployment question, not an extension fault.

• Policy delivery does not change who can sign in, it changes only how the tenant is identified. Users still authenticate with their own email address and a one-time code.

© 2026 Certero Company Confidential. All rights reserved.