M3CloudSlam
← Insights

Master data·12 October 2026·3 min read

Three levels of master data governance for Infor M3

Master data governance often fails in one of two ways: so light that nobody notices changes, or so strict that every change waits for a committee. The way out is to choose a level of control per field, based on what the field does.

Level 1: follow

Every change is recorded with its old and new value, who changed it and when. Nobody has to approve anything. This is the right level for most fields: it gives full visibility at no extra cost, and answers the question "who changed this?" when it comes up.

Level 2: follow and approve afterwards

Changes made in M3 are signed off afterwards by the person responsible. M3 is never blocked: the change takes effect immediately, and the approval confirms it or flags it for follow-up. This suits important fields where a wrong value hurts, but where waiting for an approval would hold up the business.

Level 3: change only through an agreed route

For the few critical fields, changes are proposed with a reason, approved first, and only then written to M3. Any change that still happens another way, directly in M3, is flagged as a violation and stays in the history.

Level 3 needs a closed side door

A governance tool can flag changes made around the agreed route, but it shouldn't revert or lock M3. To make the agreed route the only route, restrict direct maintenance of those fields in M3 itself.

Choosing a level per field

FieldExample levelWhy
Customer name, phone numberLevel 1Descriptive: visible to people, no effect on M3's behaviour
Delivery termsLevel 2Steers delivery, so changes should be seen and signed off
Credit limitLevel 3Critical: changed only through a proposal with a reason

A practical model is one default level per table, with a short list of field exceptions. Customers can be followed as a whole, while delivery terms are signed off and the credit limit is changed only through the agreed route.

Start light, tighten where it pays off

  1. 1Follow: put key master data tables on level 1. Every change becomes visible.
  2. 2Sign off: move the fields that matter to level 2.
  3. 3Agreed route: put the critical fields on level 3.
  4. 4Close the side door: restrict direct maintenance of level 3 fields in M3.

Each step is useful on its own. Most companies get most of the value from the first two steps, and need level 3 for only a handful of fields.

How M3CloudSlam helpsData Governance →See how the three levels work in M3CloudSlam, step by step.

Be among the first to ask your M3 anything

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows