Mitra
The briefing widget everyone sees, and the operations engine administrators configure.

What Mitra is
Mitra is BlueOneHR's HR companion. It has two distinct parts, and it is worth keeping them separate:
a briefing surface everyone sees on the dashboard, and an operations engine an administrator
configures separately.
What Mitra shows you, and what it never does on its own
Mitra is not a general chat assistant. It does not hold open-ended conversations, and what it
says is generated from your organisation's own data — payroll figures, compliance obligations,
attendance records — not from outside knowledge. Where it speaks, the product discloses that it is
doing so.
The briefing widget
On the Control Center dashboard, Mitra offers a short spoken-style briefing computed from what has
changed since you last looked: what is still open, what has not changed, and a recommended priority
if one exists. You choose Quick summary for the short version or Walk me through everything
for more detail, or dismiss it with Not now.
The capture above shows the Executive Brief panel embedded in the Control Center dashboard, rather
than the separate pop-up dialog ("Quick summary / Walk me through everything / Not now") described
above. Both are real surfaces for the same underlying briefing. The pop-up only opens when there is
something to say, and how often it opens is your own setting: in Mitra's Briefing settings, Open
with a briefing can be Every time I open the Control Center, Only when something has changed
or Never. The panel also has an Ask Mitra about your Control Center box, which its own footer
describes as reading only what your permissions allow and explaining rather than acting (its
behaviour was not tested for this page).
What the Executive Brief label means
The badge on the panel says one of two things, and the difference is only in the wording:
Computed from your data is the default. It means every line in the panel was computed directly
from your records. This is what the demo workspace showed.
AI phrased · facts computed, followed by a time, replaces it, and an AI summary paragraph
appears above the fact list, only when two things are both true: the workspace has the AI Insights
feature switched on, and the optional phrasing layer answers with wording in which every number
matches the computed facts. If the feature is off, the phrasing layer cannot be reached, it takes too
long, it returns nothing, or a number in its wording does not match, the panel simply stays as it
was and keeps the Computed from your data badge.
Either way, the fact list and the Recommended priority list underneath are computed, never
generated, and are the same. The phrasing layer can only re-word them. If your panel carries the
Computed from your data badge and no AI summary, nothing is missing.
Every figure Mitra states is computed from your own records — the same numbers you would find by
opening the underlying module yourself. Where a number cannot be verified or a data source is stale,
the briefing says so rather than presenting a guess as fact.
Autonomous Operations
Separately, Settings → Mitra → Autonomous Operations configures a governed detect → recommend
→ execute pipeline that watches defined business areas ("scopes") for situations worth attention,
and can act on a narrow, explicitly approved set of them.
The pipeline has three stages, shown on the page itself:
Detection — Mitra watches a set of scopes for defined situations.
Recommendation — a detected situation is raised for human review.
Execution — for the narrower set of scopes and policies where autonomous action is switched
on, Mitra can act directly, always landing the result somewhere a human can see it (a Help Desk
ticket, in the current implementation).
Operational controls on this page let an administrator turn autonomous execution on or off,
pause operations for a set period, and stop detection entirely. Execution can only act on what
detection has found — turning on execution for a scope where detection is off changes nothing,
which is deliberately how the page describes its own dependency.
This capture shows autonomous execution ON for the demo workspace. The counters on the screen
(detected today, cases raised, escalations, open situations, minutes since the last run) change with
every scan, so treat the numbers in the capture as a moment in time, not as anything to expect on your
own workspace. The product ships with autonomous execution off by default, as the next section
explains: this screen reflects an already-configured demo, not the factory default.
What "autonomous execution" defaults to
BlueOneHR ships with autonomous execution off. An administrator turns it on deliberately, scope
by scope, through Policies. What was observed live on a demo workspace (execution on, watching 9
scopes, acting in 2) reflects a configuration choice made on that workspace, not the product's
default state — check Operational Controls on your own workspace rather than assuming either
setting.
Other tabs on this page
Alongside Autonomous Operations: Policies (which situations Mitra watches for, and which of them
it may act on), Activity (a log of what it has detected and done), Action Review (decisions
waiting on a human), Simulation (Run simulation, to see what Mitra would do without it
actually happening), Engine, and Audit. Each tab is described in Mitra administrator settings.
Before you turn autonomous execution on
Everything below is what the Autonomous Operations page itself says, as read on the demo workspace
signed in as an HR Head. It is a checklist for a person deciding, not a guarantee about what
Mitra will do on your data.
Check that detection is on for the scope. The page says: "Execution can only act on what
detection has found. A scope with execution on and detection off changes nothing."
Run a simulation first. Run simulation is described as running "every check and every
decision against real data" while changing nothing. Read what it would have done before you allow
it to do anything.
Read the list of autonomous actions. The page groups them as case management (open a Help Desk
ticket, choose its type, priority and owner, attach evidence, add a note), communication and
follow-up (notify the owner, follow up, escalate) and resolution (verify that a situation is gone,
and close the ticket it raised). It says: "An action that is off is never performed, even when an
enabled policy asks for it." Switch off any action you are not ready for.
Know where the result lands. The page says the actions Mitra takes "always land in the Help
Desk", as a real ticket a person can see. Check Default Help Desk ticket type and Fallback
owner group; on the demo both read Not configured. Without a fallback owner group,
situations with no valid owner are recommended for human review instead of being assigned.
Set a ceiling. Maximum autonomous actions per run limits how much Mitra may change in one
run. Anything beyond it is "recorded as skipped, never silently dropped".
Know the brakes before you need them. Turn execution off, Stop detecting, and
Pause operations (1 hour, 4 hours, until the end of the day, or until manually resumed) are all
on the same page.
Enable it scope by scope, not all at once. Each scope card has its own Detection,
Recommendation and Execution setting. On the demo, 9 scopes were being watched and 2
(Assets and Help Desk) were allowed to act.
Look afterwards. Activity shows every detection, decision, action and outcome with the
evidence behind it, and Audit shows "who changed which switch, and everything Mitra did, in one
trail". Saved changes on this page are recorded in the audit trail.
Mitra reads what your records contain. If a source is stale, the briefing says so (for example, the
demo Control Center says "No attendance recorded" and labels it as missing data, not absence), so fix
stale data before relying on what Mitra finds from it.
Related
Mitra administrator settings
The Control Center dashboard
How attendance works
How payroll works

