What it decides

Rule
SPO-LIST-001
Applies to
sharepoint · list
Default severity
medium
Basis
documented-limit

On what authority

The limit is enforced by the product, not recommended by it. The second source states the consequence that makes it worth reporting: a container that exceeds the limit and is not already uniquely shared "can't be uniquely shared later".

What it needs to decide

  • items.count
  • permissions.inheritance_broken

Without these facts the rule answers unknown, which is not a pass and is not a failure: it is the rule saying the evidence could not settle the question.

Where the evidence comes from

  • permissions: every visible list on a site, and its inheritance · live-validated

What a pass does not establish

A list holding 99,000 items and growing passes this rule today and loses the ability permanently within weeks, without anything in the report changing to warn about it. The rule measures a position, not a trajectory, and the boundary it describes is the one place where being close to a limit matters more than being past it: once crossed, the option does not come back. Every pass here means "not yet", never "safe".

  • The rule does not establish whether unique permissions will ever be wanted on this list, which is a business question and the only one that decides whether the finding matters.
  • Individual items inside the container can still have inheritance broken, up to the separate limit on unique permissions. This rule says nothing about that limit.
  • A container reported as not-applicable is only outside this rule. It may have crossed the same limit for reinheritance, which this rule does not check.

Source

The rule as the Engine holds it, at the revision this page was generated from: 1.0.0b6@b4bf9c325233.

Generated from capability-manifest/1.0.0 at1.0.0b6@b4bf9c325233, contract1.0.0b6. Every fact on this page is the Engine's; this site publishes it and does not maintain it.