Box
Box files and folders attach to Strkr accounts and deals with Box governance intact. Audit logs, retention, and legal-hold policies stay enforced on the Box side; Strkr only shows what the viewer has rights to see.
Everything Box does inside Strkr.
- Attach Box files and folders to records
- Governance, retention, and legal hold preserved
- Enterprise single sign-on compatible
- Workspace-level connect
Native code, not a shim.
OAuth where available
Box will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Box once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Box from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Box is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Box is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.