Not able to add group in "Automatic AI access"

[Fabiano Damasceno]

Hi, I'm trying to add a new group to control access to Rovo AI in the beta feature "Automatic AI Access," but I'm receiving the following error: "We’re unable to grant AI access."

Upon reviewing the browser network request, the payload response was:
{
"timestamp": "2025-10-29T15:00:32.529+00:00",
"path": "/api/admin/v2/orgs/<org id>/directories/74aebf15-[...]/groups/3723a594-[...]/role-assignments/ai-access/assign",
"status": 404,
"error": "Not Found",
"requestId": "e56d9a84-4244401",
"message": "Request failed to match any route"
}

Anyone else with the same issue?

[Dr Valeri Colon _Connect Centric_]

@Fabiano Damasceno  Yes, that’s a known hiccup with the beta. The 404 usually means the group isn’t coming through the directory service Rovo expects, so the access call can’t resolve the route. It’s not a config mistake on your side. I’d try syncing the directory, then re-adding the group. If it still fails, share the request ID with Atlassian—they’re tracking this one.

[Rebekka Heilmann _viadee_]

Hi  @Fabiano Damasceno 

I don't know of that group and the ability to give access to only one group.

These days, Rovo can be activated on Sandbox and Production seperately for each App, but for all Users at once. The only thing you can control is who can create Agents.
With Rovo Rollout hitting it's last stage, you should get it rolled out on Prod quite soon.