✨ Let's dig deeper

Your metadata estate is a knowledge graph: assets connected by meaningful relationships. With this release, those relationships, and the labels that describe them are first-class, queryable data in the Lakehouse, ready for analysis.

📊 Analytics on your ontology
Because relationship labels are now queryable, you can explore the shape and meaning of your estate in more creative and useful ways-

• Map your ontology - see every labeled relationship between terms ("Is a", "Derived by", "Allowed values") as queryable rows you can roll up and visualize.
• Measure coverage - find how many terms are connected versus orphaned, and where your ontology has gaps.
• Trace semantic lineage - follow "Derived by" and "Is a" chains to understand how concepts build on one another.
• Audit consistency - spot duplicate or inconsistent relationship labels and keep your ontology clean.
• Enrich AI & discovery - feed labeled relationships into the context that powers smarter search and conversational experiences.
• Combine and report - blend relationships with the rest of your Lakehouse metadata for richer, estate-wide reporting.

🌍 Where does this work?

• ✅ User-defined relationships used in the business graph
• This is a table called userdefrelationship inside the entity_metadata (also known as "raw" layer) namespace. You can join the table with other tables like glossaryterm to understand and map the relationships.

Why it matters: Your data estate is a knowledge graph, and its real value lives in the connections. By making relationship labels queryable, the Lakehouse lets you analyze not just what exists, but how everything relates  powering richer governance, discovery, and AI context.

👏 Give it a shot
Query the new relationship data, join it to your terms and assets, and watch your estate's ontology come to life.

Atlan for SAP: Ground Your Agents in the System of Record

● Generally Available

This release turns SAP's notoriously opaque data into a governed, machine-readable context layer for AI. SAP is the system of record for most large enterprises — and the hardest source to ground agents in, thanks to cryptic tables, coded field names, and configuration-driven logic. SAP ECC and SAP S/4HANA are now GA with two new capabilities that give agents (and the people who supervise them) two things they've never had over SAP: provenance — where a number truly comes from — and a map of the human layer, where SAP data is actually created and consumed.

CDS View Column-Level Lineage

Provenance

What's new: Column-level lineage is now generally available for SAP CDS (Core Data Services) views. Trace every column in a CDS view back through its transformations to the exact source table columns that feed it.

What you can do:

• Follow a single field end to end, from the semantic CDS layer down to the underlying SAP table columns.
• Run precise impact analysis — see exactly what breaks downstream if a source field changes.
• Debug and validate at the column, not just the object, level.

Why it matters for agents: This is the provenance backbone of the context layer. When an AI agent surfaces a metric, it can cite the precise origin and transformation path of every value — making the output auditable and trustworthy, and letting governance and quality signals propagate accurately across the SAP estate.

Fiori Apps as a New Asset Type

The Human Layer · First to market for Atlan

What's new: SAP Fiori apps are now a native asset type in Atlan, with asset-level lineage from Fiori apps → CDS views → upstream SAP tables.

The problem this solves: Fiori is the modern SAP UI — where business users actually work, reading, entering, and changing data every day, with near-zero visibility into the data beneath the screen. This release connects the app the user sees to the data it actually touches.

What you can do:

• See, for any Fiori app, the chain of CDS views and source tables it draws from.
• Give business users and stewards a clear map from the interface to the underlying data.
• Trace where sensitive or business-critical data is exposed and modified at the point of use.

Why it matters for agents: Fiori is the human layer of the context graph — where data is created and consumed. Mapping it lets an AI agent understand what an app does in data terms, and lets governance follow data all the way to the screen.

On the roadmap: column-level lineage for Fiori apps · popularity & usage signals for Fiori apps.

What's Next

Next: SAP Business Data Cloud (BDC). Zero-copy data sharing across Snowflake, SAP Databricks, Google BigQuery, and Microsoft Fabric. Context that follows your data across platforms without ever moving or duplicating it — so lineage, meaning, and governance stay intact wherever SAP data is consumed. Connectors for SAP Datasphere and SAP Analytics cloud, complementing our ERP and BW connectors.

More context ingestion from the SAP ecosystem, coming soon:

• Field-level help text as glossaries — SAP's own field documentation, automatically converted into governed business glossary terms and linked to the exact columns they define. The semantic layer that gives agents authoritative meaning for every SAP field.
• Master data as data products — your unique SAP configuration, packaged into governed data products: material types, customer and vendor account groups, and Business Partner groupings, roles, and categories. Context that reflects how your enterprise actually classifies its master data.
• SAP long text as knowledge files — SAP's free-text long texts (notes, descriptions, and documentation) harvested and published as knowledge files, ready to ground agents — for retrieval in agent studios and RAG workflows.

