Skip to main content

​
Agent Access Control

The agent’s creator and organization administrators can restrict which users and groups can see and interact with specific agents. This ensures that sensitive or specialized agents are only available to the right people.

​
Who can manage access

  • Agent creator and organization admins — set visibility and pick the allowed users and groups, on the create form and on the edit page
  • Anyone else with access — can chat with the agent but cannot change who else has access
  • Viewers — read-only: can chat with agents shared with them, cannot change any settings
A member who creates a private agent shares it directly with the colleagues or groups who need it — no admin involvement is required.

​
Visibility settings

Each agent has a visibility configuration:
  • All users (default) — Everyone in the organization can see and chat with the agent
  • Specific groups — Only members of selected groups can access the agent
  • Specific users — Only individually selected users can access the agent

​
Setting access restrictions

  1. Navigate to Agents and edit the agent you want to restrict (you must be its creator or an admin)
  2. Scroll to the Access Control section
  3. Choose the visibility mode:
    • Select Groups and choose the groups that should have access
    • Select Users and pick individual users
  4. Click Save
Users who don’t have access will not see the agent in their agent picker and cannot start conversations with it.

​
How group-based access works

When an agent is restricted to specific groups:
  • A user must be a member of at least one of the allowed groups to access the agent
  • If the user is in multiple groups, they only need one to match
  • Administrators always have visibility into all agents regardless of group restrictions

​
Enterprise: Azure AD groups

In enterprise deployments, groups are synced from Azure AD. You can use your existing AD group structure to control agent access without creating separate groups in Neural Factory. For example:
  • Restrict the “HR Assistant” agent to the “HR Department” AD group
  • Restrict the “Engineering Docs” agent to the “Engineering” AD group

​
Best practices

  • Start with all users visibility while testing a new agent, then restrict once it’s ready
  • Use groups rather than individual users for easier maintenance
  • Document which agents are available to which groups for your team’s reference