Skip to content
Contact salesStart free

Security overview

How Filepad handles authentication, access control, integration security, and data governance.

Filepad is built around the principle that agents should have exactly the access they need — no more — and that every change they make should be auditable. This page covers the security model at a product level.

Security principles

Least privilege by default

Access is granted deliberately. Agent Access keys are workspace-scoped and carry only the scopes they need. Users access only workspaces they've been invited to. Both follow the same principle: no ambient access.

Auditability as a first-class feature

Every key action — proposal created, accepted, rejected, key rotated, scope changed — is logged with attribution and timestamp. You always know what changed, when, and who authorized it.

User authentication

  • SSO via Microsoft Entra ID for enterprise environments
  • Role-based access within workspaces: viewer, editor, admin, owner
  • Workspace isolation — users only see workspaces they've been granted access to

Agent Access API security

External agents authenticate via OAuth 2.1 bearer tokens:

  • Per-workspace access — a key for workspace A cannot access workspace B
  • Scoped Agent Access — each connection is granted only the permissions it needs, such as events.write, signals:write, or notifications:read
  • Scope enforcement — every endpoint checks scopes before touching any data
  • Revoked access — return 401 uniformly with no information leakage about connection validity
  • Rate limiting — per-integration throttling on external requests, with a 429 response when a connection exceeds its window
  • Audit trail — key creation, rotation, revocation, scope changes, and requests are logged

The workspace agent UI itself uses normal Filepad session auth rather than integration keys; its thread/job http/routes live under /workspaces/:workspaceId/agent/....

Key lifecycle

Workspace admins can:

  • Create Agent Access keys with specific scopes
  • Rotate secrets without revoking (zero-downtime rotation)
  • Patch scopes to adjust permissions without re-issuing keys
  • Revoke keys immediately when access should end

Data handling

  • Filepad does not train its own models on your documents
  • Content processed by an AI provider (OpenAI or Google Cloud) during a run is subject to that provider's API terms, which currently exclude API data from model training — see our Privacy Policy for details
  • Workspace isolation is enforced at the application layer, not left as an afterthought
  • Agent Access secrets are encrypted at rest with AES-256-GCM

Next steps