Tutorial | Governance basics#
Get started#
Dataiku’s Govern node enables project managers, lines of business, and compliance managers to track the progress of AI initiatives at the scale of an enterprise. Take your first steps as a Govern node end user!
Objectives#
In this tutorial, you will:
Surface items from connected Dataiku nodes in a centralized location.
Add a governance layer to chosen items.
Move items through governance workflows.
Organize governed projects under business initiatives.
Continue governing as your Dataiku items evolve.
Prerequisites#
To reproduce the steps outlined in this tutorial, you will need:
Dataiku 14.0 or later.
A Dataiku Govern node connected to a Design node.
Caution
By its nature, effective AI governance requires close collaboration between many individuals of diverse responsibilities. Completing governance tutorials may require you to perform actions outside your own day-to-day activities. If you find yourself lacking the permissions to complete certain actions, reach out to your instance administrator. Otherwise, read along to simulate the suggested steps.
Create the project#
From the Dataiku Design homepage, click + New Project.
Select Learning projects.
Search for and select Governance Basics.
If needed, change the folder into which the project will be installed, and click Install.
From the project homepage, click Go to Flow (or type
g
+f
).
From the Dataiku Design homepage, click + New Project.
Select DSS tutorials.
Filter by MLOps Practitioner.
Select Governance Basics.
From the project homepage, click Go to Flow (or type
g
+f
).
Note
You can also download the starter project from this website and import it as a zip file.
Use case summary#
You’ve just created a project in the Design node, Dataiku’s sandbox environment for building analytics, models, and agents. Your goal is to apply a governance framework to this project using the Govern node.
The contents of this project aren’t important. Consider it a stand-in for the kind of projects you’ll be governing. Using this basic project as a demonstration, you’ll be able to understand how the Govern node can fit into your AI governance strategy.
Let’s get started!
On the Design node, navigate to the Governance Basics project you just created.
On the project homepage, next to the title, click the pencil (
) icon to rename the project
<YOUR INITIALS> Governance Basics
to make it easier to identify as your own.From the waffle (
) menu in the top navigation bar of the Design node, select Dataiku Govern.
Tip
Throughout this tutorial, you’ll often move between the Govern and Design nodes. Keep both tabs open to ease switching back and forth!
Surface Dataiku items within the Govern node#
Before taking any actions, it’s important to recognize how the Govern node surfaces items from connected Dataiku nodes.
Start at the Govern homepage#
Begin at the homepage of the Govern node.
If not already there, click the home (
) icon in the top navigation bar of the Govern node.
Recognize the presence of the following pages:
Governable items
Registries for models, bundles, and possibly GenAI
Governed projects
Business initiatives
When you finish this tutorial, you’ll understand the purpose of each of these pages.
Important
Your experience with the Govern node may differ depending on whether you have a standard or advanced license. An advanced license allows for greater customization, as well as greater capabilities with respect to GenAI. Nevertheless, the foundations covered in this tutorial apply equally to all users.
Review an inbox of governable Dataiku items#
The first page to know is the Governable items page. This page functions like a Govern “inbox”. It surfaces “ungoverned” items from all connected Dataiku nodes. You’ll learn what it means to govern an item in later steps!
This page should include the project you just created — as that project is an ungoverned Dataiku item from a synced Design node.
Either from the homepage or directly from the top navigation bar, navigate to the Governable items (
) page.
Recognize the accordion menus of surfaced Dataiku items, including projects, bundles, saved models, etc.
In the Projects section, find your Governance Basics project, and click on its title.
If needed, use the search box to find it.
Review the project’s metadata in the Source Objects (
) tab of the right details panel.
Confirm in the Related objects section that this project contains one saved model, but no bundles.

