Configuration and ranking

Classifications are ranked rather than independent, and the ranking is load-bearing: approval granted at a higher level is inherited by every level below it, but never upward. That’s what lets you approve a model once instead of in every class.

Why order matters

The platform reads your classification list from top to bottom to understand which level is highest and which is lowest. Getting the order wrong doesn’t just look confusing — it changes what actually inherits from what.

The inheritance rule

If a model or tool is approved for a high classification — Confidential, say — it automatically becomes available at every classification below it too. The reverse doesn’t hold: something approved only at Open never becomes available at Confidential just because Confidential sits above it.

Ordering your classifications

Name and order your classifications from lowest security at the bottom to highest at the top — for example, Open, then Sensitive, then Confidential, read top to bottom as highest to lowest. Reorder them by dragging in the administration view; Intric handles the inheritance logic for you once the order is correct.

What happens if the order is wrong

Important

If your classifications are ordered incorrectly, inheritance flows the wrong way — a model you meant to restrict to your highest classification could end up available everywhere, or a model approved broadly could appear to be missing at the level where you actually need it. Check the order carefully after creating or rearranging classifications, not only when you first set them up.