Mitra administrator settings
Settings → Mitra is where an administrator sees and controls Mitra's autonomous operations. It has seven tabs. This page says what each one shows, so you can find the right one and read it correctly. What Mitra is explains the idea; this page is the map of the screens.
Mitra here is a rule engine that watches your records and raises Help Desk cases. It is not a chat assistant and it does not hold conversations.
Mitra Operations: where an administrator sets the rules (a tour)
Before you start
Mitra must be switched on for your subscription. If it is not, opening the page says "Mitra is not enabled for this subscription."
Seeing the tabs needs the permission to view Mitra's autonomous operations. Changing anything needs further permissions, and they are granted to a group by an explicit administrator command, not by an upgrade. In the test workspace used for this page, HR Head could see and configure everything below; HR Ops could see the tabs and change scopes and actions but not the master switch or the policies; and the Manager user group had none of these permissions.
Do not use the buttons described here on a real workspace just to see what happens. Some of them make Mitra act.
The seven tabs
They share one tab row under Settings → MITRA: Autonomous Operations, Policies, Activity, Action Review, Simulation, Engine, Audit.
Autonomous Operations
The control page. It answers "what is Mitra allowed to do here?". The top shows a status line such as "Mitra is watching 9 scopes and may act in 1 of them", then three stages in order: Detection, Recommendation, Execution.
Operational controls: Autonomous execution with Turn execution off, Pause operations (1 hour, 4 hours, until end of day, until manually resumed) and Detection with Stop detecting. Beside them are today's counters: detected today, cases raised, escalations, open situations, minutes since the last run.
Operational scopes: nine cards (Assets, Attendance, Compliance, Employee Records, Help Desk, Leave, Offboarding, Onboarding, Payroll). Each has its own Detection, Recommendation and Execution switches, the number of policies in it, and its open situations.
Autonomous actions: eleven actions grouped as Case management, Communication and follow-up and Resolution. The page states: "An action that is off is never performed, even when an enabled policy asks for it."
Defaults and safety limits: Default Help Desk ticket type, Fallback owner group and Maximum autonomous actions per run, with Save settings.
Explore Mitra: links to Activity, Simulation, Engine and Audit.
See What Mitra is for the checklist to read before turning execution on.
Policies
The list of the situations Mitra watches for. The workspace used for this page had 24, grouped by scope. Each row gives the policy name and version, its Condition in words, its Severity, the Permitted actions, how many Situations it has found, and its State (Enabled, or Not evaluated).
A policy that looks for something being absent will not run while the data it depends on is stale. For example, the policy for a missing attendance record on a working day shows Not evaluated when the data is stale, with the reason: the newest attendance record is older than "the 3 days this policy needs", and missing punches could not be told apart from a feed that had stopped, so nothing was reported. That is the intended behaviour.
Opening a policy shows its condition, severity, whether it raises new cases, its version and who saved it, the actions that would run right now and the ones asked for but blocked (with the reason, for example "This action is switched off"), and then the settings that can be changed: thresholds, follow-up and escalation timing, severity, whether a person must always approve, and who owns the cases it raises. Each change is versioned and asks for a reason. Editing a policy needs the policy-editing permission.
Activity
Every situation Mitra has detected, newest first, with its severity, the policy that found it, who it concerns, how many times it has been seen, its status and the case raised. The filters are Scope, Policy, Status (Detected, Recommended, Acted, Skipped, Resolved, Failed), Action, employee and Seen since. Opening an entry shows the evidence captured at the time and the version of the policy that was in force. It is assembled from stored records and is not recomputed when you open it.
Action Review
Actions Mitra has proposed and is waiting for a person to approve or refuse. The page states the rule: "Mitra proposes; a human decides; the approved action then runs as that human." It has status filters (Open, Proposed, Awaiting approval, Executed, Refused, Failed). When there is nothing to decide it reads "Nothing to review". A person who belongs to a company's Mitra approvers group can see this tab even without the wider permission; it grants sight only.
Simulation
Runs every check and every decision against today's data and changes nothing. You tick the policies to test, or leave all unticked to test every enabled policy, and select Run simulation. The page says: "No ticket is raised, no owner is assigned and no case is closed." The result lists what would be created, escalated and assigned, and to whom. Read it before you allow Mitra to do anything. A simulation was not run while writing this page.
Engine
Whether the scheduled scan is really running. It says it reads the platform's own scheduler, not the app's opinion of it. It shows the state (Running), the schedule (for example every 900 seconds), the last completed run and how long it took, the next run, when the scheduler last started it, the total scheduled runs and the open situations. Below is the Run history, real runs and simulations, each with its trigger, duration, number of policies, situations found, outcome counts (acted, recommended, no change, skipped, failed) and status. Run notes appear under a run, such as a policy that was not evaluated. Run now starts a real run and Simulate opens Simulation.
Audit
Every configuration change and every autonomous decision, with who made it, when, and what changed from and to. The filters are Everything, Configuration changes and What Mitra did. The page says entries are written as they happen and are never edited.
What you should see
Each tab opens on its own address under 
/mitra-operations/, marks itself in the tab row, and states in its subtitle what it is for. Counters and run times change with every scan, so treat any number, including the ones in the captures, as one moment in time.
If it does not work
You see "You do not have permission to manage Mitra's autonomous operations." You lack the view permission. Ask an administrator.
You can read a tab but its buttons do nothing or are missing. Viewing and changing are separate. Changing scopes, actions, policies and the master switch each need their own permission.
A policy says Not evaluated. That is the guard described under Policies, not a fault.
The Engine tab notes that some open detections could not be re-checked because the records they refer to no longer exist. They are left open on purpose.
Not confirmed
Toggling, saving or running anything was not tried live. In particular a simulation and Run now were not run.
The detail pages of an Activity entry and of an Action Review proposal were not tried.
Which other roles can see or change each tab, beyond what the sample user groups showed.
Related
What Mitra is
The Control Center dashboard
Help Desk