> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/data-and-assets/data.md).

# Assets overview

Reusable data connections, constants, secrets and functions, shared across notebooks.

**Assets** are reusable items your organization keeps in one place and uses across many notebooks. Instead of pasting the same database password or helper code into every notebook, you create it once as an asset and attach it wherever it's needed.

| Asset                                                                             | What it's for                                                                             | Versioned?                   |
| --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------------------- |
| [**Data connections**](/zerve-docs/data-and-assets/connections.md)                | Credentials for databases and data platforms, such as Snowflake, Databricks or PostgreSQL | No                           |
| [**Constants and secrets**](/zerve-docs/data-and-assets/constants-and-secrets.md) | Named values, such as API keys, configuration or thresholds                               | Yes                          |
| [**Functions**](/zerve-docs/data-and-assets/functions.md)                         | Reusable code, shared across notebooks                                                    | Yes                          |
| [**DAGs**](/zerve-docs/data-and-assets/dags.md)                                   | Pipelines of connected blocks, reused across projects                                     | No: each DAG is a saved copy |

Find your organization's assets under **Assets** in the Workspace sidebar.

## Attaching assets to notebooks

An asset becomes available to a notebook when you **attach** it. In a project, assets are called **resources**: open the **Resources** sidebar with **Ctrl+5** (Windows) or **⌘+5** (Mac), and select **Add Resource to Project**. You can attach one asset to many notebooks, and give it an **alias** in a particular notebook if you'd like to refer to it by a different name there.

For constants and functions, a notebook attaches a **specific version**. Updating the asset doesn't change notebooks that use an older version until you switch them, so you can roll out changes one notebook at a time.

## Assets and agents

Zerve's agents use the assets attached to the notebook they're working in, and superagent planners look at your organization's connections and constants when drafting a plan. Setting up assets first gives agents what they need from the start. See [Giving the agent context](/zerve-docs/agents-in-the-workspace/giving-the-agent-context.md).

## Who can use assets

Assets follow the same sharing rules as everything else in Zerve: each has an owner, and people need access to view, edit or attach it. See [Sharing and privacy](/zerve-docs/administration/sharing-and-privacy.md).

**Assets can't be used outside their organization.** You can't attach an asset from one organization to a notebook in another.

## How values are protected

Every constant and secret value is stored in a secure vault, and connection credentials are never shown back to users. See [Security overview](/zerve-docs/security/security.md#credentials-are-stored-in-a-vault).


---

# 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.zerve.ai/zerve-docs/data-and-assets/data.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.