Where your data lives
Fieldwork runs on AWS. Application data lives in encrypted managed PostgreSQL; files and datasets in encrypted S3 storage. All traffic is TLS in transit. Production infrastructure is isolated in its own AWS account with private networking — databases and workloads are not reachable from the internet.Organization isolation
Your organization is the trust boundary. Conversations, connectors, files, tables, the knowledge base, automations, and skills are all organization-scoped, with per-asset access controls on top. Data reads are authorized against live access-control state at the moment of access — revoking access takes effect immediately. Shared conversations never widen access: a teammate’s turns in your conversation run under their identity and permissions, not yours.The workspace sandbox
The agent’s code execution happens in isolated, per-conversation containers, provisioned fresh and torn down after use. Workspaces reach your organization’s data only through brokered, authorized channels — there is no standing credential inside the sandbox.Credentials and connectors
- Connector authorizations use each provider’s OAuth flow; Fieldwork holds only the scopes you approved
- Stored tokens are encrypted at rest
- Secrets are entered through write-only forms — they never transit chat, and the agent can never read them back
- Connector actions run under the connected account’s real permissions; approval cards gate anything that changes external systems