Test the sync between the Govern and Dataiku nodes#
The Govern node actively tracks certain types of items from connected Dataiku nodes. Bundles are one such item. Add a bundle to the project, and confirm the Govern node recognizes this update.
Return to the Design node, and open your version of the Governance Basics project.
From the More Options (
) menu of the top navigation bar, select Bundles.
Click + New Bundle.
Name it
v1
.Click Create.
Return to the Governable items (
) page of the Govern node.
Select your Governance Basics project.
Confirm the presence of the v1 bundle in the related objects section of the Source Objects (
) tab. (Refresh the page if needed).
Tip
You’ll notice the presence of a icon, indicating that the project, bundle, and model aren’t governed. You’ll understand this soon!
Filter governable items#
At the scale of an enterprise, you might have thousands of items you could govern. Accordingly, it’s worth getting familiar with the search, hiding, and filtering controls at the top of Govern node pages.
For example, the project you created on the Design node includes a specific tag: govern-training
. Filter for ungoverned projects with this specific tag.
From the Governable items (
) page, click the Add Filter (
) icon.
Click the plus (
) icon > Condition to add a condition.
Create a filter where the field value Tags does contain the value
govern-training
.Click Save. Name it
govern-training tag
, and click Save again.Click Close on the filter dialog.
Observe how only items with this project tag remain.

Explore registries of Dataiku items#
For now, resist the temptation to govern the project you’ve created. Complete the tour of the other key pages in the Govern node first.
The registry pages centralize all Dataiku items of a respective type into one location. From one particular registry, an organization can see all its models, bundles, or GenAI items. The ability to filter these lists in various ways makes these registries watchtowers for your data and AI initiatives.
From the top navigation bar of the Govern node, navigate to the Model registry (
).
Recognize that you can filter the registry in many ways, including to show only deployed models (
).
Find your version of the Governance Basics project, and expand the accordion menus to drill down into the model and model versions inside it.
Select the active model version (
) by clicking on its name.
Explore the right Details panel options, including the Model metrics (
) tab to review metrics of the model version.
Repeat the same process for the Bundle registry (
), or, if available to you, the GenAI registry (
). You’ll find these pages function just like the model registry.
Tip
Remember that the Govern node surfaces items from all connected nodes. The Dataiku instance (node ID) column reports which node the item comes from.
Add a governance layer to Dataiku items#
In the registry pages, you likely noticed a govern status for all items. Indeed, beyond surfacing synced items from other Dataiku nodes, the first action you’ll often take in the Govern node is adding a governance layer to a synced Dataiku item of interest. In other words, you’ll choose which Dataiku items you want to govern.
Focus on governed projects#
First, check if your Govern node already has projects with an active governed status.
From the top navigation bar of the Govern node, navigate to the Governed projects (
) page.
Your page might be empty. It could also have projects that other users sharing the space have chosen to govern.
If you have projects here, feel free to explore this page further, recognizing new terminology like template, workflow, and business initiative.
Tip
Once you govern your first project, it will appear on this page!
Govern your first Dataiku project#
Add a governance layer to the Design node project you initially created.
Using the top navigation bar of the Govern node, navigate to the Governable items (
) page.
In the Projects section, find your version of the Governance Basics project.
At the end of its row, click the gavel (
) to govern it.
Doing this for the first time, we’ll temporarily skip over some details.
For the project definition, confirm you’ve selected Save as a new Govern project.
For the project template, select the Dataiku Standard template.
Apply this same standard template to all applicable existing child items.
Depending on your instance settings, you may have different rules for synced items than shown below. If needed, override those rules so that synced items aren’t governed. (No row in the column for synced items should have a checkmark and assigned template).
Click Govern.

