Legatus — Your Agent for Digital Workplace

Consider it done.

Sent to act with your authority — and never beyond it. Your people ask in their own words, and Legatus carries the request through to done — accounts, devices, access.

One deployment per customer, inside your own network. Every act is gated, and every act is written down.

Carrying one request from asked to done

Six steps, every time — whichever door the request came through, whatever sits behind it. You decide which of them the agent is allowed to take on its own, and where a person has the last word.

Step I

Ask

It meets the request where it was made. Nobody learns a new tool.

A message — answered in the same thread, where the conversation already is
A ticket — it arrives on its own; the reply is written back into the ticket
A desk — the operator's console, which is also where approvals happen
A portal — your own chat, behind your own sign-on

Microsoft TeamsServiceNowService deskWeb chat

Four front doors, one delegate

Teams

ServiceNow

Service desk

Web chat

Legatusyour delegate

Four doors shown. The agent comes to the channel; the channel never has to come to it.

Step II

Ground

It reads before it reasons. Your documentation, your systems — never a guess.

Your documentation — whatever you have written down, searched at the moment the question is asked
Your systems, live — who the person is, what they hold, what their device reports
Nothing invented — a name that matches two people is refused, not picked

Your documentationEntra IDIntuneActive Directory

What it reads first

Legatusread · reason · act

Grounded in

Your own documentation

What is true in your systems right now

ambiguous_match — two people answer to that name. The tool refuses and says both.

Step III

Propose

It works out the exact call. Arguments and all, before anything runs.

A named tool — each with a schema, not a loose intention
Resolved arguments — the account, the group, the licence, looked up and shown back
A draft reply — written for the person who has to read it

one named tool per actschema-checkednames resolved first

The proposal, in full

reset_user_password

user: marta.ilic@contoso.com
target: entra
force_change: true
channel: snow-INC0042318

Nothing has run. This is what it is asking to do.

Step IV

Gate

It knows where it has to stop. Enforced by the system, not requested of the agent.

A typed phrase — in chat, a destructive action waits for the exact words. There is no button to click by accident
An operator's token — on a ticket, a one-time approval bound to that tool and those arguments. The agent holds no key to mint one, even running autonomously
Credentials apart — a temporary password never enters the model's context, and never reaches the record

confirmation phraseone-time approvalredaction

Held until a person says so

Legatusproposes

Operator approves

The approval is bound to

tool: reset_user_password
args: sha256(…)
session: snow-INC0042318
expires: in 5 minutes

Signed with a key the portal and the tool server share — and nothing else does.

Step V

Act

It carries the change through, in the systems of record, in order.

Accounts — create, update, disable, delete; move them where they belong. In the cloud directory, on-premises, or both at once
Access — groups, licences, sessions, sign-in methods, temporary access
Devices and apps — sync, diagnose, unenroll, wipe; publish, package, assign, supersede

Entra IDIntuneActive DirectoryServiceNow

Where it acts

Legatusacting

Entra ID

Intune

On-prem Active Directory

ServiceNow work note

A change that takes time to settle is confirmed on the next sync, not assumed.

Step VI

Record

Every act, in writing. Append-only, written as it happens.

Who, where, what, what came back — and how long it took
The refusals too — a gate that held is an event worth keeping
Secrets masked first — argument names and free text both, before the line is written. The person and the account stay

one line per actappend-only90-day retention

The audit file, as written

09:41:07

reset_user_password · marta.ilic@… · ok · password [redacted]

10:17:44

delete_user · j.novak@… · refused · no operator approval

10:19:08

delete_user · j.novak@… · ok · approved by m.ilic

The second line and the third are five minutes and one person apart.

You decide how far it goes on its own

Three modes. Set one globally, or a different one for each queue — so one queue can run itself while the leaver queue waits for a person. Neither holds the other up. The reasoning never changes. Only what the agent is allowed to commit.

Request

Legatusacts

Entra · Intune · AD

Reply posted

autonomous

It acts, then reports

The agent investigates, runs the tools and posts the reply itself. Nothing waits on a person; the portal records the intake.

Best for high volume and small blast radius — password resets, licence assignment, device sync.

Request

Legatusproposes

Operator approves

Entra · Intune · AD

approve

It proposes, a person commits

It investigates read-only and proposes the exact calls. An operator approves them unedited, then reviews the reply and posts it separately — two decisions, neither implied by the other.

Best where the change is hard to undo, or where somebody has to be able to say they approved it.

Request

Legatusproposes

Operator steers

Entra · Intune · AD

collaborate

It proposes, and you can answer back

Everything approve mode does, plus a way to tell the agent what it is missing. The operator steers, the agent revises, and the loop runs until the proposal is right.

Best for messy, one-off work — the tickets where the first proposal is rarely the final one.

Don't trust. Check the logs.

Every act and every refusal is logged, one line at a time, as it happens. Not a report we send you — a live audit. The guardrails are in it too, which is the half that matters most.

One line per act: Who, where, what, what came back — and how long it took.
Append-only: Entries are added, never edited. A gate that held is an event worth keeping.
Secrets masked first: Before the line is written, not after. The person and the account stay.
On your own host: The file never leaves your network, and neither does the agent.

Time	Channel	Act	Outcome	Took
09:41:07	Teams	Reset a password	Done · password [redacted]	2.1s
09:52:30	ServiceNow	Added a person to a group	Done · reply posted	1.6s
10:05:12	Web chat	Assigned an app to a device group	Done	3.4s
10:17:44	ServiceNow	Deleted a user	Refused · no operator approval	0.4s
10:19:08	Service desk	Deleted a user	Done · approved by m.ilic	4m 12s
10:26:51	Teams	Reset a password	Refused · confirmation phrase wrong (2 of 5)	0.3s
10:34:02	ServiceNow	Created an account	Queued · confirms on next sync	2.8s

An illustrative extract. The entries are fictitious; the fields are not.

Bring us one of your own requests

A private briefing, shaped around the work your teams do every day. Pick a request type you handle a hundred times a month and we will walk it end to end — including the point where it would stop and ask you.