THEO acts inside the rules you set.
Safety and control is the control model for THEO in The One Stack, the platform MSPs run their whole business on. It sets what THEO runs on its own, what it asks about and what always waits for a person, for the buyer who signs off on AI touching client systems. The settings are yours, per runbook and per client.
What THEO runs on its own
THEO acts through runbooks. It runs one on its own only when every condition below holds.
A runbook you have switched on
A runbook you have switched off does not run. A request no runbook covers goes to a technician.
At the level you set
Each runbook sits on the ladder: watch, suggest, assist or autopilot. On assist THEO runs the fix when it is confident, and on autopilot it runs the fix and reports what it did.
For a client you have opted in
Each client is opted in by you, at a level of its own. A client can be excluded, and then nothing runs for them.
For a person THEO has verified
Before a runbook changes anything for the person asking, THEO checks who they are, to the level that runbook requires.
Inside your limits
You cap how many devices a single run may change and how many changes may run in an hour.
Until you pause it
An admin can pause every automation for your organization with a single control.
What always waits for a person
Some actions are not automatic at any level. The list is fixed in the platform and has no setting.
THEO runs on its own
- Runbooks you have switched on.
- On assist, when THEO is confident.
- On autopilot, with a report of what it did.
- For the clients you have opted in.
- For example: clearing a stuck print queue, or cleaning up a full disk.
Always waits for a person
- Isolating a device, or releasing one from isolation.
- Changing a user’s account.
- Disabling or suspending a user.
- Rolling back a change, a failover or a host change.
- Anything a THEO Bot would send or change in a client’s own systems. The person signed in confirms it.
Audit
Every run is recorded step by step, whether THEO or a technician started it.
The run
The record holds the request, the runbook, each step and its result, and how the run ended.
The decisions before it
It also holds how the person was verified, which policy checks ran, and which setting allowed the action or held it.
The approval
When an action waits for a person, the record shows who approved it or declined it.
A chain you can check
Audit entries are linked in sequence. An admin can run a check that the chain is intact.
Who can read it
Technicians, admins and owners read the trace of a run. The audit chain is for admins and owners.
Boundaries
Where THEO may work is decided before what it may do.
Your organization
THEO works on your organization’s record. The platform binds each request to your organization, and nothing a caller types can change that.
One company at a time
For a client, THEO answers from that client’s own company. A request that cannot be tied to a company is refused.
Per-client opt-in
Nothing runs for a client until you opt them in. A contact can be set narrower than their company, never wider.
Per-audience limits
A managed client’s user, a co-managed IT person and your own technician each get a different list of what they can ask THEO to do. A runbook nobody has classified is staff-only.
No emergency calls
THEO does not place emergency calls. Emergency calls are for people and handsets.
Data
Training on interaction data is governed by a consent setting for your organization. An owner or admin changes it in settings.
The setting decides whether your organization’s interactions with THEO are collected for training.
What is collected and how it is handled is set out in the policy in the Help Center. This page does not restate it.
Questions
Questions MSPs ask
What does THEO run without approval?
THEO runs the runbooks you have switched on, at the level you set, for the clients you have opted in. On autopilot it runs the fix and reports what it did, and on assist it runs the fix when it is confident.
What always needs a person?
Isolating a device, changing a user’s account and disabling a user always wait for a person, whatever level a runbook is on. Anything a THEO Bot would send or change in a client’s own systems is confirmed by the person signed in.
Can I stop THEO from acting?
Yes. You can switch a runbook off, exclude a client, or have an admin pause every automation for your organization.
Is everything THEO does recorded?
Yes. Every run is recorded step by step, with the request, the checks made before it, each step’s result and any approval. Admins and owners can read the audit chain and check that it is intact.
Is our data used to train THEO?
Training on interaction data is governed by a consent setting that an owner or admin of your organization controls. The policy in the Help Center sets out what the setting covers.
Related
Keep going
Start
Run on One.
Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.