Tip
You’ll return to governing future synced items at the end of the tutorial!
Understand the source objects of Govern items#
When governing the project, you saw terms like templates, child items, and business initiatives. You’ll return to these terms, but first it’s important to distinguish between synced Dataiku source items and capital “G” Govern items.
The Govern node syncs Dataiku items (such as projects, models, bundles, and GenAI items) from connected Dataiku nodes. These items are the actual assets built by teams of data scientists, engineers, and analysts.
The Govern node presents the choice to govern these Dataiku source items, thereby creating Govern items. Although a Govern item includes the metadata of its Dataiku source item, these objects exist only in the Govern node.
To better illustrate this distinction, consider what happens when you delete a governed project.
Navigate to the Governed projects (
) page.
Find your version of the Governance Basics project, and click on its name to open your first capital “G” Govern item, in this case, a Govern project.
Navigate to the Source Objects panel.
Recognize that the source of this governed item is your Design node project.
In the item header, click the vertical dots (
) > Delete Govern project.
Read the confirmation that this action doesn’t delete the original Dataiku project found in the Design node, and then click Delete Govern Project.
Return to the Governable items (
) page to confirm your Dataiku project is once again available to be governed.
Tip
Not every Govern item necessarily has a Dataiku source item. Later, you’ll learn about pure Govern node items, such as business initiatives, that exist only in the Govern node.
Details when adding a governance layer#
The first walkthrough of governing a project skipped over some important details in the dialog. Review them now.
Governance option |
Purpose |
---|---|
Governance templates |
The template defines the structure and workflow steps of governed items that you’ll explore in the next section of the tutorial. Organizations with advanced licenses have the ability to define custom items beyond the standard template. |
Business initiatives |
An extra level of organization to group Governed projects under a shared theme. You’ll create one in the last section of this tutorial. |
Child items |
Dataiku items respect a certain information hierarchy. For example, model versions belong to a saved model, which belong to a project. Most often you’ll govern at the project level, including all child items. |
Existing vs. synced items |
The project you’re governing will often contain existing child items. In addition to choosing to govern existing child items, you can also choose how to govern future (synced) child items that Dataiku users may add to the project as it evolves. Your Govern node has its own default rules for handling future items, but you can override them if needed. |
With a better understanding of the details, govern the Dataiku project once more (thereby creating a Govern project), repeating the same procedure as before.
From the Governable items (
) page, find your Dataiku project, and click the gavel (
) again to govern it.
Apply the same Dataiku Standard governance template to the project and all existing child items.
Click Govern to add the governance layer again.
Confirm your project’s return to the Governed projects (
) page.
Navigate to the Model registry (
) or Bundle registry (
) pages.
From the page header of either registry, change the Governed status to include only governed items.
Find your Governance Basics project among the governed models or bundles!

Use governance workflows#
You’ve now added a governance layer to a Dataiku project (as well as its child bundle, model, and model versions). Now explore the contents of a capital “G” Govern item.
Add metadata to a governed item#
One benefit a governance layer enables is the ability to attach various kinds of metadata to a Dataiku item. For example, you can enrich a Govern project with descriptions, scope definitions, reviewer assignments, and a schedule.
Navigate to the Governed projects (
) page.
Find your Governance Basics project, and click on its name to open it.
While in the Overview panel, click Edit in the item header.
Next to Sponsor, click + Add, and select yourself.
Copy-paste the text below into the Description field.
This project is solely for testing the capabilities of the Govern node.
Still within the Overview panel, scroll down to the Qualification snapshot. Try selecting different values for the risk, value, cost, and feasibility ratings.
Feel free to edit any further fields, and click Save in the item header when finished.

Tip
It’s up to you and your organization to determine how to make the best usage of a governed item’s fields. You’ll want to focus on collecting the necessary information to make informed governance decisions.
Advance a project through a governance workflow#
Beneath the overview, you’ll see a workflow of five steps in the left panel. This is the standard workflow that you selected when governing the project.
For now, advance through these steps quickly. In Tutorial | Governance lifecycle, you’ll learn how to make them a meaningful part of your governance lifecycle.
From the left panel of your governed project, click Exploration to view that step of the project’s workflow.
Click Edit in the item header.
Click Set As Ongoing to indicate this step is in progress.
For the Notes field, copy-paste the following example:
During the Exploration phase, we need to determine the key risks and projected value of the project.
Click Set As Finished to advance to the next step in the workflow.
Scroll down to the Qualification step and explore the available fields.
Click Set As Finished, and repeat this process until your project has finished the Delivered step.
Feel free to move back and forth between steps to test how it works. Click Save in the item header when finished.

