Data governance - Ontologie Documentation

At a glance

Governance centralizes control, quality, and traceability of your data. Define approval policies, classify sensitive information, monitor instance quality, and visualize data lineage : all from a unified interface.

Practical example: in a procurement process, you can require dual approval before any modification to a supplier contract, classify prices as "Confidential", verify that every order has a positive amount, and trace the origin of each piece of data in the catalog.

What you'll do

Key vocabulary

Term	Meaning	Example
Policy	A rule that defines when an approval is required.	"Any instance deletion requires 2 approvals"
Classification	A sensitivity level assigned to a piece of data.	Confidential, Public, Internal
Quality check	An automated verification on your instances.	"The email field must match a valid format"
Lineage	The trace of a data item's origin and journey.	Supplier -> Order -> Invoice
Catalog	The inventory of your entity types with their metadata.	Owner, steward, quality score, freshness
Quarantine	An isolation zone for instances that fail a check.	Instance "Order #42" awaiting correction
Custom role	A role you create with specific permissions.	"Analyst": read dashboards + knowledge base
Override	A permission adjustment for a specific member.	Deny ontology access for Marie
ACL	Access control list on an individual resource.	Space "Finance": read-only for Jean

Permission architecture

%%{init: {'theme': 'base'}}%%
flowchart LR
  Member["Member"] --> Role["Role"]
  Role --> Perms["Permissions"]
  Perms --> Module{"Module"}
  Module -->|Ontology| Read["Read / Write"]
  Module -->|Governance| Approve["Approval"]
  Module -->|Dashboard| View["View"]
  Override["Override"] -.->|Adjusts| Perms
  ACL["Resource ACL"] -.->|Restricts| Read

  classDef light fill:#dce6f1,stroke:#234a7a,stroke-width:2px,color:#1f2a37
  classDef dark fill:#e8a848,stroke:#c48a2a,stroke-width:2px,color:#1f2a37
  classDef accent fill:#5ab5a0,stroke:#3d8b76,stroke-width:2px,color:#1f2a37
  classDef output fill:#edf2f7,stroke:#234a7a,stroke-width:2px,color:#1f2a37

  class Member light
  class Role dark
  class Perms accent
  class Module dark
  class Read,Approve,View output
  class Override,ACL light

A member receives a role that defines their base permissions. Overrides adjust permissions for a specific member, and ACLs control access to individual resources.

Recommended paths

Links with other modules

Ontologie: governance applies to the entity types and instances of your business model. Approval policies protect critical modifications.
Workflows: pipelines can automatically trigger approval requests when a governed operation is detected.
AI Agent: the agent respects governance policies and can query the data catalog to answer questions about data quality or origin.

Expected result

Your data is protected by approval policies, classified by sensitivity level, monitored for quality, and traced in a centralized catalog. Every critical modification goes through a validation workflow before being applied.