Engineers / Advanced

Governance with Unity Catalog

Access, lineage and policy on Databricks: groups per schema, policy tests, data contracts and the Professional exam.

Who it is for

Platform and data engineers who own who can see what on a Databricks platform.

Steps
7
Level
Advanced

What you can do afterwards

  • Model access as reader and contributor groups per schema
  • Test access policies before a release
  • Enforce a data contract before data is published

Start here

Take the NexOps course

Governance with Unity Catalog. Identity, privileges, policies, evidence, sharing and governance as code

7 lessons · 5 h

This path begins with our own course, with lessons, knowledge checks and labs. The external courses below are extra practice.

Open the course

Extra practice

  1. Course

  2. Course

  3. Build

    Reader and contributor groups per schema

    Goal. Give two teams the right access to three schemas, using groups only, and prove it with tests.

    What to do

    1. Create a catalog with three schemas: raw, curated and shared.
    2. For each schema, create a reader group and a contributor group. Grant to groups, never to people.
    3. Add table or volume grants only where a use case needs them.
    4. Write a small test that logs in as each group and checks what it can and cannot read.

    What good looks like. A new person gets access by joining a group, and the tests fail the build when a grant drifts.

  4. Read

  5. Check

  6. Certify

    The Professional exam covers security and production practice.

Course details come from each provider. Check the provider page for the latest.

Next step

Want your team to learn this together?

We give workshops to company teams and students, on-site or online. Tell us who the participants are and what they should be able to do afterwards.

Accepting projects for Q4 2026