Advance child items through a governance workflow#
Govern projects aren’t the only Govern item that have a workflow. Remember that when adding the governance layer to the project, you also chose to govern the project’s child items. According to the standard template, Govern bundles and Govern model versions have their own governance workflows.
You can navigate to the child items in several ways, including from the Source Objects panel of the parent project.
From your governed project page, navigate to the Source Objects panel.
Under Related objects, expand the Saved models accordion menu.
Expand the project’s saved model, and select the active version (
).
Explore the active model version’s metadata in the right panel, including the Model metrics (
) tab.
In the right panel, click Open to view the governed model version.
Recognize how the model version has its own independent overview and workflow steps, which you can progress through in a similar manner as the governed parent project.
Tip
At the top of the page representing the governed model version, recognize the nested hierarchy: project, saved model, and model version. You can govern up and down this hierarchy depending on your desired level of granularity.
Review the matrix and Kanban views of governed projects#
Now that your governed project includes metadata and workflow progress, explore how it’s visualized in matrix and Kanban views.
From the top navigation bar, return to the Governed projects (
) page.
Find your Governance Basics project, noting its Completed workflow step (having finished the Delivered step).
Locate your project in the qualification matrix, and click its plot point to filter for projects matching the same criteria.
Review the metadata you added in the Overview (
) tab of the Details panel.
Switch to the Kanban (
) view to represent governed projects according to workflow stages.

Tip
You can customize the matrix axes to show the qualification metrics most relevant to your governance needs.
Manage governed projects with business initiatives#
As your organization scales its governance activities, you may quickly accumulate hundreds if not thousands of governed projects.
A business initiative functions as an extra level of organization to manage governance activities. It enables grouping governed projects together on some shared theme or characteristic. On top of this grouping, it provides its own workflow and space for documentation.
Create a business initiative#
From the Governed projects page, you may have noticed that your governed project isn’t assigned yet to a business initiative. Create one now!
From the top navigation bar of the Govern node, go to the Business initiatives (
) page.
Click Create.
If necessary, select Dataiku Standard as the template.
Name it
<YOUR INITIALS> Test Initiative
.Click Create to make a new business initiative.

Add a governed project to a business initiative#
Once you have a business initiative, you can add a governed project to it.
Within the Overview panel of the new business initiative, click Edit in the item header.
For Sponsors, click + Add, and select yourself.
Copy-paste a description such as:
This business initiative groups together projects testing Dataiku Govern.
Next to Governed projects, click + Add.
Find your Governance Basics project, and Select it.
Back in the header of the business initiative page, click Save.
Return to the Governed projects (
) page, and confirm your governed project is now part of the new initiative.
Tip
Here you started with a business initiative and added a governed project to it. You can just as well open a governed project, and add it to an existing business initiative.
Move a business initiative through a governance workflow#
Business initiatives, as defined by the standard template, follow their own workflow.
From the Govern node’s top navigation bar, go to the Business Initiatives (
) page.
Find your business initiative, and click on its name Test Initiative to open it.
From your business initiative page, select the Ideation workflow step.
Click Edit in the item header.
In the Ideation step, click Set As Ongoing.
Make any adjustments to the fields and ratings as desired.
Click Set As Finished to advance to the In Progress step.
When finished exploring, click Save in the item header.
Return to the Business Initiatives (
) page, and find your in-progress initiative in the matrix (
) and Kanban (
) views.
Tip
There’s no right or wrong way to structure business initiatives. Some may represent permanent entities such as departments, business units, or geographic areas, and might never reach the “Delivered” workflow step.
Others may be time-bound, like initiatives tied to a business quarter or a special project, with clear start and end dates.
Having grouped a project under a business initiative, your tour of the standard Govern node pages is complete! Next, see how to manage governance as your Dataiku items evolve.
Govern an evolving project#
Governance isn’t a one-time snapshot. It’s an ongoing commitment! The remainder of this tutorial focuses on how the Govern node handles changes in the synced Dataiku items which it governs. By doing so, you’ll further clarify your understanding of Dataiku items and Govern items.
Review the governance rules of future Dataiku items#
Any active Dataiku project will continue to evolve. Among other changes, this means new models and bundles. How does a Govern project respond to the evolution of its source objects?
The answer depends on your instance’s auto-governance rules, which define if and how future Dataiku items in the project should be governed.
Recall the dialog when first adding the governance layer to an ungoverned Dataiku project. Although your own instance rules may have differed, unlike for existing items, you didn’t add a governance template to future synced items.

