Skip to main content
All CollectionsIntegrationsBrowser Extensions
Automatically Install the Marker.io Browser Extension on Chrome OS Devices
Automatically Install the Marker.io Browser Extension on Chrome OS Devices

Auto-Install Marker.io Extension on Chrome OS

Joe Scanlon avatar
Written by Joe Scanlon
Updated over a month ago

This guide provides a step-by-step approach to automatically installing the Marker.io browser extension on Chrome OS devices using your Google Admin console. By following these instructions, you can ensure that the Marker.io extension is readily available for your team to report issues and track bugs on websites.

Step 1: Preparing for Installation

Understand Chrome Policy Management

Before you start, it's essential to familiarize yourself with managing Chrome policies within the Google Admin console. This knowledge is crucial for force-installing the Marker.io extension on your organization's Chrome OS devices.

Organize User Accounts or Browsers

To apply specific settings, organize your user accounts or browsers into a group or organizational unit. Note that only user accounts can be added to groups. For more detailed instructions, refer to Google's guide on Groups and Organizational Units.

Step 2: Force Installing the Marker.io Extension

Access the Google Admin Console

  1. Log in to Google Admin Console: Go to your Google Admin console.

  2. Choose App Type: Select whether you want to install the Marker.io extension for 'Users & browsers' or 'Managed guest sessions.'

Select Target Users or Browsers

  1. Choose Organizational Unit or Group: Select the group or organizational unit where you want to auto-install the Marker.io extension.

Find and Install Marker.io

  1. Search for Marker.io: In the Chrome Web Store section, search for the Marker.io extension.

  2. Set Installation Policy:

    • Choose 'Force install' to automatically install the extension.

    • Optionally, select 'Force install + pin to ChromeOS taskbar' to make the extension easily accessible.

Save Your Settings

  1. Click Save: After configuring the settings, click 'Save.'

  2. Manage Inheritance Options: If you're setting up for a specific unit or group, you may need to choose between 'Inherit,' 'Override,' or 'Unset' depending on your requirements.

Step 3: Verifying the Installation

Check Policies on a Managed Device

  1. Open Policy Page: On a managed Chrome OS device, go to chrome://policy.

  2. Reload Policies: Click 'Reload policies' and check the box for 'Show policies with no value set.'

Verify the ExtensionSettings Policy

  1. Confirm Policy Status: Ensure that the status for the ExtensionSettings policy is marked as 'OK.'

  2. Review JSON Code: Check the 'Value' field for any errors in the JSON code.

Step 4: Customizing the Extension (Optional)

Customize Name and Icon

For devices running ChromeOS version 100 or later:

  1. Go to Admin Console: In the Google Admin console, find the Marker.io app under the apps section.

  2. Customize Appearance: Select 'Customize name and icon' under 'Appearance' to modify the app's display name and icon.

Additional Considerations

Permissions

Be aware that force-installing the Marker.io extension grants it certain permissions on the device. Review these permissions to ensure they align with your organization's security policies.

App ID Consistency

The app ID used for force-installing the extension will remain consistent. However, note that the app icon and name might change if the publisher updates them.

Manual Installation Option

For smaller teams or individual installations, users can manually install the Marker.io extension from the Chrome Web Store. Simply follow the on-screen instructions provided after clicking the installation link.

Conclusion

By following these steps, you can deploy the Marker.io browser extension across your organization's Chrome OS devices, making it easier for your team to track and report issues.

For more information or troubleshooting assistance, refer to the Google Admin Console Help or the Marker.io Browser Extension article.

Did this answer your question?