Jump to content

Become a Chrome Enterprise Trusted Tester

The Chrome Enterprise Trusted Tester program is a great way for Chrome customers to test new Chrome features in their own environment and provide feedback directly to our Product teams. This feedback loop is essential and helps us continue to develop and prioritize new features. If you’d like for your organization to be included, please complete this form, and we’ll follow up with more details.

We look forward to working with you.

Step /9

Sign up to become a Trusted Tester1

Required*

Please enter your first name

Please enter your last name

Please enter your company name

Please make a selection

Please make a selection

Please select a country.

Step /9

If you have existing domain(s) with Google Workspace or Chrome, please list here:

Step /9

Which platforms have you deployed Chrome on?

This is required

Step /9

Would you like to be added to our General Trusted Tester (beta) Program2?

Step /9

Would you like to be added to our Specific Opt-In Trusted Tester (beta) Program3?

Step /9

Please advise if this is a production domain or non-production domain.

Step /9

Please enter the domain the beta(s) should run on:

Step /9

Does your enterprise use Chrome browser today?

Step /9

This is required.

This is required.

By submitting this form, I agree to share my personal information with Google and acknowledge the information I provide will be subject to Google’s Privacy Policy.

1 Please provide the information for the main point of contact regarding the Trusted Tester (feature testing) Program. This person may be asked to provide feedback throughout the Trusted Tester Program. Thus, the person that fills out the form should be the person testing out the features directly.

2 General Trusted Tester (beta) Program: A program for customers who want to be automatically enabled to any feature that is released to the Google Admin Console that requires minimum (if any) configuration.

3 Specific Opt-In Trusted Tester (beta) Program: A program for customers that is feature specific. Features with prerequisites or involve complex configurations. For these betas, participants have to request to participate after we have shared the requirements and overall plan.