Tool Boundaries & Integrations

Niyatna can connect to company tools, but an integration is never hidden authority.

Every tool path is scoped by the active request, the role boundary, the action class, and the evidence required.

---

Integration types

• Workspace access: Read or write only the approved files, records, or folders needed for a request.
• Company systems: Connect to approved business tools under role and workflow boundaries.
• Communication channels: Send status, review requests, and final reports to the right channel.
• Scheduling systems: Create reminders, follow-ups, or recurring work within allowed scopes.
• Evidence capture: Store screenshots, source notes, reports, task records, or receipts as proof.

What an integration reports

Every tool action should return a clear record of:

• the request it served;
• the surface it acted on;
• the action it performed;
• the status it reached;
• the evidence it produced;
• whether review is required before the result is final.

Rule

If a tool cannot explain what it touched, why it touched it, and what evidence it produced, it should not be part of a Niyatna workflow.