Supervising the workforce
This page shows where you watch your digital employees, how to read what they did, and how to teach them and give them more freedom.
Who this is for: supervisors of digital employees.
You need: Edition: Business. See Editions.
Cockpit: Staffing
Cockpit ▸ Staffing is the manager's view. It is for Workforce managers and MitDesk administrators. Each employee has a card with:
- the name, the job role, the state, and the account it Works as,
- the autonomy level,
- one line about what it is doing now,
- decisions waiting for you, runs today, and spending against the monthly budget.
Use the filters All, Waiting for you, Active, Needs attention and Paused. The six figures at the top show the workload and the spending of the month.
| State | Meaning |
|---|---|
| Active | It is switched on and follows its schedule. |
| Waiting for you | A decision must be taken before the work can go on. |
| Waiting for approval | The decision belongs to someone else. |
| Deferred | Jobs are queued and will run in turn. |
| Budget exhausted | The month's budget is used up. Scheduled runs are skipped. The card offers Raise budget. |
| Schedule off | The employee is active, but its schedule is missing or off. The card offers Fix schedule. |
| Last run failed | The last run ended with an error. |
| Paused | Scheduled work is off. The card offers Resume. |
| Draft | It was hired but not started yet. |
On each card, Open workspace opens the workspace of the employee. The … menu has Talk, Conversations, Audit log, the weekly review and Settings. Use Hire to hire a new employee.
Stop every agent pauses all employees of the company after you confirm. Use it in an emergency.
Cockpit: Digital staff
Cockpit ▸ Digital staff shows the employees grouped by department. It uses plain words: Active, Waiting for you, Budget exhausted, Needs attention, Paused. It shows no costs, so everyone who uses the cockpit can see it. A draft employee is listed too.
Departments
A department is a group of digital employees, for example Finance, Sales, Marketing & CRM, Purchasing, Operations, Projects, Customer Support and Office & Admin. These are not Odoo HR departments, because a digital employee is not a person. Each department belongs to a business area, and the cockpit shows its employees on that area's card.
Open Workforce ▸ Departments to see them. Choose the department of an employee on its form. An employee without a department is shown as unassigned. MitDesk does not guess.
The employee workspace
Open it with Open workspace from a card or from the Work tab of the employee. It has five parts.
- Work. The budget bar, what the employee achieved this week, and a list of all its runs, newest first. A run is one scheduled run, one task, one Run now or one conversation. Open a run to see its steps and what it changed. You can press Why? on a step to have the employee explain it. On a running run you can press Stop. On a finished one you can press Retry, Correct… or Save as check.
- How it works. The standing mission, and the lines that tell the employee how to work.
- Trust. What the employee did with each tool, and how freely it may use it.
- Checks. Runs you saved as a test.
- Conversation. Talk to the employee.
The workspace is for the account it runs as, its supervisor, the handover owner, and Workforce managers.
Teaching an employee
To change how an employee works, tell it in its conversation, for example "next time, skip customers with a payment plan". It proposes a short line of up to 300 characters. The line does nothing until the supervisor or a MitDesk administrator presses Accept. You can also choose Accept it in your own words or Discard. An employee can have up to 20 accepted lines. You can edit, reorder, deactivate and restore them. Each change keeps the old and new text.
On a finished run, Correct… sends a correction to the employee in the same way.
Letting an employee act without asking
The Trust part lists each tool the employee used in the last 30 days. It shows how often it ran, how many requests were approved or rejected, how many runs a person corrected, and how many failed.
When the record is good, the tool shows Let it do this without asking. MitDesk offers it only when all of this is true:
- the tool changes data, and it is not one that always needs a person (money, deleting, and so on),
- the employee's own autonomy allows acting alone,
- at least 5 decisions were made, none was rejected, and no run was corrected or failed,
- no administrator rule for this tool and account exists, and the company-wide view does not advise to keep asking.
Only the supervisor or a MitDesk administrator can apply it. If the employee has saved checks, MitDesk first replays them with Try it first. If it has none, you must confirm that you decide without that evidence.
MitDesk also works the other way. Every hour it looks at the last 5 uses of each tool that you released. If 40 % or more failed or were corrected, the tool goes back to asking, and the supervisor is told.
Checks and dry runs
On a run that went well, press Save as check. Say what you expect from it. A check keeps the starting instruction of that run and your expectation. An employee can have up to 20 checks.
Try it first replays up to 10 checks against a change, for example a new line, or a release of a tool. It writes nothing. Every change the employee wants to make is only recorded as a proposal. A judge compares the result with your expectation. A dry run uses the employee's budget.
Weekly reviews
Every week MitDesk writes one review for each active employee. A paused or fired employee gets one only if it spent money or had a conversation that week. The review is added to the employee and creates a to-do for the supervisor. Open Workforce ▸ Weekly Reviews.
A review shows the actions, the approvals, how many were approved or rejected, the overrides (rejections and dial changes), the errors, the cost and the estimated time saved. Its buttons are:
- Lower Dial. Sets a lower autonomy level. It never goes up.
- Edit SOP. Opens the skills of the job role.
- Open Flow. Opens the automations of this employee. It says so if the Automations module is missing.
- Acknowledge.
ROI Ledger
Workforce ▸ ROI Ledger is for MitDesk administrators. It shows, per job role and week, the actions, the approvals granted and rejected, the estimated time saved and the estimated value. Read the estimates as explained here.
Approval history
Workforce has no Approval Insights menu any more. The approval history of a tool is on its rule: open the rule in Configuration ▸ Rules ▸ Autonomy Rules to see how many approvals for that tool were approved or rejected in the last 30 days, and whether financial actions were among them. See Autonomy policies.
Starting an employee from an event
An employee can also start when something happens in Odoo, for example when a lead arrives. A Workforce manager or MitDesk administrator creates an Odoo automation rule with the action Run digital employee. An employee started this way follows the same state, schedule and budget rules. It never starts from its own changes, it runs once at a time for a record, and it starts at most 12 times an hour.
If it does not work
If a digital employee stops running, see Troubleshooting.