The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability. Environment:MDM = Omnissa Workspace One UEM (we are also hearing reports of this impacting SOTI customers as well)Rugged Zebra Mobile devices, majority running either A11 or A13Leads:Managed App configs are still present on Chrome & ServiceNow Now Agent, hence why we believe this is not an MDM Console issue. We have escalated to Omnissa support anyway, who have in turn escalated to Google.Is anyone else seeing this issue?

Level 1.6: Donut

Solved

Managed configuration to Gboard has disappeared from MDM

Forum|Forum|11 months ago
May 8, 2025
12 replies
117 views

The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability.

Environment:

MDM = Omnissa Workspace One UEM (we are also hearing reports of this impacting SOTI customers as well)
Rugged Zebra Mobile devices, majority running either A11 or A13

Leads:
Managed App configs are still present on Chrome & ServiceNow Now Agent, hence why we believe this is not an MDM Console issue.

We have escalated to Omnissa support anyway, who have in turn escalated to Google.

Is anyone else seeing this issue?

Best answer by Lizzie

Hey @badams1, @AndroidE, @mattdermody, @Stefano, @Magcho, @Alex_Muc, @Moombas, @jeremy, @Flaviano, @Sulander, @Kraeutergarten,

I think we have lift off! 😀 🤞🚀

A fix has just been pushed for this, it could take a few hours to start coming through on your side, I wondered if you could validate and let me know if you see any change please?

Massive thank you for all the feedback you've given this has been really helpful. Looking forward to hearing from you.

Thanks,

Lizzie

[Will mark this as an 'Accepted solution' to highlight this at the top of the topic - but this is still pending validation - please still reply below - thank you]

Show previous replies

Lizzie

Community Manager

Hey everyone,

Our engineering team are still investigating this and are working on a potential resolution. I'm waiting and pushing for more updates and will update you all as soon as I have more details.

Please do continue to share if you are experiencing this, it is useful to share back with the team.

Massive thanks and hope to speak soon.

Lizzie

Welcome to the Community everyone!

Lizzie

Answer

Community Manager

Hey @badams1, @AndroidE, @mattdermody, @Stefano, @Magcho, @Alex_Muc, @Moombas, @jeremy, @Flaviano, @Sulander, @Kraeutergarten,

I think we have lift off! 😀 🤞🚀

A fix has just been pushed for this, it could take a few hours to start coming through on your side, I wondered if you could validate and let me know if you see any change please?

Massive thank you for all the feedback you've given this has been really helpful. Looking forward to hearing from you.

Thanks,

Lizzie

[Will mark this as an 'Accepted solution' to highlight this at the top of the topic - but this is still pending validation - please still reply below - thank you]

Welcome to the Community everyone!