macOS user locked out of Hexnode Access after Google Workspace suspensionSolved

Participant
Discussion
6 days ago Jul 28, 2026

During macOS onboarding, we create a local user account and then enroll the Mac with Hexnode using the user’s Google Workspace credentials. A Hexnode Access policy is applied so the device uses Google-based login.

If that Google Workspace account is temporarily suspended, can the user still sign in to the Mac with the local account that was already created? In the Hexnode portal, I can see options like Disenroll device and Change owner, but I’m not sure which one affects the actual login screen or whether it could impact local user accounts on the Mac.

Replies (3)

Marked SolutionPending Review
Hexnode Expert
6 days ago Jul 28, 2026
Marked SolutionPending Review

Hey @rob_mitch,

With Hexnode Access enabled on the Mac, the login window authenticates against the configured identity provider, such as Google Workspace. If the Google Workspace account is suspended, Google rejects the authentication request, so the user will not be able to get past the Hexnode Access login screen even if a local macOS account exists.

For immediate access, the most direct option is to disenroll the device from Hexnode. This removes the Hexnode management profile and disables the Hexnode Access policy, causing the Mac to return to the standard macOS login window. The user can then sign in with the existing local macOS credentials.

Other possible options are:

  • Temporarily unsuspend the Google Workspace account long enough for the user to sign in.
  • Use a local administrator account if an admin bypass key was already configured in the Hexnode Access policy.

Best Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
6 days ago Jul 28, 2026
Marked SolutionPending Review

So even though the user account was originally created locally on the Mac, the Google suspension still blocks login because Hexnode Access is controlling the login window, right?

Also, if I change the owner of the device to an admin account in Hexnode, will that give me more control over the Mac? Would I need to manually change it back later once the Google account is active again?

Marked SolutionPending Review
Hexnode Expert
6 days ago Jul 28, 2026
Marked SolutionPending Review

Yes @rob_mitch, the local macOS account may still exist on the device, but while the Hexnode Access policy remains active, the login flow is still controlled by Hexnode Access and Google Workspace authentication.

Changing the owner in the Hexnode portal does not change the local accounts on the Mac and does not remove the Hexnode Access login window. It is only an administrative change in the Hexnode dashboard.

If you change the owner to another user, you will need to manually change it back later. Hexnode will not automatically revert the device owner when the suspended Google Workspace account becomes active again.

Best Regards,
Isabel Lora
Hexnode UEM

Save