Tenantry / docs / optimization action review only

date: 2026-05-04

Optimization Action `review_only`

This page explains why the engine selects review_only and why that is intentional for safety.

When review_only is selected

review_only is selected whenever safe automation criteria are not met. Common triggers:

• Identity matches exclusion policy:
  • service-like identity,
  • shared/resource identity,
  • explicit operator exclusion rule.
• Candidate is forced review-only:
  • activityClass === unknown,
  • reason includes heuristic_only,
  • candidate confidence is low.
• Downgrade safety checks fail:
  • missing app report at tenant level,
  • missing per-user app evidence,
  • current assignment has disabled plans.
• Add-on checks fail:
  • unsupported automation for that add-on,
  • add-on evidence source unavailable,
  • evidence indicates active use.
• Report identity settings limit automation:
  • concealed report identities prevent user-level mapping,
  • report settings permission missing or unverifiable.

Why this action is selected

• It prevents risky automated reclaim in low-evidence conditions.
• It routes uncertain cases to human validation.
• It preserves service continuity when telemetry is incomplete.

Savings calculation

• No savings estimate is emitted for review_only.

Operator guidance

• Treat review_only as a triage queue.
• Validate usage and business criticality before making changes.