Every action has a rule, a record and you behind it.

Opsidian AI employees work inside permissions you set. Anything unusual waits for a person, and everything they do is written down.

  • Scoped to each role
  • Approval for exceptions
  • Full audit trail
  • Encrypted in transit and at rest
How it’s built

Four rules that never bend.

These hold for every employee, on every plan, at every stage of rollout.

Scoped to the role.

Each employee can only reach what its job needs. Access is declared up front, never inherited or assumed.

Unsure means stop.

When a request falls outside the rules, the employee holds it and brings in a person. It never improvises a price, a date or a promise.

Everything on the record.

Every call, message and action is logged in order, with the rule it followed and who approved anything that was held.

Rules are versioned.

Every change gets a version with a timestamp and an author. Past calls keep the rules they ran under, so nothing is rewritten after the fact.

Permissions

Every capability, declared per employee.

A capability is granted, held for your approval, or withheld. Switch the stage to see how access widens only as you allow it.

Capabilities for each AI employee at the selected rollout stage
Capability Forge Ivy Axel
{{ r.cap }} {{ r.f.text }} {{ r.i.text }} {{ r.a.text }}
{{ r.cap }} Forge{{ r.f.text }} Ivy{{ r.i.text }} Axel{{ r.a.text }}
Granted: runs inside your rules Approval: held for a person Withheld: never available

Default posture shown. Your permissions are written with you during the pilot and versioned from then on.

Audit trail

Replay any call, decision by decision.

What was decided, against which rule, and who approved it. If a customer rings back three weeks later, the whole chain is still there.

  • Recording and transcript attached to the job
  • The rules version in force at that moment
  • Who approved anything that was held
  • Anything it couldn’t confirm, flagged instead of guessed
job #4471 · forge · rules v12 Complete
  1. {{ e.t }} {{ e.what }}{{ e.tag }} {{ e.why }}
Illustrative record · sample job
Your data

Handled like it belongs to you. Because it does.

Your customers trust you with their details. Here’s how we protect that trust.

{{ d.title }}{{ d.body }}
Straight talk

No badges we haven’t earned.

You won’t find certification logos here that we don’t hold. Data handling, retention and residency are documented for each deployment, and if you ask about a specific framework, we answer plainly, including when something isn’t in place yet.

Need it in writing?

Send us your security questions.

Questionnaires, data handling details or a specific requirement. We’ll answer what applies to your deployment.

Ask our team
Common questions

What owners ask before they say yes.

Can an AI employee do something I haven’t approved?

No. Every capability is granted, held for approval, or withheld, per employee. Anything outside the rules is held for a person instead of acted on.

Will the AI take payment details over the phone?

No. Taking payment details is withheld from every employee at every stage.

Can I see everything my AI employee did?

Yes. Every call, message and action is recorded in order, with the rule it followed and who approved anything that was held.

Watch it work in shadow mode first.

Every pilot starts with the employee drafting, not speaking. You read everything before a single customer hears it.