Governance Roles

ONE admin changes the application model and settings, manages group hierarchy, and creates new entity types. They make sure the overall consistency of the metadata model is preserved.

ONE admins have full access to all system management features of ONE including access management.

ONE operators can perform actions on all data assets that change the ONE workflows. For example, ONE operators can manage synchronization with Keycloak and the lifecycle of assets, track data quality, create reports.

ONE operators cannot modify the application model and settings nor access the assets.

Data owners define the data quality requirements of a specific department, division, or data domain.

They work with a team of ONE operators and other roles to ensure the data governance criteria are met. Data owners are usually senior business managers.

Data Consumers work with metadata only when they browse Ataccama ONE. They are business or technical users with limited knowledge of data management.

They can view metadata but are not allowed to view actual data values.

Data Stewards work with both technical assets, like tables, fields, files, systems, and models, and business assets, like business terms, acronyms, KPIs, and reports. They manage the life cycle of assets, track data quality, and create reports for data owners.

The level of access to the System entity governs whether a role can draft changes in the metadata model. However, to apply the changes you must also have the MMM_admin identity provider role, which is attached to the ONE Administrator role by default.

The level of access to the User Management entity determines the actions a role is able to perform as related to the User and Access Management features.

Child entity of the Source entity. Defines a data source connection.

Identifies catalog item attributes to which a specific business term should be applied. Evaluates the data quality of catalog items and their attributes.

For more information, see Detection and DQ Evaluation Rules.

Terms enable further analysis of data, as evaluation and quality checks operate on the basis of expected values of specified terms.

For more information, see Data Quality.

Access to result files of post-processing plans.

For more information, see Monitoring Project Results, Reports, and Notifications, section Export and post-processing plans.

Components are ONE Desktop files that can be used for three possible data processing steps:

Entity that defines assets in the Data Catalog. For more information, see Catalog Items.

Child entity of the Source entity. Defines the location of a data source.

Defines the workspace folder of virtual catalog items in the data catalog.

Entity that describes the source of catalog items in the application. ONE can work with data from a number of sources.

After a data source has been added, data and metadata from this source can be imported and consequently cataloged and profiled, as well as monitored for data quality.

When you user assigns policies, the conditions on the application work are set.

These conditions have a "do when" format: "do something when something happens". Policy Condition Settings screen configures the timing for the action (the "when" part). In other words, it specifies where to look for particular values when evaluating conditions on certain entities.

Entity that allows you to use reference data in ONE. They provide a list of predefined values for an attribute, and can be used both in DQ evaluation rules and detection rules.

For more information, see Lookup Items.

A list of values aggregates referenced and enumerated lists of values you can assign to entities. Currently, there are two default lists: Deployments and Data Instances. Once you add a value list, you can configure it as needed.

Used to evaluate the data quality of selected catalog items and monitor it over time.

Data is evaluated in accordance with the DQ rules applied to the selected items, automatic anomaly detection, and structure checks.

For more information, see Monitoring Projects.

Entity that defines policies. The level of access to this entity determines whether you can create and manage policies in ONE.

Entity that can be used to organize policies under a specified regulation. Regulations are a single-level aggregation framework for policies (this means you cannot have regulations within regulations).

Entity that can be used to organize policies in a specified category. Categories are a multilevel aggregation framework for policies (this means you can store categories within categories).

Entity that defines various configuration options within the Data Catalog. Additionally, Full and Edit access level to this entity enables you to create SQL catalog items.

Enables you to configure profiling settings.

Entity that defines the level of access to various configuration options related to Data Quality features.

The level of access to this entity determines whether a role can make changes to the layout, color palette, and navigation of ONE. For more information, see the following topics:

The level of access to this entity determines whether a role can configure the Slack integration with ONE.

The level of access to this entity determines whether a role can use the Data Export feature.

The level of access to this entity determines whether a role can configure the MS Teams integration with ONE.

The level of access to this entity defines the actions a role can perform as related to ONE Data.

The level of access to this entity defines the actions a role can perform as related to Content Security Policy Configuration.

The level of access to this entity defines the actions a role can perform as related to data reconciliation.

The level of access to this entity defines the actions a role can perform as related to the ONE home page features.

For more information, see The Home Page.

The level of access to this entity determines whether a role can configure the DQ Firewall features.