Before you get started using Gopher for Chrome there are a few Admin console settings you'll need to address; enabling API Access, adding Gopher for Chrome to trusted sites, and enabling a local cache.
Amplified Labs uses Google's APIs to gather information about your Google resources. For Gopher for Chrome to work, you will need to mark restricted apps as trusted. This is found in Manage Google Services of the Admin Console under Security > API controls.
Next, you need to add Gopher Buddy and/or Gopher for Chrome to the trusted apps using the Manage Third-Party App Access setting. This is found in the App access control of the Admin Console under Security > API controls.
Some of Amplified Labs tools utilize Google Drive to store a local cache file. To use this file, you need to permit addons to use the Drive API. The setting for this can be found under Apps > Google Workspace > Drive and Docs > Features and Applications under the setting Drive SDK.
Gopher for Chrome utilizes the Admin console's data to report Chromebook metadata to the Administrator in a readable format. The Most Recent User metadata field is updated in the Admin console on the Logout event on the Chromebook.
The Logout event is also tied to the device setting to erase local user data. As a result, when this setting is configured to erase user data, the Most Recent user data is empty. The setting for this can be found under Devices > Chrome > Settings > Device Settings > Sign-in settings. We recommend setting the User Data setting to Do not erase all local user data if administrators want to have a list of recently logged-in users.