Using configuration groups to manage access to Gemini for Workspace

[SG-]

We're planning to pilot Gemini for Workspace to our Enterprise Plus org. By default the features have been disabled. I was planning on using a configuration group to manage Gemini access to the 50 pilot users.

I've followed the directions outlined in the Manage access to Gemini features in Workspace services article, but the Gemini for Workspace features are slow to rollout to those in the configuration group. A few users have gotten it, but others haven't yet.

When I test deploying Gemini for Workspace through a test OU, the accounts have access to the features in minutes.

We will enable Gemini for Workspace to our primary OU once the pilot is over, but for now I'd like to use the configuration group  to manage access.

Anyone else run into the same issue?

[icrew]

How slow is “slow to roll out”? In my experience, it can take 24, even 48, hours after a person has a feature enabled for it to show up for them, though it’s often much faster than that. This isn’t Gemini-specific—this is for any feature enablement in the admin console.