Beyond that — context from across the SAP application landscape (actively working with customers on outcomes and use cases for the below):

• SAP Signavio — business process context (how work actually flows).
• LeanIX — enterprise architecture and application portfolio context.
• SAP IBP — integrated business planning and supply chain context.
• SAP Concur — travel, expense, and spend context.
• SAP SuccessFactors — people and HR context.

The Bigger Picture: SAP + the Leading Non-SAP Context Layer

Pair the deepest context layer for SAP with the leading context layer for everything outside it — cloud warehouses, lakehouses, BI, transformation, and AI tooling — and the whole enterprise becomes legible to AI in ways neither side can deliver alone. An agent can trace a metric from a BI dashboard, through the cloud warehouse, across a zero-copy SAP share, into the CDS view and its source table — with provenance at every hop.

The estate is opening. The connective tissue is here. The result is a single, trustworthy map of how the business really runs — and the foundation for enterprise AI you can actually rely on.

🎉 What's new

Snowflake semantic views are now cataloged directly into Atlan as an open context layer home for the metric definitions that Cortex Analyst, Talk-to-Data and more agents depend on.

Atlan ingests the full hierarchy: the semantic view plus its logical tables, dimensions, facts, and metrics as discoverable, governable assets.

Because these views are the same objects Cortex Analyst runs on, cataloging them closes the gap between your governed metric definitions and the agents querying them.

And Atlan Context Studio lets you build and deploy new agents and semantic views from Atlan with the context they for agents that return accurate, governed answers

✨ Let's dig deeper

Here's what this looks like in practice and how it connects to Context Studio.

• Search for any semantic view and open its asset profile to see its logical tables, dimensions, facts, and metrics in one place.
• Feed these cataloged views directly into Context Studio, where they act as the primary execution surface. Context Studio either attaches to an existing semantic view or generates and updates its definition, with Atlan staying the source of truth.
• Apply the same governance you use elsewhere, like certification, ownership, README, and tags, to make a view trusted before it powers a production agent.
• Note: if your crawler role lacks the required grants, semantic views are skipped without failing the workflow, so an existing crawl won't break.

👏 Give it a shot

To start using semantic views:

1. Check the Snowflake permissions on your Atlan<>Snowflake connection
2. Run or schedule a metadata sync for your Snowflake connection.
3. Use global search and filter by asset type → Semantic view.
4. Open a semantic view to explore its Entities, Relationships, and Metrics tabs.
5. From there, point a Context Studio context product at the view to power an AI analyst.

📘 Full setup guide here. 

Finally, if you are at Snowflake Summit this week, come say hello and learn more about Snowflake+Atlan together!

🎉 What’s new

Atlan just became smarter, faster, and AI-native.

Data teams today need more than a catalog, they need a foundation built for AI. The new Atlan is that foundational context layer: a space to enrich your assets, build enterprise context, and give your LLMs what they need to be accurate and reliable at scale. 

✨ Let’s dig deeper

Here is what you can expect from the new Atlan experience:

✦ Ask Atlan anything
You no longer need to know where something lives to find it. Just ask Atlan. Search for assets, understand lineage, get instant answers about your data, or even ask how a specific feature in Atlan works. Atlan understands your intent and surfaces exactly what you need, without requiring filters, exact names, or technical queries.

🧠 Work smarter & faster
The new Atlan is built to make your AI work better over time. Enrichment agents help you keep your data assets accurate, well-described, and consistently up to date. That enriched data feeds directly into enterprise context.
The result: more reliable, more accurate AI outputs across your entire data stack.

🏠 Clean home for everything
Assets, governance, and your admin center are all reorganized into one focused, clean experience. What used to take extra clicks is now surfaced upfront — so you spend less time navigating and more time doing the work that matters.

👏 Give it a shot

Keep an eye out for an email with more details as we continue rolling this out to all users over the coming weeks.

• Once enabled, switch between old and new UI at any time from your profile dropdown
• A quick onboarding walkthrough will guide you through the changes.

Give the new Atlan a try and let us know what you think. We'd love your feedback as we keep refining the experience!

🎉 What's new

Introducing Knowledge Folders and Knowledge Files to close the gap between your structured data context and the procedural knowledge that actually governs how your business works.

Before this, your SOPs, policies, and compliance docs lived scattered across SharePoint, Confluence, and Google Drive, invisible to agents at the point of use. 

Now you can upload the definitive versions directly into Atlan as governed, first-class catalog assets. 

A Knowledge Folder is a domain-scoped container (e.g., "Finance SOPs"). 

