> 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/add-documentation.md).

# Editing properties

After you've connected your data to Secoda, you can start adding documentation and metadata to your data to enrich it for your users.

## **Why enrich your data?**

* **Clearer insights:** Makes data easier to understand and trust, so everyone can make better decisions.
* **Streamlined governance:** Defines clear responsibilities, ensuring data is used correctly.
* **Boosted collaboration:** Helps teams easily share and utilize data.
* **Stronger security:** Protects sensitive information and controls who can access it.

## How to add context to your data

Secoda integrates with your data sources to automatically bring in existing descriptions for tables, dashboards, and columns. For instance, if you connect your dbt YAML files, Secoda will sync the descriptions directly to the corresponding columns and tables.

### Automating documentation

Automatically add property documentation by leveraging some best practices within Secoda:[Documentation best practices](/best-practices/documentation-best-practices.md).

### Manually add enrichment

1. **Locate your data**: Use the Search feature or navigate directly through the Catalog to find the dataset you want to enrich.
2. **Edit descriptions**: On the dataset overview page, click under the dataset's name to add or update its description.
3. **Enhance documentation**: Navigate to the Documentation tab to add detailed documentation, guides, or any supplementary material.

#### Further enrichment options:

* **Tagging**: Apply [tags](/resource-and-metadata-management/tags.md) like PII, Verified, or custom tags to categorize and mark the status of data assets.
* **Relate resources**: Create [links](/resource-and-metadata-management/relating-resources.md) between different datasets to establish and visualize relationships.
* **Assign ownership**: Define [ownership](/resource-and-metadata-management/assigning-owners.md) for datasets to clarify responsibilities and direct queries.


---

# 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/add-documentation.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.