🎉 What’s new

As a data leader, you'll want to understand how your teams are adopting and using Atlan.

We've added a new usage_analytics namespace/schema to Atlan Lakehouse that exposes product telemetry captured from Atlan’s UI – every page view, user action, and identity snapshot – so you can understand how your teams interact with Atlan and measure adoption, engagement, retention and beyond.

Previously, you had to rely on custom charts and exports to understand who was active, which features were used, and how engagement changed over time. Now, curated product usage tables live directly in your Lakehouse, so you can analyze product usage using the same SQL and tools you already use and trust.

✨ Let’s dig deeper

In practice, this means you can turn raw Atlan activity into clear, visual insights about how your teams work with data:

• Track active users over time by workspace, role, or team so you can see whether onboarding and enablement actually stick.
• Understand feature adoption by looking at which core workflows (like search, lineage, glossary, or queries) are used most, and where usage drops off.
• Monitor engagement patterns (daily, weekly, monthly activity) to spot healthy teams, identify dormant groups, and time interventions before adoption slips.
• Build retention views that show how frequently users come back after their first week or month, and which behaviors correlate with long-term value.
• Join usage analytics with your own business data (for example, teams, departments, or customers) so you can see which parts of the organization get the most value from Atlan.

Because everything lives in your Lakehouse, you can plug these tables into your favorite compute platform or data visualization tool, so you can build reports and AI applications to understand how Atlan usage evolves across teams, features, and time.

👏 Give it a shot

You can start exploring usage analytics data for your Atlan tenant today:

• First, make sure Lakehouse is enabled for your Atlan tenant
• In your Lakehouse environment, look for the usage_analytics namespace/schema alongside your existing Atlan metadata schemas
  • Use your preferred compute platform to run SQL queries against the usage_analytics tables to inspect active users, features, or time ranges
  • Connect your BI or reporting tool to your compute engine to build dashboards that visualize active users, feature adoption, and retention for your Atlan tenant
  • If you use Claude as your AI assistant, run the same usage analytics queries conversationally using the atlan-usage-analytics skills repository so you can ask questions in natural language instead of writing SQL.
• Check out sample queries for product usage analytics in our use case documentation.

📘 Learn more

Visit the docs to learn more about the usage_analytics schema, including tables, use cases, and sample queries you can use to drive product usage analytics use cases.

🌊 Introducing Atlan Lakehouse

Atlan captures rich context about assets across your data estate, including definitions, tags, ownership, usage, and lineage, which you can use to answer core governance and adoption questions with confidence. 

Historically, teams have had to wait hours or days to export this metadata from Atlan, load it into their compute platform, and only then start building reports or AI applications to understand how their data estate is being used.

Atlan Lakehouse is a new way to work with Atlan. We now store this rich context about your data estate in an open, interoperable lakehouse that’s instantly accessible from your preferred engines, so you can build dashboards and AI applications on Atlan context immediately, without custom exports or pipelines.

🎉 What's new

You can now enable Lakehouse for your Atlan tenant via Atlan’s App Marketplace and start building dashboards and AI applications on your Atlan context in minutes.

✨ Let’s dig deeper

Atlan Lakehouse is an Apache Iceberg–based data lakehouse that contains everything Atlan knows about your data estate, exposed through an Iceberg REST catalog that your engines can query like any other source.

Just like the rest of Atlan’s platform, Atlan manages the infrastructure behind the scenes so you can focus on connecting your warehouse and building reports, dashboards, and AI applications. Once Lakehouse is enabled, you can instantly power AI and advanced analytics with rich Atlan context:

• Treat metadata like data
  Unify technical, business, governance, and operational signals in a high-performance repository that can feed AI models, contextual search, and agentic workflows across your stack.
• Answer governance and adoption questions easily
  Answer questions like “What percentage of assets are documented or tagged?”, “Which domains have the most stale tables?”, or “Where are critical data quality gaps?” directly from Snowflake or other supported engines – without building export jobs.
• Use your preferred Iceberg REST–compatible engine
  Use any Iceberg REST-compatible engine (for example Snowflake, Spark, Trino) so Atlan context shows up alongside your existing data sources and follows the same analytics patterns you already use.

👏 Give it a shot

If you are an Admin on Atlan, you can enable Atlan Lakehouse for your tenant:

1. In Atlan, go to Workflows > Marketplace.
2. Find the Atlan Lakehouse app tile.
3. Click Enable. We'll notify you when your Lakehouse is ready.

Once your Lakehouse is ready, you can connect any Iceberg REST-compatible engine and start building dashboards and AI applications on your Atlan context.

📘 Learn more

Visit the docs to learn more about popular use cases, including sample queries you can copy and paste to jump-start governance dashboards, adoption reports, and AI applications.

We’re thrilled to announce that Atlan’s SAP ECC and SAP S/4HANA connectors are now live in Public Preview!

