Torq takes visibility and tracking very seriously. It is important to track the actions taken by both human and AI analysts, so Torq audits all actions analysts and Socrates take.
Socrates in Your Log
Socrates is always audited in Torq's audit log, including in the following scenarios:
Workflows that Socrates executed
Updates to cases are marked as done by Socrates when relevant
Ex: Socrates changes the severity of a Case, Socrates adds a tag to a Case, etc.
Analyst Actions and Socrates
In the audit log, under
extra data, the user who asked Socrates to take a certain action is visible underrequesting_actor. This allows visibility into which analyst or user asked Socrates to act and ensures the ability to follow up with the user. For example:
{
"id": "xxxxx-xxxxxx-xxxxxxx",
"timestamp": "2024-08-14T09:10:36.854112Z",
"email": "socrates@torq.io",
"actor_name": "Socrates",
"action": "Cases linked",
"resource_id": "144001",
"extra_data": {
"linked_case_id": 143696,
"requesting_actor": "{\"kind\":\"USER\", \"user\":{\"email\":\"employee@torq.io\"}}"
},
"account_id": "xxxxxxx-xxxxx-xxx-xxxx-xxxxxxxx",
"account_name": "employee-dev"
}
Cases Audit Entries
Socrates' actions are logged in every Case instance included in the Audit Log. If Socrates completes any of these actions, they will be logged with Socrates as the actor_name.
Socrates and Conversation History
Conversation history with Socrates is saved in the case where it occurs and visible to everyone with Case view access. This ensures that all instructions to Socrates are reviewable, and conversations can be understood—and joined (by those with Case write access)—no matter which analyst began them.
