> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/interview-studies/conduct-an-interview-session/share-an-interview-session-link.md).
# Share an interview session link
If an observer, participant, or guest loses track of the link needed to join an interview session, you can manually retrieve it from the **Manage** tab of your study. Then, you can share the URL directly to ensure anyone who needs to join is able to.
{% hint style="info" %}
If you're already in a session waiting for someone to join, quickly copy the link to your clipboard by clicking the **link (chain)** icon in the top left corner beside the participant's name.
{% endhint %}
**To manually share an interview session link:**
{% stepper %}
{% step %}
Navigate to the **Manage** tab of your study. A list of scheduled sessions is displayed.
{% endstep %}
{% step %}
Find the session you need to share a link to.
{% endstep %}
{% step %}
Click the **link** icon.
{% endstep %}
{% step %}
Select the link you need (observer, participant, or guest).
{% endstep %}
{% endstepper %}
Now, the session link is copied to your clipboard and you can share it however works best for you—whether that’s via message in Dscout, email, or another means of communication.
{% hint style="info" %}
If you're sharing a link with a participant, sending it via message in Dscout is typically the fastest option as they'll also receive your message via email. For more information, see [Communicating with participants](/recruit-participants/working-with-participants/communicating-with-participants.md).
{% endhint %}
For information on user roles and permissions during interview sessions, see [User roles in interview sessions](/interview-studies/what-are-interview-studies-in-dscout/user-roles-in-interview-sessions.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://help.dscout.com/interview-studies/conduct-an-interview-session/share-an-interview-session-link.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.
.jpg?alt=media&token=0f66aa8a-6c8f-47b7-bc8a-a362335a7853)