# Service Desk Administration

Service desk templates are pre-designed formats that streamline and standardize the service request process. They serve two purposes: generating Service Requests and outlining the request format. They're divided into System and Custom templates.

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

Author license users can use System templates, which are predefined templates built into the service desk. They are designed to address common or standard service requests and are default options for handling various requests. System templates come preconfigured with standard fields and workflows, helping streamline the process by providing a ready-to-use solution for common scenarios.

## Add Details for External Integrations

An integration connects the service requests with other applications or tools. It enables smooth communication and data exchange between systems, improving the service desk's functionality and efficiency.

### External Integrations

External Integration details can be added/edited on the Service Desk Templates page through the Integrations option at the top right corner. Three external integrations are supported: JIRA, Service Now, and Azure DevOps. If no integration information is available, the selected Integration is indicated as "No Integration Information." Click on the integration button at the top right corner of the Service Desk Templates page, and in the new window, click the plus icon to add a new integration.

### Add/Edit JIRA

To add a JIRA integration tool, include the following details:

1. Integration Name
2. Connector Description
3. JIRA Server
4. User Name
5. Authentication Type (Basic / Bearer)
6. Version (Cloud / On-Premise> 8.4)

Everything except the JIRA server field can be changed when editing the JIRA integration.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcKnF_scqrKDstAiGCwf4R32sD5h4eV7PX-AXhRx0QBgkLWemf93X8zpptqF-L1V-WTrw_YrTpdF2JY3d7rf41fIHxXWzFSBgVI2LGxdgsS_D-gC4fai5KF3Bkcu_oL1TXdGgL0?key=6qINK2Swwz4qFAlWMh6DaQ" alt=""><figcaption></figcaption></figure>

#### Security Changes

To integrate JIRA with OvalEdge, the user linked to the API token must at least have Create Issues or Browse Projects permissions. These permissions allow the user to create issues and perform other actions through the API.

### Add/Edit ServiceNow

To add a Service Now integration, include the following details,

* Integration Name
* Connector Description
* ServiceNow Server
* User Name
* ServiceNow token
* Authentication Type (Basic / Bearer / OAuth)

Everything except the ServiceNow server field can be changed when editing the ServiceNow integration.

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

### Add/Edit Azure DevOps

To add an Azure DevOps integration, input the following details:

* Organisation
* Integration Name
* Connector Description
* Host Name
* User Name
* Token
* Authentication Type (Basic / Bearer)
* API version (7.0 / 7.0 preview / 6.0 / 6.0 preview / 7.1 preview)

Everything except the Host Name and Organization fields can be changed when editing the Azure DevOps integration.

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