Notification

Planning your return to office strategy? See how ChromeOS can help.

Zahtevana stran za zdaj ni na voljo v vašem jeziku. Na dnu strani lahko izberete drug jezik ali takoj prevedete katero koli spletno stran v jezik po izbiri z vgrajeno funkcijo prevajanja Google Chroma.

Guidelines for Chrome Enterprise Trusted Testers

Recommendations for testing new features in your organization

Thank you for your interest in testing new features in your environment. You’ll provide feedback directly to our product teams so that we can develop and prioritize new products and features. All program details and feedback are confidential.

As a Trusted Tester, when you test new features on Chrome browser, ChromeOS and ChromeOS Flex, you help us to succeed together through valuable feedback and feature requests that cover real-world scenarios and represent customer diversity.

We are committed to helping you through the process, including:

  • Clear communication that helps us to identify the right features for each customer
  • Easy onboarding guidance and support in the configuration process
  • Feedback tools and responsive interactions

Things to consider when becoming a Trusted Tester

Understand the broad requirements for being a Trusted Tester

Before you sign up, read the requirements for being in the program. For details, go to Become a Chrome Enterprise Trusted Tester.

Become familiar with the relevant agreements. Ensure that you have sufficient authorization and understand the relevant clauses in the agreements.

Understand the feature that you have signed up to test

We will provide documentation about features. It is important that you review them. We will also let you know which type of Trusted Tester that you have been allowlisted for. We have two types:

  • General—A general list which receives information on new features as they get released
  • Specific opt-in—You have signed up to test a specific product feature.

General features use a rolling enrollment approach. For specific opt-in features, your enrollment is automatically canceled when the Trusted Tester phase of that specific feature is completed.

Assign the right resources to the project

Trusted Testers within the enterprise are experienced IT administrators and managers who understand their existing infrastructure and the technologies that are to be tested. For example, ChromeOS admins should explore the certified ChromeOS administrator credential.

Guidelines for Trusted Testers

All Trusted Tester features are released behind IT admin controls to ensure that you, as the customer, have full ownership and control of the configuration and test process.

Use a Test Domain

We strongly recommend that you enroll for Trusted Tester features with a test domain. Our team will accept a subdomain of your existing domain or a separate domain that you can confirm you own.

We do not recommend that you deploy Trusted Tester features to your users without prior testing with a small group on your test domain. You can perform initial testing with a few devices on the ChromeOS Beta channel. For details, read ChromeOS release best practices.

Enroll a specific IT admin

When you sign up for our Trusted Tester, in some cases you can choose to have the admin controls for Trusted Tester features to be available and visible to all admins on your domain or to specific admins. For details about admin roles and privileges, go to Delegate administrator roles in Chrome

Where possible, we recommend that you opt for the specific admin option and provide at least 2 admins. It is important that you contact us if the specified admin needs to change—due to a role change, for example.

Provide the right contacts for communication

Our communication with Trusted Testers is carried out exclusively over email. Because of this, it is important that when enrolling for the Trusted Tester program you provide contacts that have reachable monitored email accounts.

Where possible, we recommend that the contact is the same as the IT admin, but we are aware that this is not always the case.

Optimize constantly

We recommend that you keep a close eye on user feedback and keep optimizing your deployment.

Unsubscribe when done

If your organization was signed up for our general Trusted Tester and is no longer interested in testing or has completed testing the feature that was of interest, fill this opt-out form to be removed from the allowlist. To access the form, sign in with the Google Account that you used to sign up for the Trusted Tester program.

From time to time, we will contact you to confirm if you would like your enrollment as Trusted Testers to lapse. For example, if emails are being bounced from your delivery account.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
3932993281372777809
true
Search Help Center
true
true
true
true
true
410864
false
false