Dataiku Govern concepts¶
Dataiku Govern licenses¶
Depending on which license you have, you will be able to use the Govern node differently in your Dataiku environment.
Standard license gives you access to all core features, and more.
Advanced license allows you to customize your instance. In other words, it empowers you to create custom pages, workflows, sign-offs, and more.
Note
Reach out to your Dataiku Account Manager or Customer Success Manager to learn more about licenses, features, and profiles.
Items in Dataiku Govern¶
Item is the generic way to describe the objects manipulated in Dataiku Govern. Items can be:
Dataiku items: there are synced from Dataiku nodes and the hierarchical relationship between objects are represented in the way Dataiku Govern employs inheritance throughout its architecture. Governable items are projects, saved models, saved model versions, and bundles.
Govern items: these can be pure govern object such as Business initiatives or the representation of the layer of governance added on Dataiku items.
See also
To learn more, see Types of Govern items.
Note
With Advanced Govern you can build other types of items using the Blueprint Designer features.
Dataiku Govern pages¶
Dataiku Govern will automatically provide views of all your items within the following pages:
Governable items: This page is your inbox to view synced Dataiku items that have not been governed.
Model and Bundle registry: Focus on all models and bundles grouped by projects.
Other standard pages will only represent governed items. These pages are enriched by creating items directly or by adding a governance layer to existing items:
Business initiatives: list of business initiatives
Governed projects: list of governed projects
Governance actions¶
Two main actions can be applied to synced items:
Hide, meaning no further action is necessary. This will hide the item in Dataiku Govern, but it will not affect the item visibility in other nodes.
Govern, which means additional metadatas and/or actions are expected. Once this optional layer has been applied to projects, models, model versions or bundles, they become Govern projects, Govern models, Govern model versions and Govern bundles.
This layer can embed specific definitions, metrics, attachments, workflows, sign-offs, and more.
These actions are mainly applied in the Governable items page.
The governance layer can be added manually or automatically. You can decide to:
Automatically govern items as soon as they are synced from the instance Governance settings page.
Manually define the governance rules from the Governance modal.
See also
For more information, visit Concept | Governable items.
Instance Governance settings¶
From the Application menu, the Governance settings page allows admins to define auto-governance rules on the related items of the project:
Bundles
Saved models
Saved model versions
For each related item, you can define the template to use.
Warning
Auto-governance will be applied only if the parents are governed.
Governance modal settings¶
Governance settings can be applied at different levels:
the item on which the Govern button has been selected.
related items where the governance is mandatory or suggested.
The governance rules can be applied on the existing and the upcoming items.
By default, the rules for upcoming items are inherited from the instance governance settings and are identified by an “Instance rules” tag. It is possible to override these rules for a specific item and it will be marked with a tag depending on the item impacted:
“Custom rules” for projects
“Project rules” for bundles and saved models
“Model rules” for saved model versions
See also
To learn more, see Concept | Governance layers.
All Actions history centralized in the Timelines¶
From the Applications menu, the Timeline page centralizes events such as updates, deletions, and creations linked to items. You will be able to filter by:
Date and Time, Users, Items type, and Items.
Actions on Items, Templates, Sign-off, and others.