As an administrator, you can:
Users with the Manage Catalog model role permission will see a tile entitled Data Model on the Catalog homepage.
The Data Model area is where Catalog administrators can define the structure, relationships, and governance rules for all objects within the Catalog. This includes configuring Object Types, metadata fields, associations, review cycles, interests, and conformance rules. Use this area when setting up new governance models or maintaining existing structures.
Bulk updates - Certain users might also be given the role permission Bulk load Catalog data. This permission allows users to extract Catalog objects and create/update/delete Catalog objects at scale.
To begin defining new metadata, click the Create new Object Type button and specify the required information for your Object Type:
By default, only a Name field is captured for new objects. You can configure additional fields to capture further metadata about the object.
When configuring fields for an Object Type, you can control the type of data captured, how each field behaves, and how it is displayed within forms and tables. The available configuration options include:
Beyond defining the fields that users will complete, you can also configure how this Object Type relates to other Object Types. These relationships, known as Associations, determine how objects link together, how users navigate between them, and how information is presented within the form.
The Is relationship many to many? setting determines how the association between two Object Types behaves.
When this setting is enabled, the relationship becomes many‑to‑many.
Each Object Type can link to multiple records from the other, and associations can be created and managed from either side, making this suitable for flexible, non‑hierarchical relationships.
For example, a Policy can apply to many Processes, and a Process can reference many Policies. This setting allows for a more dynamic and interconnected data model, reflecting real‑world complexities where entities often have multiple relationships with each other.
When this setting is turned off, the relationship becomes one‑to‑many.
Each record in the current Object Type can link to only one record in the target, while the target Object Type can link to many records from the current Object Type. This is ideal for hierarchical relationships.
For example, a Data Asset belongs to one Business Unit, but a Business Unit can have many Data Assets.
Associations support many of the same configuration controls as fields, including:
In addition, associations have options specific to relationship behavior, such as:
Interest Types let you assign specific roles to users or groups for each object. These roles can use whatever terminology fits your organisation. For example, a policy might need an Executive Sponsor, a data asset might require a Steward, Owner and Custodian, and a business process might track who is Responsible, Accountable and Consulted.
As with associations and field configuration, you can also set conformance monitoring rules for Interest Types. This lets you control how important each interest assignment is using the Is required settings.
Within this area, Catalog administrators can also optionally allow users to subscribe to updates for each object of this type. For example, a user can subscribe to updates relating to a specific policy so that they get notified against any updates relating to this item.
Interest Types support many of the same configuration controls as fields, including:
In addition, Interest Types have specific options, such as:
These are the individual Users, User groups and/or Interest Types responsible for reviewing user suggested changes for an object or Object Type.
Review cycles allow administrators to ensure that key objects are periodically reviewed for accuracy. This supports ongoing governance and helps maintain up‑to‑date metadata.
Learn more about Review cycles and how to use them to maintain data quality across your Catalog.
Conformance levels indicate how important a field is for data completeness and quality. Each level determines whether warnings are shown when values are missing. The levels are:
, indicating a critical issue that needs attention. , indicating a high severity issue that needs attention.
, indicating a moderate issue that should be addressed.You can format the text using Markdown - allowing the use of rich text, links and images.
Markdown is a simple markup language for adding rich formatting and embeds to plain text. Below are some of the most commonly used markdown elements.
Using special characters
# Heading 1
## Heading 2
### Heading 3
Headings go as small as H6.
**Create bold text with double asterisks** and *italic text with single asterisks.*
Markdown supports ordered lists using numbers:
Markdown also supports unordered (bulleted) lists using dashes:
- First item
- Second Item
- Third item
`Format a line of code with backticks.`
Add a horizontal rule line with three dashes (---).
[Link text](https://google.com)
Images are supported if the image file is Base64 encoded.
For example: 
Format tables with horizontal bars and dashes.
| Table | Column | Header |
| ------ | ------ | ------ |
| First | row | here |
| Second | row | here |
The resulting table:
[.no-100perc-width]
| Table | Column | Header |
|---|---|---|
| First | row | here |
| Second | row | here |