> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/helpdesk-integrations/jira-service-management/customer-portal.md).

# Customer portal

Add a Record your screen button to your Jira Service Management customer portal, so customers can attach a recording when they raise a request.

Add a **Record your screen** button to the request forms of your Jira Service Management customer portal, so customers can show the issue when they raise a request.

{% embed url="<https://app.screendesk.io/recordings/15511cd2-8c11-4b8a-aead-18f799ea45e1>" %}

1. In Screendesk, go to **Settings → Integrations** and click **Configure** on the Jira Service Management card.
2. Under **Let customers record on their own**, turn on **Record on the customer portal**.
3. Under **When a recording arrives**, check that **Add portal recordings to the request** is on.

On your portal's request forms, customers now see **Show us on your screen** with a **Record your screen** button. Jira asks before it opens Screendesk (**Continue**), and the recorder opens in a new tab. Meanwhile the form says **Finish recording in the new tab, then send your request here.**, with **Record again** to start over. When they've recorded, they go back to the form and send the request.

The recording is added to the new request as a comment, as set under **Comment** in Screendesk. As an **Internal note**, only your agents see it: the customer doesn't see it on the portal.

The button needs the Screendesk app installed and connected to your workspace. See [Install and set up](https://docs.screendesk.io/helpdesk-integrations/jira-service-management/install-and-set-up.md).


---

# 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.screendesk.io/helpdesk-integrations/jira-service-management/customer-portal.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.