This marks a major milestone in our mission to bring deep metadata discovery, lineage, and governance to the SAP ecosystem — helping enterprises unlock visibility into their most complex, business-critical systems.

Why This Matters

End-to-End SAP Metadata Discovery and Governance
Atlan now natively connects to SAP ECC and SAP S/4HANA to extract comprehensive metadata directly from the application layer — including Components, TCODES, Function Modules, ABAP Programs, application components, tables, views, fields, check tables, CDS views and the relationships between them. This allows teams to understand the “what” behind their SAP Components like FI, LO, MM, SD and CO and how the data flows and is consumed within the modern data stack.

New Features from PrPr Release

Column-Level Check Table Relationships
The connector now automatically discovers column-level check table relationships, enabling precise data lineage and semantic context. 

Application Component Hierarchy
We’ve added Application Component Hierarchy relationships — allowing automatic discovery of related SAP tables, fields, and data objects by business domain or component (FI, MM, SD, LO, PP, PM, etc.).
These hierarchies can now be leveraged to build rich business semantic Data Products in Atlan that align directly with SAP’s organizational structure, driving cleaner discovery and business alignment.  If interested in more automation around this please contact your Atlan account representative.  

This helps users discover and connect transactional and master data across key SAP for use as data products such as:

• Business Partners
• Customer & Vendor Master
• Material Master
• Sales & Purchase Orders
• Work Centers
• G/L Accounts
• Profit Centers
• Maintenance Plans
  …and more.

Smarter Metadata Scoping

New flexibility lets users filter the SAP metadata extraction scope by:

• Application Component(s) – focus on only the modules relevant to your use case (e.g., FI, SD, MM).
• Atlan Asset Types – choose which metadata objects (tables, function modules, Programs, TCODEs, views) to include or exclude based on business requirements.

This enables faster, more targeted metadata ingestion and reduces noise across massive SAP landscapes.

 What’s Next

This Public Preview is just the start of Atlan’s journey in the SAP ecosystem.
Coming soon on our roadmap:

• SAP Business Data Cloud
• SAP BW on HANA
• SAP BW/4HANA
• SAP Datasphere
• SAP Analytics Cloud
• SAP Business Objects

Together, these will provide an end-to-end metadata lineage bridge across SAP’s legacy and modern data SAP Business Data Cloud ecosystems — from SAP to cloud analytics and beyond.

Interested in early access or upcoming connectors?
Reach out to your Atlan Account Representative to learn more or join the next preview cohort.

📘 Learn More

• SAP ECC
• SAP S/4HANA

🎉 What’s new

Atlan now supports an OpenLineage based integration with Alteryx! This allows you to catalog, discover, and manage your Alteryx workflows data assets, providing you with seamless access to real-time data flows.

✨ Let’s dig deeper

You can setup the Alteryx connector to seamlessly discover and document your Alteryx workflows

• Explore workflow lineage, workflow inputs & outputs
• Explore asset level lineage across your metadata estate
• Enrich assets with metadata: descriptions, tags, terms and beyond

👏 Give it a shot

Ready to integrate Alteryx with Atlan? Get started today!

Interested in additional OpenLineage or Alteryx integrations? Reach out!

🎉 What’s new

The Atlan MCP Server is a powerful way to bring AI into your metadata workflows (such as managing your assets or glossaries), without sacrificing control or context.

With this update, you can use our remote MCP servers instantly in your IDE (think Cursor or Windsurf) or AI workflow tool of choice (like Claude or n8n) with no local overhead and authentication managed securely via Atlan.

✨ Let’s dig deeper

Here’s what this means for you in practice:

• Connect your IDEs or AI workflow tools to a remote MCP server using just the server’s URL and credentials
• Manage access with OAuth (SSO) or API keys
• Use MCP powered capabilities inside tools like Claude, n8n, Microsoft Copilot Studio, Windsurf, or Cursor without local setup
• Switch between multiple servers easily, helpful for dev, staging, and production environments
• Collaborate seamlessly, since teammates can connect to the same remote MCP without replicating installs
• Keep your local machine clean while still tapping into full MCP functionality

👏 Give it a shot

Read the setup guide for step-by-step instructions.

And be on the lookout for what's next with Atlan's MCP, from new actions to integrations with Slack, Teams and beyond

🎉 What's new

Introducing OAuth Clients in Atlan! You now have a more secure, scalable way to generate API tokens using client credentials—designed for modern authentication flows. With short-lived tokens and tighter control, this enhancement brings enterprise-grade security and flexibility to your integrations.

✨ Let's dig deeper

Head over to the Admin Center → API Access → OAuth Clients tab to get started.

Here's how the new OAuth flow works:

1. Create a new OAuth application
   You’ll receive a Client ID and a Client Secret after setup.
