I’m currently attempting to draft out a proof-of-concept conversational agent, however it seems that it cannot see the context index I created, nor can any of the tools see any connections.
Both the Index and the connections are located in a shared folder for which I should have full access to.
Is there something I might be missing? Possibly a permission somewhere that needs to be set or a missing license.
We are currently operating on the Basic platform tier with a pro license assigned to my account and access level into the Tennant being Org Admin.
Double check your user and robot accounts have full read/write access to the shared folder with the context index.
Confirm your Basic tier and Pro license support conversational agents upgrade if neded then in Orchestrator refresh the context grounding index and correctly link it to your agent for full visibility and functionality.
Hi,
It sounds like you’ve already set up the basics correctly (index + connections + proper roles), so the issue is likely tied to platform tier or resource access scope, not your role.
Maybe this is what’s happening, on the Basic tier, even with a Pro license, AI-based resources like conversational agent context indexes often require Enterprise features (AI Center, Vector Indexing, or AI Unit allocation) to function. The agent can be created, but it won’t “see” the context index or the connections because those capabilities aren’t fully supported under Basic.
You can double-check a few things:
In Admin > Licenses > AI Units, confirm that at least some AI consumption units are available.
In Connections, make sure the folder and index are shared not only with you but also with the Agent Service (the system identity running the agent).
Try moving the index out of a shared folder and into your personal workspace just to rule out folder-level restrictions.
If you’re using Automation Cloud Basic, upgrading to Enterprise Trial or Enterprise plan usually enables full index visibility and agent–connection integration.
So maybe that’s the missing piece, the Basic tier doesn’t yet support full conversational agent context linkage. You could try requesting a temporary Enterprise Trial from UiPath support to validate your POC.
After confirming everything, it seems that the most probable cause here is the fact that I’m currently using an Automation Cloud Basic plan.
Looking back at an old conversation with our UiPath representative they had listed agents as a feature not available through the basic plans.
Will provide updates to this post in the future should that for some reason not come up to be the case for anyone looking to reference this at a later point in time.