A Knowledge File is the individual document inside it. 

Context agents process each file automatically, extracting glossary terms, attaching business rules, and generating skill files with full lineage back to the source. 

That output flows into Context Repos via Context Engineering Studio, making your unstructured knowledge available to your MCP-connected agents, Atlan's native conversational search, and anything you deploy downstream.

Consider a customer support agent. It knows the order schema, the churn model, the interaction history. But it guesses when a VIP customer asks about a refund outside standard policy because none of the escalation path, the tier-specific SLA, the product defect window live in a database. They live in a PDF or shared doc.

Upload that PDF as a Knowledge File. Context agents extract the rules and make them available downstream. Now the answer is grounded and cites the source.

✨ Let's dig deeper

• Upload once, governed forever: Drag and drop your PDF or Markdown files into a Knowledge Folder. They become searchable catalog assets with lineage, metadata, and access control.
• Context agents extract automatically: After upload, context agents process knowledge files and synthesize glossary terms, business rules, and skills. Everything traces back to the source document.
• Flows into your Context Repos: Extracted knowledge becomes available via Context Engineering Studio. It feeds your Context Repos, conversational search, and any MCP-connected agent downstream.
• You decide what governs agent behavior: You choose which document is the definitive version. Nothing governs agents without your sign-off.

👏 Give it a shot

If your team has SOPs, policy docs, or compliance guidelines that your AI agents should know about, this is where to start.

Click + New > Knowledge Folder from the top right of Atlan. Create or select a folder, drag and drop your PDF or Markdown files, and upload. Open any file's profile page to preview content, review extracted terms, and trace lineage to downstream skill files and context repos.

Admin access is required to upload; all roles can preview and search

See more at Knowledge Folders | Context Engineering Studio

🎉 What's new

As a security admin managing Snowflake access, you'll want this integration because it eliminates shared credentials and centralizes authentication through your existing identity provider.

Previously, users had to manage separate Snowflake credentials or rely on service accounts. Now, Atlan connects to Snowflake using PingFederate OAuth, letting your team authenticate with their corporate identity while you maintain centralized control over access policies.

✨ Let's dig deeper

This integration uses OAuth 2.0 with PingFederate as your authorization server:

• Users authenticate once through PingFederate and access Snowflake resources without storing passwords in Atlan
• Scope-based permissions determine what each user can see and query, aligned with your existing access policies
• Token refresh happens automatically in the background, so sessions stay active without manual re-authentication
• All authentication events flow through PingFederate, giving you a single audit trail for compliance reporting
• You can revoke access instantly at the identity provider level without touching Snowflake directly

🚀 Give it a shot

Go to Governance > Connections > Snowflake and choose Snowflake OAuth and External Oauth as your authentication method. You'll need admin access in both Atlan and PingFederate to complete the setup, refer the setup guide for more information.

Verify the integration by following the below steps:

1. Open an Insights worksheet on the configured Snowflake connection.
2. Run any query. Atlan opens a Login with Snowflake (PingFederate) modal.
3. Click the login button. A new browser tab opens to your PingFederate authorization endpoint.
4. Sign in with your usual SSO credentials. The tab closes and the modal flips to Login successful.
5. Once login is successful, run your queries inside Atlan. Queries authenticate as the PingFederate-authenticated user, not as a shared service account.

📘 Refer to the to setup guide here.

🎉 What's new

If you use AWS, your AI/ML teams may be building together in AWS SageMaker Unified Studio. And your context layer lives in Atlan.

As of today, those two are the same thing.

The AWS SageMaker Unified Studio (SMUS) connector is now generally available - built jointly with the AWS team. Every published asset, data product, project, and glossary term from SMUS now flows into the Atlan Context Layer, and the context you govern in Atlan flows back into SMUS automatically. Business stewards and AI/ML teams work on the same governed context, without leaving the tools they already use.

This is what it looks like when a hyperscaler builds natively on the Context Layer for AI.

✨ Let's dig deeper

🔁 Context flows both directions - not just into Atlan Crawl SMUS domains, data products, projects, published & subscribed assets, glossaries, terms, and key column metadata into Atlan. Reverse-sync descriptions you enrich in Atlan back to SMUS projects, published assets, and columns — so the governed context your data stewards define surfaces automatically in the workspace where your AI/ML teams build.

🔗 See how data products are reused across teams Lineage from any published asset surfaces every project that subscribes to it. Cross-team dependencies that were previously invisible become discoverable in a single view, making impact analysis and reuse decisions far easier.

