- 0 minutes to read

Manage the Repository

The Repository Model is only as useful as it is correct. These pages show administrators, and users whose Role may change the Repository, how to add, edit, clean up, and restore each kind of Repository entity.

  • ✅ One page per entity, with every management action step by step
  • ✅ Clear rules on who may delete, restore, and permanently delete
  • ✅ Business users keep short, read-only guides in Getting Started

Tagging two Systems with With Selected, Manage Tags, and then deleting them, animated walkthrough (7.12)
Animated walkthrough: the daily clean-up. Tag and delete many entities at once with With Selected, shown on Contoso sample Systems.

The walkthrough shows the steps, the same in the Integrations, Systems, Services, Contracts, Message Types, Endpoints, and Domains lists:

  1. In Repository > Systems, filter the list and tick the Systems to clean up.
  2. Choose With Selected > Manage Tags.
  3. Add the Tag to all selected Systems, then click Save and close. Each listed Tag is set to All, None, or As is for the selection; Tags that aren't listed are not touched.
  4. Both Systems now carry the Tag.
  5. Choose With Selected > Delete (2).
  6. Confirm. Deleted Systems can be restored.
  7. The Systems disappear from the list, but they're deleted, not gone: tick Include deleted to see them again.

On this page, an administrator finds the management page for each Repository entity. Business users who only look things up start with the Repository Overview instead.

Understanding who manages the Repository

The same lists open from two places in the Web Client. Which actions you get depends on your Role, not on the menu you came from, except that the Administration menu itself needs the built-in Administrator Role.

flowchart LR BU["fa:fa-user Business user
Access"] ED["fa:fa-user-pen Editor
Access, Create, Modify"] AD["fa:fa-user-shield Administrator"] View["fa:fa-eye Find and view"] Change["fa:fa-pen Add, edit,
delete, restore"] Purge["fa:fa-trash-xmark Permanently Delete
system entities"] PurgeUC["fa:fa-trash Permanently Delete
user content"] BU --> View ED --> View ED --> Change ED --> PurgeUC AD --> View AD --> Change AD --> Purge AD --> PurgeUC style BU fill:#2678BD,color:#fff style ED fill:#E47528,color:#fff style AD fill:#9E59BB,color:#fff style View fill:#93d16d style Change fill:#FFD525 style Purge fill:#c33d34,color:#fff style PurgeUC fill:#E47528,color:#fff

What each kind of user can do with Repository entities. Access, Create, and Modify come from the Permission Set for the Repository Model. Permanently deleting a system entity needs the Administrator Role; user content, such as Articles, Images, Files, and C4 Diagram Sets, is permanently deleted with Modify. Deleted items can be restored until they are permanently deleted, see Show deleted records.

Who Can do Where it's documented
Business user (Access) Find and view entities Getting Started - Repository
Editor (Create, Modify) Add, edit, delete, and restore entities; permanently delete user content The pages below
Administrator All of the above, plus Permanently Delete of system entities The pages below

Set the rights on each Role's Repository Permissions tab:

  • Access on Repository is the global gate; without it, the Repository menu isn't shown at all (Repository Access).
  • Each entity has an Access row (read) and a Permissions for all row with Create and Modify.
  • Every right is Inherited, Allow, or Deny, and a Deny in any of the user's Roles always wins.
  • Modify also covers delete and restore. Permanently Delete isn't a separate right; who may use it depends on the kind of entity, see Two delete models.
  • Contracts exist only while UseContracts is true, and the Custom Fields menus are hidden while DisableCustomFields is on.

Two delete models

New 7.12 Nodinite deletes in two ways, depending on who owns the content. Delete and Restore always need Modify; Permanently Delete differs:

Model Entities Delete and Restore Permanently Delete
User content Articles, Snippets, Templates, Document Profiles, Images, Files, C4 Diagram Sets, and C4 Diagrams Modify Modify, on live or deleted items (no need to delete first or tick Include deleted)
System entities Everything else: Integrations, Systems, Services, Contracts, Message Types, Endpoints, Domains, Component Types, Resources, and so on Modify The built-in Administrator Role, and only after the item is deleted

Some items are refused even with the right permissions, and the result message names each refused item and why:

  • Shipped (built-in) Articles, and Articles that live Articles still include
  • A C4 Diagram Set that still holds diagrams
  • A Component Type that is built in or still used
  • A Domain used as a lane in a BPM

A delete never detaches the items that use the deleted one: a deleted Component Type stays on its Systems, icon and all, until it is permanently deleted.

Permanently deleting any of the seven Repository entities, Integrations, Systems, Services, Contracts, Message Types, Endpoints, and Domains, opens one shared impact dialog first. Children that are already deleted go with the entity; live children are detached, never deleted, and are never a reason to refuse:

Entity Its deleted children Its live children
System Its deleted Services and Contracts are permanently deleted with it Live Services and Contracts are kept and lose the System; the dialog lists them
Service Its deleted Contracts are permanently deleted with it Live Contracts are kept and lose the Service
Integration, Contract, Domain They own no Repository entities What links to them is unlinked
Message Type, Endpoint They own no Repository entities What links to them is unlinked. A Transport Contract left without a Message Type or Endpoint is removed together with its Contract; the dialog lists those Contracts by name

Only these things refuse an item. The dialog lists them before anything happens, in a box headed These are not permanently deleted:, one line per item:

  • The item isn't deleted: Delete it first; only deleted Systems can be permanently deleted.
  • A BPM uses the Domain as a lane (Domains only). The BPMs tab marks the lane in red; remove the lane first.
  • It's the default Message Type or the default Endpoint (Message Types and Endpoints only): it is the default Message Type, which is never permanently deleted.
  • The item no longer exists.

Refused items are left out: Permanently Delete acts only on the others, and stays disabled when nothing can be purged. The dialog counts on the live data what the purge removes, keeps, and changes (Impact tab), and lists the Log Views (Views tab) and BPMs (BPMs tab, not shown for Message Types and Endpoints, which no BPM uses) it affects: a Log View that filtered only on the deleted entity is no longer restricted by it and shows more events. Permanently Delete stays disabled until you tick I understand that this cannot be undone, and the result is written to the Log Audits.

Restoring one deleted System and permanently deleting another, with the impact dialog, animated walkthrough (7.12)
Animated walkthrough: the Administrator-only purge. Restore what you need, then permanently delete the rest after reviewing the impact.

The walkthrough shows the steps:

  1. Tick Include deleted. The deleted Systems show up, marked Deleted.
  2. On the one to keep, choose Action > Restore. On a deleted row, the menu ends with Restore and Permanently Delete.
  3. Confirm the restore.
  4. The System is Available again, with its Tags.
  5. On the other, choose Action > Permanently Delete.
  6. Review what the purge changes in the impact dialog.
  7. Tick I understand that this cannot be undone, then click Permanently Delete.
  8. The result message names only what was purged: 1 System permanently deleted. It is gone with everything listed in the review. If the data changed between the review and the click, it adds how many items could not be permanently deleted because they changed since the review. When none can be purged any more, it says Nothing was permanently deleted and asks you to reload the list and try again.

What each Repository list offers

New 7.12 Every Repository list follows the same conventions: Manage Tags is the first With Selected entry, and in a row's Action menu, Delete (or Archive) and Restore come before Permanently Delete. A single item's Tags are edited on its edit page. What each list offers:

Entity Tags Custom Metadata Linked from Articles With Selected Row Action menu Permanently Delete Show in Mapify / Mermaid
Integrations, Systems, Services, Contracts, Message Types, Endpoints, Domains ✅ ✅ ✅ Manage Tags, Delete, Restore, Permanently Delete Delete, Restore, Permanently Delete Administrator, deleted items only Row and list
BPMs ✅ ✅ — Manage Tags Delete, Restore — Row and list
Mapify Maps (Saved Views) ✅ ✅ — Manage Tags Delete, Restore — —
Custom Metadata definitions ✅ — — Manage Tags Delete, Restore — Row and list
Articles, Snippets, Templates, Document Profiles ✅ ✅ — Manage Tags, Delete, Restore, Permanently Delete, Purge revisions, Apply Document Profile, Regenerate from BizTalk, Export, Compare Delete, Restore, Permanently Delete Modify, live or deleted; not shipped documents, or documents that live documents include Row and list
C4 Diagram Sets ✅ — — Manage Tags, Delete, Restore, Permanently Delete Delete, Restore, Permanently Delete Modify, live or deleted; not while the set holds diagrams Row and list
C4 Diagrams ✅ ✅ Nodes and boundaries Manage Tags, Delete, Permanently Delete Archive, Permanently Delete Modify, live or deleted Row and list, plus the diagram's own Mermaid view
Images, Files ✅ — — Manage Tags, Archive, Restore, Permanently Delete Archive, Restore, Permanently Delete Modify, live or archived Row
Tags — — — — Delete, Restore, Clear See Tags Row
Component Types — — — Delete, Restore, Permanently Delete Delete, Restore, Permanently Delete Administrator, deleted and unused only; built-in types are protected Row
Transport Contracts — — — No list of their own — — An icon on Contract rows and on a Log Event's Repository Model tab

✅ available, — not available. Images and Files say Archive and Archived where other lists say Delete and Deleted, including the Include archived filter.

Repository management pages

Repository Management

CMDB Attributes

Managed elsewhere

Next Steps

Manage Endpoints
Permission Set for the Repository Model

Administration
Repository Model
Repository Overview - Find and view Repository entities
Show deleted records