For stewards

Editing an asset

Change a description, an attribute or a link, and what happens when you do.

Before you start

To change a value you need Edit attributes (ASSET_EDIT) on the asset. In the starter model it comes with Data Owner, Data Steward, Technical Custodian, Subject Matter Expert, Metadata Manager and Sysadmin.
To add or remove links you need Manage relations (RELATION_MANAGE).
A role held over a data domain covers everything the domain owns. So if an asset is read-only for you, the fix is usually one assignment higher up, not one on each asset.

If you may not edit, the page says so once, near the top: Read-only for your name.

Change a value

KRISID saves one field at a time, so History can say exactly what changed and who changed it.

Open the asset and find the value under Attributes.
Click the value. It turns into a box, a dropdown or a larger text area, depending on the kind of attribute.
Type or choose the new value.
Press Save, or press Enter (in a long text box, use Save). Press Cancel or Esc to leave it as it was.

You'll see Saved. and the page refreshes from the repository. The choices in a dropdown are the attribute's allowed values, exactly as the metamodel sets them. A date field accepts dates like 2026-03-31 or 31 Mar 2026.

The name and the key at the top work the same way. The key is what a re-load from Excel matches on, so change it only when you mean to.

Mandatory attributes

An attribute your repository treats as mandatory carries a required chip. If it is empty, it shows missing. You can change a mandatory value, but you can't clear it: the save is refused and the message says why.

Which attributes are mandatory, and for which kinds of thing, is set in the metamodel. Your repository may differ from the starter model, where Definition is required on business terms, entities, rules and data products.

Harvested assets: what is yours and what is the source's

Tables, views, columns and the other physical assets come from a source system through a harvest. On these pages you'll see a Harvested. notice.

Name and key belong to the source. They are locked, because the next harvest would put them back.
Attributes, responsibilities and links are yours to edit. Adding them is the point of governing harvested data.
Descriptions have two owners. The source's own comment or description is the attribute Description from Source, under From the source, and every harvest refreshes it. The Description attribute belongs to stewards: a harvest never writes it.
Everything under From the source is read-only. Change it in the source and harvest again.
Source tags, if any, are shown as the source has them and can't be edited here. To change one, change it in the source and harvest again.

If the source no longer has the asset, the page opens with Missing in Source. That's a note from the last harvest, not a deletion. It clears on its own if the source shows the asset again.

Add a link

Under Relations, open Link this to….
Choose the kind of link, for example owned by a Data Domain or realised by a Table. You only see the links your metamodel allows for this kind of asset.
In the picker, tick what you want to link to. Candidates are grouped by where they sit (system, database, schema), and ticking a group takes everything under it. Use the search box to filter by name, key or location.
Press Link, or Link followed by the count when you've ticked several.

A short message tells you how many were linked, how many were already there, and why any were refused. One refusal doesn't stop the rest. If a link allows only one asset at the other end, the picker lets you choose only one.

Remove a link

Find the link under Relations and press the × beside it.
The × turns into Unlink?. Press Unlink to remove the link, or Keep to leave it.

Clicking anywhere else or pressing Esc also keeps the link. There is no undo, so check the name first.

Create a new asset

On the list for a kind of thing (for example Business Terms), press New business term. You need Create assets held over the whole repository; in the starter model that is Metadata Manager or Sysadmin. The form marks required fields and won't create the asset until they're filled in. Under Links you can attach it to a domain, entity and so on as you create it. Press Create business term to finish.

Harvested kinds of thing have no New button. The connector creates those.

Delete an asset

Press Delete… beside the asset's key. It appears only if you may delete this asset. Deleting needs Delete assets (ASSET_DELETE) held over it. A harvested asset also needs Delete harvested assets (HARVESTED_DELETE), which only the Sysadmin holds in the starter model. If the source still has a harvested asset, the next sync brings it back.

Before anything is deleted, the page tells you what goes with the asset: its links to other assets, and what sits under it (for a Subject Area, its Data Entities and their Data Attributes). If something sits under it, you choose:

Delete only the asset. What was under it stays, no longer under anything. Browse the logical estate then shows it at the top, under a heading such as Data Entities not under any Subject Area.
Delete it and what is under it. Only what you may delete goes. Anything you may not delete, such as a harvested table if you're not a Sysadmin, stays and is named in the message.

If a workflow governs deletions of this kind of asset, Delete raises a request instead, and nothing is deleted until someone approves it. What goes with it is fixed when the request is raised.

When a change needs approval

If a workflow governs this kind of asset, the page says Changes here are proposed, not written. Every edit then goes into Your change set on the page instead of being saved: values, the name and key, links and responsibilities. Submit the set as one request when it's ready. Nothing changes until someone approves it. A new asset of a governed type is a proposed asset until it's approved. See Requests and approvals.

History

The History section at the bottom lists every change to the asset: day, time, who made it, which field, and the old and new values. It includes links added and removed and responsibilities assigned and removed. Changes made by a harvest or a load are labelled with what made them. Press Show earlier changes to go further back.

Good to know

A save that the repository refuses shows a message in the metamodel's own words, for example a link that allows only one parent.
Editing a field on the asset page also means that field wins over the semantic model's YAML later. See Editing the semantic model.
To change many assets at once, use Loading from Excel.