Working with Your Organization's Files

Giving agents access to your organization's file systems — delegated access, not sovereign encryption

Bob's SharePoint Story

Bob sets up HUMΛN Cloud for Acme Corp. He connects SharePoint via the Marketplace. An agent is now able to list, read, and search Acme's contract library. The agent's delegation token includes connector:sharepoint:read — it can reach into SharePoint and read documents. Meanwhile, Bob's certification from his last job lives in his personal vault. The agent never touches it. SharePoint documents belong to the org; Bob's certification belongs to Bob. HUMΛN knows the difference because the resource policy says so.

Two Kinds of Storage

HUMΛN distinguishes between Vault (you hold the key, sovereign data) and Connected Storage (external service, delegated access). Same agent, different trust models.

Aspect	Vault	Connected Storage
Who holds the key?	You	External service (OAuth)
Can HUMΛN read?	No	Yes (with delegation)
Typical use	Health records, certifications, identity	Contracts, org docs, SharePoint, Drive
Resource policy	`default_store: "vault"`	`default_store: "sharepoint"`

Installing a Storage Connector

Install the Google Drive or SharePoint connector from the Marketplace. The flow: browse Marketplace → select connector → Install → OAuth flow (or API key for some connectors). After installation, the org's resource policy includes the connector, and agents can request delegated access when they need to read or write files.

What Agents Can Reach

Delegation anatomy: the agent's JWT includes connector:sharepoint:read. That scope is granted when the org admin installs the connector and delegates to the agent. The agent uses ctx.muscles or connector invocation to read a contract from SharePoint.

typescript

// Agent reads a contract from SharePoint (delegated access)
// The agent's JWT includes connector:sharepoint:read
const contract = await ctx.connectors.invoke('sharepoint', 'files:read', {
  path: '/Contracts/2026/Q1-agreement.pdf',
  org_did: ctx.orgDid,
});

The Boundary in Practice

Bob's certification scenario: the org's resource policy maps core.drive.file to default_store: "sharepoint". Bob's personal vault maps health.* and identity.* to default_store: "vault". Why these are separate namespaces — and why that matters when the org is acquired or Bob changes jobs. His certification stays in his vault. Acme's contracts stay in SharePoint.

Consumer Storage: One Service, Two Roles

Google Drive can play two roles: (1) Vault backend — encrypted blobs, user holds the key, HUMΛN never sees plaintext. (2) Connected Storage — org files, OAuth, HUMΛN reads them with delegation. Same service, different resource policy, completely different trust model. The decision is made by the resource policy — not by the connector type alone.

Connector Delegation Reference

Scope	Meaning
`connector:{id}:read`	Read files, list resources
`connector:{id}:write`	Create, update, delete
`connector:{id}:admin`	Full configuration

Grant scopes via the org's delegation policy or when installing a connector. Revoke by updating the delegation or uninstalling the connector.

Next Steps

For personal sovereign data like certifications and medical records, see Your Data, Your Key.

Your Data, Your Key