Skip to content
Datablau DAMData governance documentation

Datablau DAMData governance user guide

Follow governance tasks from resource discovery to trusted data use, with clear product and permission boundaries.

Datablau DAM covers administration, metadata, standards, quality, assets, security, services, lineage, and Data Governance Agents. Each module has its own goals, entry points, permissions, and workflows. Read by module or follow the governance journey.

Product navigation ​

ModulePurposeGuide
System ManagementUsers, organizations, roles, workflows, tasks, configuration, licensesAdministration
Metadata ManagementHarvest and maintain tables, fields, reports, files, and basic object lineageMetadata
Data StandardsDefinitions, codes, dictionaries, metrics, dimensions, field mappingsStandards
Data QualityRules, validation, remediation, verificationQuality
Data CatalogCatalog structures, registration, inventory, publicationCatalog
Data MarketplaceDiscover and request assets or products with approval recordsMarketplace
Data SecurityClassification, discovery, policies, masking governanceSecurity
Security GatewayServer and JDBC-based dynamic masking and auditGateway
Data ServicesDevelop, test, publish, request, and call APIsServices
Data LineageMaps, parsing, impact analysis, application scenariosSQLink
Data Governance AgentsAI-assisted governance through Intelligent Data GovernanceDIG

Choose a reading path ​

Start with resources ​

  1. Prepare systems and sources and harvest metadata.
  2. Inspect tables, fields, reports, and basic lineage. Use SQLink for advanced maps, scenarios, and parsing.

Start with governance requirements ​

  1. Create standards, codes, metrics, and dimensions.
  2. Implement requirements as quality rules and tasks.
  3. Complete classification, discovery, and access controls in Data Security.

Start with asset use ​

  1. Design catalogs, register, and publish assets.
  2. Discover and request assets and products.
  3. After approval, the accountable team delivers data offline through organizational procedures.

For API publication and consumption, use Data Services. Product requests and API authorization are separate workflows. For governance metadata integration, use the REST API guide, distinct from published business data APIs.

Product relationships ​

CapabilitiesResponsibilities and boundariesWhen to combine
Metadata lineage and SQLinkMetadata provides object-based dependency views. Independently deployable SQLink adds spaces, parsing, maps, impact, and scenarios. Basic lineage entitlement is separate from SQLink.Use basic views for object tracing; use SQLink to build and validate advanced paths. Connectivity and synchronization follow deployment settings.
Metric Standards and Metric ManagementBoth belong to Data Standards. The former maintains definitions and dimensions. The latter adds atomic/calculated/qualified metrics, mappings, queries, monitoring, and permissions under the Data Metrics license.Use basic definitions for consistent meaning; use management for operational queries and monitoring. Definitions alone do not produce values.
Catalog and marketplaceCatalog administrators organize, maintain, and publish assets. Consumers discover and request them. Marketplace approvals retain decisions; they do not deliver data.Publish discoverable content, submit requests, then coordinate offline delivery.
Security and gatewaySecurity defines classification and policies. Gateway server and JDBC Driver enforce dynamic masking and audit on configured paths.Define protection requirements, configure the actual access route, and verify results.
DAM and DIGTraditional DAM modules hold governance objects and results. DIG assists tasks and organizes governed semantics and knowledge into context. Its UI name is Intelligent Data Governance, subject to license and permissions.Review proposals and verify target results; validate space context before publishing to AI applications.

Administrator setup ​

Complete system preparation for organizations, roles, workflows, and sources. Check license, functional permissions, data scope, and approval policy separately. An available menu does not grant every operation or object.