BACK TO ALL POSTS

How can you use DataHub to manage and control user access to metadata

Rbac

Access Control

DataHub

Data Catalog

Paul Logan

Jan 30, 2023

Rbac

Access Control

DataHub

Data Catalog

‘How do I control access to metadata?’ is a common question among data practitioners.

DataHub

Metadata Access Control in DataHub: All you Need to Know

When it comes to Role Based Access Control (RBAC) and Attribute Based Access Control(ABAC), DataHub has the answers.

Read on to learn how you can use DataHub to implement access controls that regulate and control how your organization’s users view and edit metadata.

Who, What, and How: Access Control in DataHub

Access control is a way for you to regulate your end users’ access to your metadata so you can manage and control who can access what data and how. In this article, we show you how DataHub’s access control policy lets you control how your organization’s users view and edit metadata — based on entity, domain, or platform type.

Why you need Metadata Access Controls

‘How do I control access to our organization’s metadata?’ is one of the most common questions we’ve heard from data practitioners and DataHub users.

And it’s easy to see why — there are so many reasons to regulate and limit how users access and edit your metadata entities and domains.

For example, you could want

  • Dataset Owners to edit documentation, but not tags
  • Data Stewards to edit tags, but no other metadata
  • Data Analysts to edit links for data pipelines they consume
  • Data Platform teams to manage users, groups, and policies, and view analytics

…and so on.

Access Control using DataHub

Permissions management under DataHub Settings

Permissions management under DataHub Settings

DataHub allows you to declare fine-grained access control policies via its UI (under “Settings-> Permissions”) as well as the GraphQL API.

DataHub currently supports access control via

  • Platform Policies (determine who has platform-level privileges)
  • Metadata Policies (control how users interact with metadata entities)

DataHub’s Access Control using Platform Policies

Platform policies serve to assign specific privileges to DataHub users and groups. For example, they can help you define

  • Who can edit dataset documentation and links
  • Who can add Owners to a Chart?
  • Who can add Tags to a Dashboard, etc.
  • Based on platform-level privileges, these help you determine who can
  • Manage users & groups
  • View the DataHub Analytics page
  • Manage the policies themselves
  • Platform policies can be looked at through
  • Actors: Users or groups to whom the policy applies
  • Privileges: The privileges assigned to the Actors (e.g. “View Analytics”)

Here is a quick look at the platform privileges DataHub offers for access control


It’s important to note that platform policies don’t have a target resource that they control.

DataHub’s Access Control using Metadata Policies

A Metadata Policy can be looked at through

Actors (WHO)

Determines the specific users or groups to whom the policy applies.

DataHub currently supports three ways to define the set of actors the policy applies to

  • a list of users
  • a list of groups, and
  • owners of the entity.

Privileges (WHAT)

Determines the actions permitted by a policy, e.g. “Add Tags”

This enables DataHub operators to access and manage the administrative functions of the system.

Resources (WHICH)

Outlines the resources that the policy applies to, e.g. “All Datasets”.

A Resource Filter defines a list of criteria that determines the set of resources to which the policy applies. (Note, that if there are no criteria or a resource is not set, the policy is applied to ALL resources.)

Each criterion defines a:

  • field type (like resource_type, resource_urn, domain),
  • a list of field values to compare, and
  • a condition that checks whether the field of a certain resource matches any of the input values.

How can you use DataHub’s Access Control Policies?

We hope this helps explains how DataHub gives you a simple and effective way to control who accesses your metadata and how.

To know more about how you can implement access control in DataHub using platform and metadata policies, check out our detailed guide: Policies Guide for Access Control in DataHub

Have any questions or suggestions on access controls in DataHub?

Come say hello on Slack. 👋

Rbac

Access Control

DataHub

Data Catalog

NEXT UP

Governing the Kafka Firehose

Kafka’s schema registry and data portal are great, but without a way to actually enforce schema standards across all your upstream apps and services, data breakages are still going to happen. Just as important, without insight into who or what depends on this data, you can’t contain the damage. And, as data teams know, Kafka data breakages almost always cascade far and wide downstream—wrecking not just data pipelines, and not just business-critical products and services, but also any reports, dashboards, or operational analytics that depend on upstream Kafka data.

When Data Quality Fires Break Out, You're Always First to Know with Acryl Observe

Acryl Observe is a complete observability solution offered by Acryl Cloud. It helps you detect data quality issues as soon as they happen so you can address them proactively, rather than waiting for them to impact your business’ operations and services. And it integrates seamlessly with all data warehouses—including Snowflake, BigQuery, Redshift, and Databricks. But Acryl Observe is more than just detection. When data breakages do inevitably occur, it gives you everything you need to assess impact, debug, and resolve them fast; notifying all the right people with real-time status updates along the way.

John Joyce

2024-04-23

Five Signs You Need a Unified Data Observability Solution

A data observability tool is like loss-prevention for your data ecosystem, equipping you with the tools you need to proactively identify and extinguish data quality fires before they can erupt into towering infernos. Damage control is key, because upstream failures almost always have cascading downstream effects—breaking KPIs, reports, and dashboards, along with the business products and services these support and enable. When data quality fires become routine, trust is eroded. Stakeholders no longer trust their reports, dashboards, and analytics, jeopardizing the data-driven culture you’ve worked so hard to nurture

John Joyce

2024-04-17

TermsPrivacySecurity
© 2025 Acryl Data