2. Secure your secret
   The Client Secret is shown only once at the time of creation. Make sure to store it securely—it's not retrievable later.
3. Generate short-lived access tokens
   Use the Client ID and Secret to request an API token. These tokens are time-bound, ensuring better security.
4. Regenerate anytime
   If the token expires, you can use the same client credentials to fetch a new one. No need to manually reset or rotate tokens unless needed.

This approach gives you:

• 🔒 Improved security via short-lived tokens
• 🔄 Repeatable generation without friction
• 🛠️ Better control over API access points in Atlan

Tip: Use this flow when integrating Atlan with internal apps, pipelines, or external orchestration tools.

👏 Give it a shot

Create your first OAuth Client in the Admin Center and experience more secure and manageable API authentication. As always, we’d love your feedback on how this fits into your workflows!

🎉 What's new

Introducing webhook events for Domains and Products in Atlan! You can now set up webhook triggers for key events related to these asset types. This enhancement allows you to seamlessly integrate Atlan with external systems by sending real-time updates when changes occur—like domain creation, updates, or product modifications.

This unlocks powerful automation use cases across your ecosystem, helping you react instantly to events and maintain consistent data workflows.

✨ Let's dig deeper

To get started, go to the Webhook settings in your admin panel. You'll now see new options for Domains and Products in the list of event types. You can choose to enable events such as:

• Domain Created
• Domain Updated
• Domain Deleted
• Product Created
• Product Updated
• Product Deleted

Once enabled, Atlan will automatically send webhook payloads to your configured endpoint whenever one of these events occurs.

Webhook payloads follow the same structure as other Atlan event notifications and include details like the asset’s name, GUID, user who triggered the action, and a timestamp—making integration and automation simple and predictable.

Note: Ensure your receiving system is configured to accept and process the incoming payloads as expected.

👏 Give it a shot

Start leveraging webhook events for Domains and Products to streamline your workflows and keep your data operations in sync across tools. Already using it? Let us know what you think—we’d love your feedback!

🎉 What's new

As an Atlan admin, you can now permanently remove users from your Atlan instance and transfer asset ownership to a fellow team member. Note that removing a user from your Atlan instance is a permanent and irreversible action.

With the remove user capability now available, Atlan admins can:

• Remove other users from Atlan.
• Transfer assets from the removed user to another user within the same flow.

Learn more: How to manage users

🎉 What's new

Raise and track data access and revocation requests with ease using the brand-new ServiceNow integration! Once requests have been approved, tickets will be auto-created in ServiceNow, and you will be able to track their status directly in Atlan — ensuring full visibility without manual creation.

Here's how it works:

1. You must have the governance workflows and inbox module enabled in your Atlan workspace.
2. Your Atlan admin needs to set up the ServiceNow integration while working with a System Administrator of your ServiceNow instance with a security_admin role.
3. Once set up, you can use ServiceNow to request or revoke data access for governed assets in Atlan or any other data source!

✨ Let's dig deeper

Managing data access and revocation requests across multiple systems can be time-consuming and error-prone, often resulting in incomplete details or unnecessary back-and-forth.

Atlan makes this easy with the ServiceNow integration:

• Raise data access requests — ServiceNow can now be configured as an action within Atlan’s data access governance workflow. After approval, ServiceNow tickets are automatically generated with all the required details.
• Revoke data access — Atlan admins can now raise data access revocation requests for any user on a source, directly from Atlan. Once initiated, a ServiceNow ticket for the revocation request will be automatically created, streamlining the process.
• Real-time tracking — track the status of your ServiceNow requests in real time and right within Atlan, reducing delays and increasing transparency.

👏 Give it a shot

Ready to integrate ServiceNow with Atlan? Say goodbye to fragmented workflows and switching between different tools. Use the ServiceNow integration in Atlan to raise requests and work with your data, all in one place!

Learn more:

• How to integrate ServiceNow
• How to link your ServiceNow account
• How to automate data governance
• How to create governance workflows
• How to revoke data access

🎉 What's new

Introducing a new user role in Atlan — Workflow admin! This role helps your users manage connector workflows while having member-like access to other areas of the product. You can delegate workflow management duties without giving users access to the rest of the governance center or any part of the admin center.

✨ Let's dig deeper

The workflow admin subrole allows for:

• Enhanced delegation — you can delegate connector workflow management to specific users without giving them access to other admin capabilities.
• Improved security — a workflow admin will not be added to the “All admins” group on connections. This means that you have the ability to add a workflow admin to a connection only if you want them to manage the connection. With member-like access required for other areas of the product, your existing persona configurations will work seamlessly.

👏 Give it a shot

As an Atlan admin, you can head straight to the admin center and change the role of an existing user to that of a workflow admin or create a new user as a workflow admin. And as you try it, let us know what you think!

Learn more: How to delegate administration