Hiring a digital employee
This page shows how to hire a digital employee from a job role, what each step of the hire dialog asks, and which limits apply.
Who this is for: administrators and managers who hire digital employees.
You need: Edition: Business. See Editions.
Job roles
A job role is the blueprint for a hire. It holds the mission, the tools, the highest autonomy, a suggested budget and schedule, and the models the role works on. Open Workforce ▸ Job Roles to see them. This menu is for Workforce managers.
A job role gives no rights by itself. When you hire, the role is tied to a user account. That account's access rights are the limit of the employee.
Open a role to see these tabs: Mission, What it may do, Defaults for a hire and Cost and value. The form also shows the chat starter prompts and What success looks like.
What a role lets an employee do
- If the role has a Tool allowlist, the employee gets exactly those tools.
- If it has no list but names the models it Works on, the employee gets the tools for those models. It also gets a fixed set of basic tools: ask a question, check its own access, count, search, read and group records, and open a record. The basic read tools work on any model that the Runs as account may read.
- If it has neither, the employee gets every tool. An empty list is the widest setting, not the narrowest.
You can see the real list on the employee, under the tab What it may do.
Changing a role later
Most values are copied when you hire. Changing the role does not change employees you already hired. Three changes that make things stricter do reach them:
- Lowering Highest autonomy lowers the employee's setting too.
- Taking a certified model away removes it from the employees.
- Narrowing the Tool allowlist limits them at their next run.
Narrow hired employees writes a narrower tool list onto the agents of the employees at once. It only removes tools. It also stops queued work that needs a removed tool. Making a role wider never changes existing employees.
Who can hire
Everyone with MitDesk user rights can open Workforce ▸ Digital Employees and press Hire a digital employee. What you may choose depends on your role:
| Workforce manager | Other MitDesk user | |
|---|---|---|
| Runs as | Own account. A MitDesk administrator can choose any allowed account. | Own account only |
| Monthly budget | Any amount above 0 | Not more than the role suggests |
| Schedule | Any | Not more often than the role suggests |
| AI model | Only a model that the role allows (administrators: any model) | Only a model that the role allows |
| Starts working at once | Yes, by default | Not by default. The employee waits in Draft until you press Activate. |
| Number of employees | No limit | At most 3 working or paused employees that you supervise and that run as you. Administrators can change this number. |
An archived job role cannot be hired.
The hire dialog
The dialog has seven steps. Use Next and Back.
- Job. Choose the job role and give the employee a name. Or write in Describe the job what the employee should do, and press Draft a mission from this. MitDesk picks the nearest job role and writes a mission for you to edit. Nothing is created yet.
- Mission. Read the mission and change anything you do not agree with.
- Access. Choose Runs as. This is the most important choice. The dialog says: "Can see and do what name can. Nothing more." If the account is not yours, it warns you that everything the employee does is recorded under that account.
- Dial. Choose the Autonomy and the AI model. You cannot go above the role's highest autonomy. The dialog sets it back to the highest allowed value.
- Budget. Enter the monthly budget. It must be above 0.
- Schedule. Choose Every hour, Every four hours, Twice a day, Every day, Every week or Something else. Optionally set Only during a working-hours calendar.
- Confirm. Read the summary and the First-run preview. Then press Hire.
If you leave Start working now on, the employee starts at once. Otherwise it stays in Draft.
What you should see: the new employee under Workforce ▸ Digital Employees.
Accounts that cannot be used
- a portal user,
- an administrator,
- an account without MitDesk user rights.
Schedule and working hours
With a working-hours calendar, scheduled runs do not start outside its working times, on leave days or on public holidays. Run now and Assign a task ignore the calendar on purpose.
Before each scheduled run MitDesk checks the calendar, the budget, the account, the AI model and whether an earlier run is still going or waiting for you. If a check fails, the employee shows the reason and the time. If the same problem blocks three scheduled runs in a row, the employee pauses itself and tells its supervisor. Press Resume after you fix the problem.
Limits for one conversation
A hire also copies limits for a single conversation: how often it may wake itself (100 by default), how long it lives (168 hours if the role sets none), a cost limit (the role's limit, or else a monthly budget), and an optional token limit. When a limit is reached, the next run opens a new conversation. The employee keeps working.
Hiring in chat
You can ask the chat to hire for you. The employee is created in Draft and the hire waits for your approval in Decisions. Press Activate on the employee when you want it to start.
What happens after the hire
The employee gets its own agent, a schedule and a Supervisor, which is you. Open it under Workforce ▸ Digital Employees. Then see Supervising and Pause, hand over, retrain, fire.
If it does not work
If a digital employee does not run, or the monthly AI budget is reached, see Troubleshooting.