Skip to main content

Metadata types

Every asset in Atlan—a table, a column, a dashboard, a dbt model—is an instance of a type. Types are the schema layer of the metadata platform: they define which attributes an object carries, what it inherits from parent types, and which other types it connects to through relationships. Whether you are writing connector output, reading asset properties in an app, or traversing lineage graphs, you always work from a type definition.

What you use types for

🔌

Build connectors

Look up required attributes before writing connector output. Every type page shows which fields are mandatory on create and what values they accept.

⚙️

Read and write metadata

Get and set typed properties on assets in your app. Check the full attribute list for a type to know which fields are available and what data types they carry.

🕸️

Traverse asset graphs

Follow relationships between types to navigate lineage, ownership, and dependencies. Each type page lists its relationship targets and their cardinality.

How to use this reference

1

Start with Asset

Most types inherit from Asset, which carries the attributes shared across all metadata objects: name, description, owners, classifications, and more.

2

Find your type

Browse the sidebar to locate the type for your asset. Use the search bar on any type page to filter across hundreds of attributes by name or description.

3

Check own and inherited properties

Review own properties first, then expand inherited groups. Switch to the Relationships tab to see how this type connects to others in the graph.

💡

Required on create: When building a connector, pay attention to required fields—they must be present in your output for the asset to ingest correctly. Each type page highlights which attributes are required.