🧭 Fits the domain model you already operate Attach SMUS projects and assets to your existing Atlan Data Domains. No parallel taxonomy, no duplicate ownership, no forced rework of how your business is organized.

🛡️ Enterprise-ready out of the box IAM-based authentication, a supplied CloudFormation template, preflight checks, and on-demand or scheduled crawls — built for production from day one.

🚀 Give it a shot

Setup is self-serve and most teams are connected in a single session.

In Atlan, head to New Workflow → AWS SageMaker Unified Studio. 

Deploy the supplied CloudFormation template in your AWS account, paste the IAM role ARN into Atlan, run the preflight check, and trigger your first crawl!

For more information, see

• 📘 Connector documentation for setup, supported assets, and reverse-sync configuration
•  📝 Joint AWS + Atlan blog for architecture and design rationale

Why Atlan + AWS:
SageMaker Unified Studio gives your AI/ML teams the workspace. Atlan gives them the context that makes the work trustworthy.

The definitions that drift, the lineage that goes untracked, the governance that gets bypassed — that gap is where AI projects lose credibility before they reach production. With SMUS as a first-class citizen in the Atlan Context Layer, the governed context your stewards maintain is the same context your AI/ML teams build on. It doesn't drift, because it only lives in one place.

Atlan is not just another connector in your AWS stack. SMUS connects to Atlan because the Context Layer for AI is where enterprise context compounds — and compounded context is what makes AI work at scale.

Have setup questions or want to talk through scoping? Reach out to your Atlan CSM or Account Manager. For product-related questions, you can also reach out to Bindu Neeharika at bindu.reddy@atlan.com to help you get from CloudFormation template to your first crawl ⚡

We're excited to announce that the SAP BW/4HANA connector is now available in Private Preview. This release extends Atlan's SAP coverage into the modeling and reporting layer, making it possible to trace a single number on a BEx query all the way back to the SAP application table it originated from.

What's new

The SAP BW/4HANA connector brings the InfoObjects, providers, transformations, and queries that turn raw SAP transactional data into BW models into Atlan for the first time.

Combined with the existing SAP ECC, SAP S/4HANA, and SAP HANA connectors, customers can now extend lineage and discovery into the BW/4HANA modeling layer — tracing data from source SAP application tables, through Transformations, ADSOs, and CompositeProviders, into the BEx queries that consume them. Coverage of the full SAP analytics estate — including legacy BW landscapes, SAP Datasphere, and the SAC consumption layer — will land as those connectors ship over the coming weeks and months.

Supported capabilities

Discovery

Catalog the core building blocks of your BW/4HANA environment:

• InfoAreas — hierarchical organization of BW objects
• InfoObjects — Characteristics and Key Figures, including attributes, texts, and hierarchies
• Advanced DataStore Objects (ADSOs) — standard, staging, and direct-update types
• CompositeProviders — with union and join definitions across underlying providers
• Open ODS Views — virtual access layer to external sources
• BEx Queries and Query Elements — calculated key figures, restricted key figures, filters, variables, exceptions, and conditions
• Transformations and Data Transfer Processes (DTPs) — including rule types (direct mapping, formula, routine) and source/target object references
• DataSources — extraction sources from SAP and non-SAP systems
• Process Chains — orchestration metadata and step dependencies

Lineage

End-to-end traceability across the BW/4HANA stack:

• Source-to-target lineage through Transformations and DTPs
• Provider composition lineage showing how CompositeProviders union and join underlying ADSOs and Open ODS Views
• Query lineage connecting BEx Queries to the InfoProviders they consume and the InfoObjects they reference
• Field-level lineage through Transformation rules — including direct assignments, formula rules, and ABAP routine-based rules
• Cross-connector lineage linking BW/4HANA assets to upstream SAP ECC, SAP S/4HANA, and HANA sources already cataloged in Atlan

The practical outcome within BW/4HANA: a business analyst can trace a BEx query key figure back through every Transformation to its originating SAP table, and a data steward can see exactly which queries depend on a given ADSO before approving a change.

For the full list of supported objects, lineage paths, and configuration requirements, see the SAP BW/4HANA connector documentation.

What's coming next

BW/4HANA is the first milestone in a broader rollout that will bring the entire SAP analytics estate into Atlan. Three connectors are already in active development:

• SAP BW on HANA — the classic NetWeaver BW deployment on HANA, for the many customers who haven't yet migrated to BW/4HANA. Extends BEx query and InfoProvider lineage to the existing BW landscapes still running in production today.
• SAP Datasphere — discovery and lineage for SAP's next-generation data fabric, including Spaces, Local Tables, Views, Data Flows, and Analytic Models.
• SAP Analytics Cloud (SAC) — Story, Model, and Dataset metadata with upstream lineage to Datasphere, BW, and HANA Live Data Models.

