Agent capabilities & guardrails — found from sitemap — LightOn

Cited by

Facts read from this source

• Agents availability Report an error

  “Agents are available for the Wise Wolf release (February 2026) and later, if you are on Unique Urchin (December 2025) or Victorious Vicuna (January 2026), please refer to the legacy agentic threads documentation.”

• Agents description Report an error

  “Agents are the evolution of the legacy ChatSettings system, there can be several within the same company and allows you to create and use a specialized prompt as wess as set of tools, MCP servers and scoped workspaces to achieve a specific task.”

• Agents group link Report an error

  “The agents are linked to Groups which controls who can access them and which workspaces can be accessed with them.”

• Agents create endpoint Report an error

  “Create an agent using the POST /api/v3/agents endpoint.”

• Tools list endpoint Report an error

  “You can list native tools available within your company using GET /api/v3/tools and the MCP servers available within you company using GET /api/v3/mcp endpoint.”

• Default agent Report an error

  “Every company has a default agent linked to the company’s default company-wide group of which every company’s users are member of. When using the Threads API, if you don’t specify an agent_id field, the default agent will be used implicitely.”

• Ownership values Report an error

  “ownership Who can access it group_id required? "personal" The creator only No "company" All users in the organization No "team" Members of the specified team Yes”

• Ownership company admin required Report an error

  “Only Company Admin and System Admin can create agents with ownership set to "company".”

• Team ownership roles Report an error

  “For ownership: "team", the caller must be a Company Admin, a System Admin, or hold the Owner role in the target group.”

• Scoped workspace ids release Report an error

  “The ownership field and scoped_workspace_ids are available from Xenial Xerus (March 2026). On earlier versions, use group_id with scope_workspaces_by_group — refer to the legacy workspace scoping behavior below.”

• Workspace scoping default Report an error

  “By default, an agent accesses all workspaces belonging to its team. You can restrict this to a specific subset using the scoped_workspace_ids field (a list of workspace IDs) when creating or updating an agent.”

• Workspace scoping effect Report an error

  “When scoped_workspace_ids is set, the restriction applies regardless of which user calls the agent.”

• Agent scoped resources Report an error

  “workspaces: list available ones via GET /api/v3/agents/:id files: list available ones via GET /api/v3/agents/:id/files tags: list available ones via GET /api/v3/agents/:id/tags”

• Legacy scope workspaces by group Report an error

  “Use group_id to associate an agent with a team and scope_workspaces_by_group (boolean, default true) to control workspace access. When true, the agent accesses only the team’s workspaces; when false, it accesses all workspaces the requesting user has access to. scope_workspaces_by_group is still accepted in Xenial Xerus and later for backwards compatibility but is deprecated.”

Scores citing this record

• The Automation Lead Admin, identity & access controls
• The Automation Lead Integrations, connectors & knowledge
• The Automation Lead Agent capabilities & guardrails
• The Automation Lead Admin, identity & access controls
• The Automation Lead Integrations, connectors & knowledge
• The Automation Lead Agent capabilities & guardrails
• The Customer-Service Director Admin, identity & access controls
• The Customer-Service Director Integrations, connectors & knowledge
• The Customer-Service Director Agent capabilities & guardrails
• The Customer-Service Director Admin, identity & access controls
• The Customer-Service Director Integrations, connectors & knowledge
• The Customer-Service Director Agent capabilities & guardrails
• The Data Protection Officer Admin, identity & access controls
• The Data Protection Officer Integrations, connectors & knowledge
• The Data Protection Officer Agent capabilities & guardrails
• The Data Protection Officer Admin, identity & access controls
• The Data Protection Officer Integrations, connectors & knowledge
• The Data Protection Officer Agent capabilities & guardrails
• The Data Protection Officer Pricing transparency
• The Head of IT Admin, identity & access controls
• The Head of IT Integrations, connectors & knowledge
• The Head of IT Agent capabilities & guardrails
• The Head of IT Admin, identity & access controls
• The Head of IT Integrations, connectors & knowledge
• The Head of IT Agent capabilities & guardrails
• The Skeptic Admin, identity & access controls
• The Skeptic Integrations, connectors & knowledge
• The Skeptic Agent capabilities & guardrails
• The Skeptic Admin, identity & access controls
• The Skeptic Integrations, connectors & knowledge
• The Skeptic Agent capabilities & guardrails
• The Works Council Member Admin, identity & access controls
• The Works Council Member Integrations, connectors & knowledge
• The Works Council Member Agent capabilities & guardrails
• The Works Council Member Admin, identity & access controls
• The Works Council Member Integrations, connectors & knowledge
• The Works Council Member Agent capabilities & guardrails