🎉 What’s new

Say hello to Enhanced Metadata Policies in Atlan! You can now create dynamic, rule-based metadata policies inside personas—making governance more scalable, flexible, and precise than ever before.

✨ Let’s dig deeper

With this update, you no longer need to manually select individual assets when setting up metadata access controls. Instead, you can build policies using dynamic filter rules—based on asset metadata like tags, schema, database, or qualified names.

Here’s how it works:

🧩 Create metadata policies using flexible rules

• Each rule filters assets based on metadata fields such as:

  • ✅ Tags (with support for tag values as well)
  • ✅ Schema Qualified Name
  • ✅ Database Qualified Name
  • ✅ Asset Qualified name
• These rules are composed inside personas, directly from the “Metadata Policies” section.

➕ Use up to 3 rules per policy

• You can combine up to three rules to define asset access.
• This makes your policy both powerful and targeted—no manual asset selection needed.

🌐 Requires connection selection first

• Before adding any rules, you must select a data connection.
• This ensures your filters are applied within the right context and metadata scope.

Why this matters: Dynamic rules let you govern entire categories of assets with just a few clicks, supporting governance at scale while staying maintainable and auditable.

Note- This feature won't work today if you have data quality turned on for your Atlan instance.

👏 Give it a shot

Try building your first rule-based metadata policy inside a persona today! Whether you're granting access to all Snowflake assets inside a connection tagged “PII” or restricting access to specific schemas, this new system makes it faster and smarter to govern access dynamically.

Let us know how you’re using it—we’re excited to hear what you think!

🎉 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

Access requests just got better!
You can now request access to BI assets directly within Atlan—just like you do for tables, views, and other data assets. Whether it's a dashboard in Power BI or a workbook in Tableau, this update helps streamline how users gain access to governed BI assets in your workspace.

✨ Let’s dig deeper

Here’s what this means for your data consumers and stewards:

🔓 Request Access on BI Assets

Users can now initiate access requests from:

• BI dashboards
• Reports
• Workbooks
  All these assets now show a "Request Access" button in Atlan, making governed BI assets part of the self-serve experience.

🛠️ Flexible Fulfillment Options

Once a request is raised, access can be granted using one of the following methods:

• ✅ JIRA ticket generation
• ✅ ServiceNow ticket generation
• ✅ Webhook with a customizable payload
  This ensures your existing IT and approval workflows remain fully in control.

⚠️ SQL + BI Assets? Here’s the catch.

If a request includes both SQL and BI assets, then:

• SQL assets may be fulfilled automatically via Atlan’s Insights module (if enabled)
• BI assets, however, will follow the external fulfillment process (JIRA/ServiceNow/Webhook)

This ensures compliance and auditability, while allowing flexibility in how access is granted across asset types.

Note: Fulfillment for BI assets does not currently support direct access provisioning inside Atlan.

👏 Give it a shot

Start exploring governed Access Requests on BI assets today—streamline how business users access dashboards, reports, and visualizations while keeping governance workflows intact. We can’t wait to hear how this simplifies your access management!

🎉 What’s new
Atlan now supports Databricks Struct datatypes, giving you complete visibility into nested fields for the first time.

✨ What’s in Store

• Explore Struct fields with an interactive tree view—expand & collapse for clear visualization.
• Seamlessly navigate Structs just like simple columns.
• Full metadata context now available for all Struct fields.

👏 Give it a shot

Start exploring Databricks Struct fields in Atlan today — and let us know what you think!

📘 Learn More

• What does Atlan crawl from Databricks?

🎉 What's new

Re-introducing Governance Workflows & Inbox — a powerful way to automate, route, and act on governance requests in Atlan. Whether you're modifying tags, updating descriptions, or defining ownership, you now have fine-grained control and visibility over how governance changes are reviewed, approved, or auto-executed — all from a central place.

And that’s not all — with Conditional Branching, your workflows can now route requests dynamically based on metadata, glossary location, or change type. It's governance, reimagined.

✨ Let’s dig deeper

Governance in Atlan just leveled up. Here’s everything that’s a part of governance workflows and task inbox:

🧠 Governance Workflows

Set up smart approval flows that are triggered when governance actions are taken on assets — for example:

• Updating descriptions
• Changing tags or certificates
• Creating new glossary terms

Each flow follows a clear structure:

1. WHEN a condition is met (e.g., asset tag is modified)
2. CHECK if auto-approval is enabled or not
3. ROUTE the request for approval — or skip if allowed

You can create multiple workflows, each mapped to different metadata fields or asset types, providing full control and customization.

🌿 Conditional Branching

Use conditional logic to dynamically route approvals:

• Route based on where a glossary term is created (e.g., Finance vs Marketing)
• Trigger based on what metadata is being modified (e.g., Tags vs Certificates)

This allows you to send different requests to different teams — like:

• Tag changes → Data Security Team
• Certificate updates → Data Privacy Council

Bonus: These branches can be configured with multiple layered conditions, enabling deeply tailored workflows for large, federated teams.

📥 Governance Inbox

All triggered governance requests now land in a centralized Inbox where reviewers can:

• View pending actions
• Approve or reject requests
• Track what’s happening across teams

This means no more digging through scattered approvals — everything is just where it should be.

👏 Give it a shot

Start building your Governance Workflows today in Atlan and see how much smoother, smarter, and scalable your governance can become. With conditional logic and an Inbox that brings it all together, you’re all set to drive clean, auditable, and federated governance at scale.

Let us know how you're putting it to work — we're all ears! 🪄

🎉 What's new

Domains are now discoverable directly from the assets page in Atlan! No matter how a user navigates—whether through assets, products, or search—they’ll now encounter domains as a first-class entity, making domain discovery seamless across the board.

✨ Let's dig deeper

Previously, discovering domains depended on navigating through specific UI paths like the domain browser or the products section. With this update, domains are now fully integrated into the asset search experience.

Here’s what’s new:

• Domains now appear in global asset search results
  You'll find them listed just like tables, views, and products—with a new domain-specific badge.
• Searchable, filterable, and ranked
  Domains come with relevance-based ranking and can be filtered using the asset type selector.
• Complete visibility
  Domain metadata—like name, description, and associated assets and products—can now be previewed from the asset results.

This means that no matter where users begin—searching for a product, asset, or table—they can discover and navigate to the relevant domain effortlessly.

Why this matters: This boosts discoverability, enables better context-switching, and helps users connect data assets to business concepts in just a few clicks.

👏 Give it a shot

Try searching from the global assets page and see how Domains now surface as part of your everyday discovery journey. Whether you’re starting with a table, a product, or just exploring—your domains are now right there with you!

🎉 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!