Together with the existing SAP ECC, SAP S/4HANA, and SAP HANA connectors, these four upcoming releases will complete the picture: a navigable view of SAP data from raw application tables, through every modeling and warehousing layer — classic SAP BW, SAP BW/4HANA, and SAP Datasphere — into the SAC dashboards and stories where business users consume it. BW/4HANA opens the modeling layer today; BW on HANA extends it to classic deployments; SAP Datasphere covers the next-generation fabric; and SAC closes the loop by bringing the consumption layer into the lineage graph. End-to-end SAP analytics lineage is the destination, and BW/4HANA is the next step.

Getting access

The SAP BW/4HANA connector is available to a limited set of design partners during Private Preview. To request access or learn more, reach out to your Atlan account team.

View the SAP BW/4HANA connector documentation →

Your AI agents are only as smart as the context they can reach.

Over the last few months, Atlan MCP has matured into the production bridge between your governed context layer and every AI tool your team uses, and is already powering AI analysts, internal GPTs, and Cursor workflows with early adopters.

🎉 Your context, natively in more tools

Atlan MCP now ships native in Claude (Desktop, Web, Code), ChatGPT, Cursor, Windsurf, VS Code, n8n, Microsoft Copilot Studio, Glean, and Databricks. Connect once with OAuth or API key. No local install, no replicated setup.

Meanwhile, inside Atlan's UI, Conversational AI is now Generally Available!

✨Remote MCP, production-ready

Hosted per-tenant at https://mcp.atlan.com/mcp.

🔧 A deeper toolbox — 28+ tools and growing every day

- Read: semantic search, column-level lineage, SQL on connected sources, docs with citations
- Write: descriptions, owners, tags, certificates, custom metadata
- Create: glossaries, terms, domains, data products, DQ rules
- Govern: archive, restore, purge; schedule and update DQ rules

📝 Policy-aware by default

New partner integrations such as with Cyera (classification) and Immuta (enforcement) mean sensitivity and access rules can travel with every agent query.

Every agent reads from the same governed context layer. One shared brain. Context stays yours.

🚀 Give it a shot!

Explore the MCP docs

🎉 What’s new

Conversational AI in Atlan lets everyone explore their data estate in plain language instead of hunting through filters and asset pages. Ask questions like “What powers our revenue dashboard?”, “How do we define active customer?”, or “Who owns this table?” and get grounded answers with lineage, glossary, ownership, and quality signals surfaced for you — inside Atlan, your data tools, and collaboration apps.

✨ Let’s dig deeper

Find and understand assets in natural language  

Search across tables, columns, dashboards, schemas, and glossaries by describing what you’re looking for, not its exact name. Conversational AI returns the most relevant assets plus key context like descriptions, usage, and tags.

Trace lineage and assess impact without leaving chat  

Ask “What feeds this dashboard?” or “What breaks if I change this column?” to see upstream sources, downstream consumers, and critical dependencies before you make changes.

Summarize definitions, docs, and signals in one place  

Get quick explanations of metrics and business terms, along with summaries of table readmes, column definitions, and data quality or freshness signals so you can decide if a dataset is safe to use.

Find owners and subject-matter experts instantly  

Use ownership metadata to identify who’s responsible for a table, dashboard, or term, so you know exactly who to tap when you need deeper context or approvals.

Use it where you already work  

Start a conversation from the Atlan homepage or Copilot on any asset page, use the browser extension in tools like Snowflake and Databricks, or ask questions directly from Slack or Microsoft Teams once they’re connected.

Stay in conversation, with answers you can verify  

Refine results with follow-up questions; Conversational AI remembers context within the session. Every answer comes with citations that link back to source assets in Atlan so you can quickly inspect and trust what you see.

 👏 Give it a shot

Configure it in Labs: Conversational AI is being rolled out in phases. Once it has been rolled out to your tenant, users can start using it right away. If you’re an admin, you’ll also see the Conversational AI option in Admin settings → Labs → Atlan AI, where you can configure its behavior and add custom instructions.

Ask your first questions: Open Chat from the Atlan homepage to search across your catalog, or use Copilot on any asset page to ask context-aware questions scoped to that asset.

Use it where your team already works: After Slack or Microsoft Teams is integrated with Atlan, you can ask questions directly in those tools too.

Start with something simple like “Show me trusted tables for MAU”, “How do we calculate ARR?”, or “What’s upstream of the customer 360 view?” — and let Conversational AI handle the rest.