> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.2-and-lablink-v2.4/lablink-v2.4-guide/resource-materials-and-contact-us.md).

# Resource Materials & Contact Us

The Resource Materials tab provides LabLink users with resource materials from the lab. The lab can upload different types of resources from the Configuration tab. There are two types of resource materials:

* Sample Submission Templates—Templates that can be used to submit samples. Each template contains headers and custom fields that are required for each sample.
* Supplementary Materials—Documents that can be used as part of the sample submission process.

The Contact Us tab provides LabLink users with information on how to contact the lab. The lab can update this information through the Configuration tab.


---

# 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.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.2-and-lablink-v2.4/lablink-v2.4-guide/resource-materials-and-contact-us.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.