# Use Operational Intelligence safely

Operational Intelligence shows current branch metrics, anomalies, recommendations, and preview-only action posture; acknowledgement records review but recommendations do not silently execute changes. Open Intelligence, review health, risk, momentum, anomalies, and recommendation evidence, and acknowledge an anomaly when reviewed. Review the evidence and scope behind every recommendation; acknowledgement or a suggestion does not execute a business change.

Canonical URL: https://admin.tajergo.ae/help/articles/pos/intelligence/
Article ID: pos-intelligence
Surface: POS
Category: Insights
Last reviewed: 2026-09-06

## Before you start

- An authenticated POS session assigned to the intended branch.
- The intelligence page has received current branch data and the selected date context.

## Steps

1. Open Intelligence.
2. Review health, risk, momentum, anomalies, and recommendation evidence.
3. Acknowledge an anomaly when reviewed.
4. Use preview-only actions to inspect the proposed response.
5. Open Orders for related operational history.

## Expected result

The selected branch insight appears with its supporting evidence and a link to the relevant operational context. Treat an insight as decision support and verify its underlying operational records before acting.

## Permissions

- The user needs pos.read or intelligence.read for the active branch; displayed recommendations do not grant permission to change operational records.

## Troubleshooting

### When staff open Intelligence, POS blocks progress before they can review health, risk, momentum, anomalies, and recommendation evidence.

First confirm the following access and record state: An authenticated POS session assigned to the intended branch. The intelligence page has received current branch data and the selected date context. Reopen /intelligence once and read the exact validation or configuration message. If the control remains unavailable, stop and give Support the insight, branch, period, metric, visible error, and time. Keep evidence of the result when staff open Intelligence.

### The branch, period, metric, and source records do not agree after the final checkpoint: Open Orders for related operational history.

Compare the visible insight scope with the named order, shift, inventory, or customer source records. Refresh the same scope once; do not act on a financial or stock insight whose source scope is unclear. Do not repeat the action if the records conflict; ask Support to review the insight, branch, period, metric, visible error, and time. Before another attempt, establish whether staff could open Orders for related operational history.