How can we help?

Polyosync provides different forms of operational visibility to help organizations understand activity, investigate execution results, and evaluate business performance. Enterprise audit logs, Action History, and business reports serve related but distinct purposes. Understanding these differences helps administrators use the appropriate information for each task. Enterprise audit logs Audit logs focus on recorded activity relevant to accountability, administration, security, or governance. They help answer questions such as: 1. What relevant event was recorded? 2. When did it occur? 3. Which actor or operational context was associated with it, where recorded? 4. What resource or operation was affected? 5. What outcome was recorded? The precise event coverage depends on the available audit implementation. Action History and execution records Action History and module-specific execution histories focus on operational activity. These records can help explain what happened when an automation, autonomous workflow, AI collaboration, or business process executed. Depending on the module and available details, execution information may include: 1. Execution status. 2. Start or completion time. 3. Relevant inputs. 4. Execution steps or events. 5. Results. 6. Error information. 7. Other technical execution details. The available fields differ between modules. Business reports Business reports focus on performance and outcomes rather than individual technical events. Reports can help organizations evaluate trends and understand how operational activities contribute to business objectives. The available reporting capabilities and metrics depend on the implemented functionality and available data. Example: Investigating a failed workflow An administrator wants to understand why a business process failed. Execution history is the appropriate starting point because it may show the failed step and error information. Audit information may provide additional context if a relevant configuration or access event occurred. A business report may help determine whether repeated failures are affecting broader operational performance. Example: Reviewing an unexpected administrative change An administrator notices that a configuration is different from the expected state. Relevant audit records may help investigate recorded changes. The current workspace settings can be reviewed to determine the active configuration. If the change affected running operations, execution history may provide additional evidence. Example: Evaluating AI workforce effectiveness An organization wants to understand whether its AI operations are producing useful business outcomes. Business reports and operational results are more relevant than raw audit events. Audit logs should not be treated as a substitute for performance analytics. Can these sources contain overlapping information? Yes. A business activity may produce information in more than one operational record. However, the presence of an event in one source does not guarantee that an equivalent record exists in every other source. Are all three sources available in every Enterprise configuration? The exact interfaces and information available depend on the enabled platform functionality and Enterprise configuration. Recommended approach Use audit logs for accountability, execution history for operational investigation, and reports for performance evaluation. Together, these sources can provide a more complete understanding of Enterprise activity.