> 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.1/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.
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 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.1/administration/security/workflow.md?ask=&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.
