> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/service-desk/service-desk-administration/service-desk-audit-trails.md).

# Service Desk Audit Trails

The Service Desk Templates Audit records all modifications made to service desk templates, workflows, and integrations. It captures details of additions, updates, and deletions, allowing administrators to track changes effectively.

## Service Desk Templates

The audit logs capture any modifications related to adding, editing, or deleting templates. This includes changes to the template name, description, additional settings, template fields, associated workflows, fulfillment configurations, and integration mappings. Any updates to predefined fields or structural modifications within a template are also logged to maintain a comprehensive record of adjustments.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcBBDmmznlST3Y59ZseDCPMpDzSuG1QTnUyOkIBS2WnQpbV5nABkMt8nFrTIylS3imzMSUNq_C1ACk2423vYHa-TRb4SLxLMncOjbvJf2jUG3C9Ok53hFOh77QfNiP5U-7Xz7Hd4w?key=6qINK2Swwz4qFAlWMh6DaQ" alt=""><figcaption></figcaption></figure>

## Workflows

The audit logs capture all workflow modifications, including when a workflow is added, updated, or removed. It records changes to the workflow name, scope, and description, and modifications to workflow actions, execution steps, triggers, and mapped service desk templates.&#x20;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeWknNlyx3z-eQCR8b4er4rMyiZ_Dkbrz5iTdzsukeGoqwSAZDCvJliQFpzlRb3tzkQ-gMATjO5623P8xCNykQmpwqsYa5B-PTbI5adMhD9_mmb78fPbL6wbTk6R0oGKZxsFofDmA?key=6qINK2Swwz4qFAlWMh6DaQ" alt=""><figcaption></figcaption></figure>

## Integrations

The audit logs track changes to external integrations used for managing and tracking service requests. When integration is added, updated, or deleted, the system logs details such as authentication updates, API endpoint modifications, and changes to integration settings. This allows administrators to monitor connectivity with third-party tools and maintain seamless integration with external platforms.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeXHW84Fp77TwyQIownwFQvBJw85ROPfI_DixpGTYqaLiEPjXnGfqUokXq9xXqKGR9G1T2BuY9qaTO4GLuKo0ldIigHXg_6lihYhLLIa8E_2xF8a6VBK2VneblGp-MFHFj03_t6_A?key=6qINK2Swwz4qFAlWMh6DaQ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/service-desk/service-desk-administration/service-desk-audit-trails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.