> 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.2/administration/security/workflow.md).

# Workflow

The "Workflow Security" streamlines the process of approving service requests, ensuring proper oversight and governance. Service requests are automatically routed to designated approvers based on predefined rules. Administrators, including OE\_ADMIN and Users with "ovaledge.role.admin" roles, can create custom workflows applicable to specific requests and object types, allowing them to have granular control over the approval process. Approvers can be defined as individuals, teams, or roles, providing flexibility in assigning approval responsibilities. It is possible to establish approvers at global (for all requests) and service desk template-specific levels. OvalEdge also provides a set of system-defined workflows based on service desk templates that are readily available. Custom workflows created by administrators can be deleted, but system workflows are permanent.

<figure><img src="/files/TXuAfz0ShApCd4CMB2zA" alt=""><figcaption></figcaption></figure>

The OE\_ADMIN can perform the following additional actions.

* Create custom approval workflows for service requests.
* Define approvers (individuals, teams, or roles) and set Service Level Agreements (SLAs) for approvals.
* Delete custom workflows (system workflows are pre-defined and non-deletable).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/administration/security/workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