Take a moment to review the rules for your instance.
From the top navigation bar of the Govern node, open the waffle (
) menu.
Select Governance settings.
Yours may differ, but in the screenshot below, no type of synced item from Dataiku nodes is automatically governed.
Accordingly, there is no applicable Governance template to select.

Tip
There’s no one correct answer to defining auto-governance rules. It’s up to your organization to determine which rules best meet your governance objectives!
Add a child item to a governed project#
Put these rules to the test by creating a new bundle in the Dataiku source object of the governed project.
Return to the Design node, and open your version of the Governance Basics project.
From the More Options (
) menu of the top navigation bar, select Bundles.
Click + New Bundle.
Name it
v2
.Click Create to finish adding a second bundle to the Dataiku project.
Back in the Govern node, return to the Source Objects panel of the governed project.
In the Related objects section, confirm the v2 bundle is present (the sync works), but it isn’t governed (assuming your auto-governance rule for bundles is the same as shown above).

Override auto-governance rules#
Your instance rules may not always define the behavior you want for future child items. For this project, assume that you do indeed want to automatically govern future Dataiku bundles.
Navigate to the Governance settings panel of the governed project (not the instance-wide settings).
Click Override (or Edit depending on your instance rules).
Next to bundles, check the box to Govern synced items.
Select Dataiku Standard as the governance template.
Click Save to confirm the new custom rule.

After choosing to govern future child bundles of your project, test it works as expected.
In the Governance Basics project on the Design node, add a third bundle named
v3
.Refresh the Source Objects panel of the governed project.
In the Related objects section, expand the Bundles accordion menu.
You should have governed v1 and v3 bundles, as well as an ungoverned v2 bundle.

Edit the source object of a governed project#
That addresses the governance of entirely new Dataiku source objects. But how does the Govern node respond to changes in the source objects themselves?
To explore this question, change the name of the Dataiku source project belonging to your Govern project.
Return to the Design node, and open your version of the Governance Basics project.
From the project homepage, click the pencil (
) icon to edit the title. Name it
<YOUR INITIALS> New Governance Basics
, and click Save.Refresh the Source Objects panel of the governed project.
In the Dataiku project section, confirm the governed project points to the updated “New” project title.
Confirm the presence of an information (
) icon in the item header of the governed project. Hover over it to find the name of the Dataiku source project (which no longer matches the name of the governed project).

Tip
Recall the distinction between Dataiku items and Govern items first discussed when deleting the original governed project. These mismatched names highlight the difference between the synced Dataiku source project and the capital “G” Govern project connected to it.
If desired, navigate to the Overview of the governed project page. Click Edit in the item header, and match the name of the governed project to its Dataiku source project. The information () icon disappears!
Next steps#
Congratulations! You’ve taken your first steps using the Govern node to:
Surface Dataiku items from connected nodes.
Apply a governance layer to those items.
Advance those items through workflow steps as defined by a governance template.
Organize governance activities according to business initiatives.
Continue governing items as their Dataiku source objects evolve.
Before you finish, take a moment to delete work that you no longer need as a courtesy to those sharing your Govern node.
From the Business initiatives (
) page, open your test initiative. From the vertical dots (
) menu, click Delete Business Initiative.
From the Governed projects (
) page, open your project. From the vertical dots (
) menu, click Delete Govern Project.
From the Design node, open your project. From the project homepage, click Actions > Delete this project.
In this tutorial, you added a governance layer to Dataiku items, and moved them through workflow steps in an arbitrary manner to understand the basic functionality of the Govern node.
Next, look at these how tools can play a instrumental role during all stages of the AI lifecycle. Start with pre-qualification in the ideation phase and execute an AI project all the way through to monitoring a deployed project.
You’ll see how to do that in Tutorial | Governance lifecycle!