> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/resource-and-metadata-management/relating-resources.md).

# Related resources

This section will go over how to relate resources.

Secoda is a powerful knowledge management platform that allows users to organize and access their resources in a centralized location. One key feature of Secoda is the ability to link resources to each other using the "Related Resources" function.

The Related Resources function in Secoda is a powerful tool for building knowledge networks. By linking resources together and creating relationships between them, you can create a web of interconnected knowledge that allows you to explore different topics and ideas in a more holistic way.

## How are related resources created?

#### Automatically

* Secoda identifies resources within the same lineage graph and tags them as "Related"
* If another asset is referenced by using the @ tagging feature, Secoda automatically establishes a link between the two resources, indicating their relationship as "Related."

#### Manually

* Users can manually add Related resources by clicking into a resources and editing the metadata

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/2c8bb790-252d-45dc-bdd3-1472031ee99c.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: For resources within the catalog section, the related property is shown as a tab on the resource page
{% endhint %}

Overall, the Related Resources function in Secoda is a powerful feature that allows you to link resources together and create relationships between them. By using this feature, you can build knowledge networks and explore different topics and ideas in a more comprehensive way.


---

# 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.secoda.co/resource-and-metadata-management/relating-resources.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.