# metadata-only access, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** A way of connecting a lineage tool to a warehouse so it reads schemas, query logs and usage but not table contents. It lowers risk because row data never leaves the warehouse. Vendors describe it differently, so read the setup grants. Secoda's security policy says it needs only READ permissions on databases and API cloud applications.

## Definition

A way of connecting a lineage tool to a warehouse so it reads schemas, query logs and usage but not table contents. It lowers risk because row data never leaves the warehouse. Vendors describe it differently, so read the setup grants.

## Example from a real tool

**Example.** Secoda's security policy says it needs only READ permissions on databases and API cloud applications.

## Related terms

- [stitching (cross-system lineage)](/glossary/stitching-cross-system-lineage/): Joining lineage collected from separate systems into one connected graph, for example warehouse queries, a dbt project and a BI tool.
- [lineage freshness](/glossary/lineage-freshness/): How soon the lineage graph reflects a change in the real pipeline.
- [persona-scoped context](/glossary/persona-scoped-context/): Context for an agent that is filtered by the role of the person asking.

## Where to read more

- [The Lineage Depth Matrix](/matrix/)
- [All glossary terms](/glossary/)

## Sources

- docs.secoda.co/policies/security-policy.md: https://docs.secoda.co/policies/security-policy.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/glossary/metadata-only-access/
