Summary
When changing an agent’s visibility from Public/Private to Group Restricted, the system throws an allowed_groups error. However, the UI does not provide any field to configure allowed_groups, making it impossible to complete the action.
Environment
- Project: Agent Registry (Open Source)
- Deployment: Enterprise setup
- Auth/Identity Provider: Microsoft Entra ID (groups-based access control)
Steps to Reproduce
- Create or edit an existing agent.
- Set visibility to Group Restricted.
- Attempt to save/update the agent.
Actual Behavior
- The operation fails with an error indicating that
allowed_groups is missing or invalid.
- No UI field is available to input or select
allowed_groups.
Expected Behavior
Impact
- 🚫 Blocking issue: Cannot create or update group-restricted agents.
- Prevents enforcing group-based access control for agents.
- Limits usability in enterprise environments where access must be scoped to specific user groups.

Summary
When changing an agent’s visibility from Public/Private to Group Restricted, the system throws an
allowed_groupserror. However, the UI does not provide any field to configureallowed_groups, making it impossible to complete the action.Environment
Steps to Reproduce
Actual Behavior
allowed_groupsis missing or invalid.allowed_groups.Expected Behavior
When Group Restricted visibility is selected:
The UI should display a field to configure
allowed_groups.This could be:
The agent should be saved successfully when valid groups are provided.
Impact