Google Workspace not configured. How do I set it up and what credentials are used for direct enrollment?Solved

Participant
Discussion
1 day ago Jun 10, 2026

I’m setting up Hexnode with Google Workspace and I’m stuck at the “not configured” part. I saw that I need to do something in Google Admin, but I’m not sure what exactly has to be configured. Also, if I skip Google Workspace for now and try to enroll a device directly with a Hexnode account, what username and password should be used? Is it the same username and password used to log in to the Hexnode UEM portal as an admin?

Replies (2)

Marked SolutionPending Review
Hexnode Expert
1 day ago Jun 10, 2026
Marked SolutionPending Review

Hi @_ashur.

For Google Workspace integration, Hexnode needs permission from Google before users and groups can be synced into the Hexnode portal.

The usual setup flow is:

  1. In Google Cloud Console:
    • Create a service account.
    • Enable the Admin SDK API.
    • Generate and download the JSON key file for the service account.
  2. In Google Admin Console:
    • Go to Security > Access and data control > API controls.
    • Configure domain-wide delegation.
    • Authorize Hexnode using the required client ID and scopes.
  3. In the Hexnode portal:
    • Go to Admin > Google Workspace.
    • Upload the JSON key file.
    • Complete the integration.

Once this is done, Google Workspace users and groups can be synced to Hexnode.

For device enrollment, you cannot use the Hexnode portal administrator username and password to authenticate a device. Instead, create a local user in Hexnode UEM or use a synced directory user once the Google Workspace integration is complete.

Best Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
1 day ago Jun 10, 2026
Marked SolutionPending Review

One thing to watch out for on Android devices: during setup, battery optimization can interfere with the Hexnode app running properly in the background. If the device prompts you to disable battery optimization for Hexnode, do it directly from the device settings. After disabling it, the rest of the configuration should continue normally.

Save