Fields to protect
Employee records, contracts and business secrets. This scenario covers fields extracted and registered from documents. Source files remain in the enterprise document system.
NSECURED MemberGo / Enterprise AI agents
An internal AI agent may connect to procurement, document and HR systems. Each workload can request access under its own service identity and receive only the structured fields approved for its task.

Enterprise AI agents
Employee records, contracts and business secrets. This scenario covers fields extracted and registered from documents. Source files remain in the enterprise document system.
A procurement agent may be approved for custom fields such as expiry date, renewal notice period and clause category.
Synthetic data example
renewal_remindercontract.expiry_date contract.notice_days200 · access_id: demo_52daThe procurement agent requests the expiry date and notice period for a renewal reminder and uses them to calculate the notification date.
renewal_remindercontract.expiry_date hr.salary ×403 data_access_deniedIf the same agent adds an unapproved salary field to a reminder request, the entire request is denied, even if the document system can locate its token.
The fields and decisions here are illustrative. Actual access depends on tenant settings, the basis for processing and the approved purpose.
Workflow
Procurement selects one renewal workflow and identifies the contract fields needed to calculate a reminder date.
Bind the renewal purpose and permitted contract fields to the workload, and exclude payroll from that purpose.
The valid reminder uses approved values in memory. Adding a restricted field stops the job; the agent cannot generate a reminder from an empty result.
Proof of concept
Have procurement and the AI platform team prepare synthetic terms, an expiry date and a fictional salary field. Demonstrate one approved reminder and one request that must stop.