> 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/organization-and-workflows/collaboration/comment-links.md).

# Comment links

Comment links open the exact discussion in the timeline.

Use them when you want to share one decision or question without sending someone through the full recording.

### Copy a comment link

{% stepper %}
{% step %}

#### Hover the comment

Move over the comment you want to share.
{% endstep %}

{% step %}

#### Copy the link

Select the link button on the comment.
{% endstep %}

{% step %}

#### Share it

Send the copied URL in chat, email, or a ticket.
{% endstep %}
{% endstepper %}

### What happens when someone opens it

Screendesk opens the recording and highlights that comment in the activity timeline.

The link does not bypass recording permissions. The recipient still needs access to the recording.

### Common uses

* Share a decision in Slack.
* Reference a question in a bug ticket.
* Send a reviewer to the right thread.


---

# 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.screendesk.io/organization-and-workflows/collaboration/comment-links.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.