Skip to main content

See it in action

Connect to approved systems.

See Entellex use scoped source-system operations only and keep denied scope visibly out of reach.

What to look for

Watch for the approved lookup, the fields it may use, and the denied scope that stays out of reach.

RequestThe request enters the operation.

The walkthrough starts from the user request before controlled execution begins.

Review artifactApproved lookup across source systems

Approved lookup: ecommerce stock, WMS stock, POS sales. Result: source-backed mismatch. Writeback: none in this recording.

Controlled step
Approved system lookup
Outcome
Entellex used approved inventory lookups to compare system state and explain the cancellation pattern without taking an unapproved write action.
/

What just happened

Approved source-system lookup stays bounded.

The operation needs source-system evidence, so it uses one approved operation instead of broad system access. The lookup returns only the fields allowed for the task, while denied fields and write actions remain outside scope.

The control shown is the access contract. The review record preserves the source, returned result, allowed fields, and denied scope, making the system interaction inspectable without granting AI general permission to explore or change records.

First operation

Map approved system access for one operation.

Bring the source system, the approved operation, the allowed fields, and the denied scope.