Frequently asked questions

No. An AI Employee can answer from approved knowledge without using an Agent. Agents become useful when a focused task or connected system is involved.

Yes. For example, an Email Agent may support HR, Sales and Operations AI Employees while using the permissions defined by the organization.

No. An AI Employee is the digital coworker people interact with. An Agent is a specialized capability that can support that AI Employee.

Yes, where the organization allows it. Direct access is useful for focused tasks, while AI Employees provide a broader and more contextual experience.

Yes. Each AI Employee can be connected to the Knowledge appropriate for its role and audience.

No. Availability depends on the Workspace, assignments and permissions defined by the organization.

Yes. Documents and other supported knowledge sources can be organized within the Collection that best represents their purpose.

Yes. A Collection can be made available wherever the organization needs that shared knowledge.

No. They make the content easier to use within the platform while the organization continues to manage its source material according to its own processes.

Yes. Documents follow the Knowledge, Workspace and permission structure defined by the organization.

No. Organizations choose which supported sources and permissions are made available.

No. A Connector provides a link to a source or service. An Agent provides a specialized capability and may use a Connector when needed.

No. A Workspace is the broader environment. It may contain multiple teams with different responsibilities and access.

Yes. Multiple Workspaces can support different divisions, regions, customers or operating models.

No. An Agent performs a specialized task. A Workflow coordinates multiple tasks and participants across a broader process.

Yes. Human review, approval and decision points are important parts of many business processes.