Security at Worknet

Last updated: 15 September 2026

This page describes how Worknet protects customer data: where it runs, who can sign in, how integrations are scoped, and how access is logged. It is written for the security and IT teams who review Worknet before or during deployment. For the full access-security overview, the SOC 2 Type II report or our policies, contact us using the details at the end of this page.

Hosting and tenant isolation

Worknet is a multi-tenant SaaS hosted on Amazon Web Services in the United States. Services run as containers on AWS ECS.
Every customer is a tenant with its own logically separate database in MongoDB Atlas and its own vector index. Each request, agent and tool call is scoped to one tenant from the moment it enters the platform.
Credentials, tokens and configuration are stored per tenant and encrypted per tenant.
Customers who need the platform inside their own network boundary can have Worknet deployed in their own AWS VPC.

Authentication and single sign-on

Admin access is by invitation only. Sign-in runs on Auth0, which supports Okta, Microsoft Entra ID and other identity providers as enterprise connections over SAML or OIDC. With SSO in place, the customer's own MFA, session and offboarding policies apply to every admin sign-in.
End users are identified by the channel they use: their Slack identity, their Salesforce session, or a token signed by the customer's own application for web and in-product experiences. Worknet never asks end users for a separate password.
Roles the customer defines, such as Sales or Support, come from the identity provider or the signed token and control which assistants and tools a user can reach.

Network and access controls

All traffic in and out of Worknet uses TLS.
Access to the content Worknet serves can be restricted to an IP allowlist the customer provides.
The web widget loads only on the domains the customer registers.
In Slack, the Worknet bot sees only the channels it is invited to. In Salesforce, a dedicated integration user sees only the objects and fields its permission set allows.

Integrations and least privilege

Worknet is a certified partner of Salesforce, Slack, HubSpot and Zendesk, and follows each platform's least-privilege model.

Salesforce. OAuth 2.0 through an app the customer creates and controls, with a dedicated integration user and a scoped permission set. Records are read on demand, only when an agent calls a tool the customer's admin configured. Nothing is bulk-synced. Write access is off unless the customer enables specific actions.
Slack. A bot identity with the minimum scopes for the chosen use. No admin scopes, user tokens or workspace-wide scopes. Customers can run their own custom Slack app if they prefer.
Agent tools. An agent can call only the APIs and MCP servers a customer admin has configured, under the credentials and scopes the customer granted.

Data protection

Encryption. TLS in transit; AWS and MongoDB Atlas encryption at rest.
Residency. Customer data is stored on AWS in the United States, and every sub-processor is US-based. See our sub-processor list.
Models. Conversations are answered through the enterprise APIs of OpenAI or Anthropic under zero-data-retention terms, and customers can bring their own provider key. Worknet never uses customer data to train models.
PII removal. Before imported records are indexed, a redaction layer masks emails, phone numbers, card and account numbers, national IDs, IP addresses, passwords and API keys. Page context captured for in-product guidance is redacted in the browser before it is sent, at a privacy level the customer sets.
Retention. Data stays in the customer's tenant for the life of the agreement and is deleted within 7 days of termination under our data-retention policy.

Logging, audit and monitoring

An audit log records every configuration change and every view of a stored credential, with who did it and when. Entries cannot be edited or deleted, and the log is visible to the customer's admins.
Every model call and tool call an agent makes is traced, so a customer admin can see exactly what an assistant read and did in any conversation.
Services are monitored around the clock with real-time alerting, intrusion detection and database health alerts.

Compliance

SOC 2 Type II. Worknet holds a SOC 2 Type II report covering the Security, Availability and Privacy trust services criteria, issued by an independent auditor. The report is available under NDA.
GDPR. Worknet is GDPR compliant and processes personal data as a processor on the customer's behalf under our Data Processing Addendum.
Testing. Quarterly third-party vulnerability scans and an annual penetration test of the production environment.
Incident response. Security incidents are handled under our incident-response policy, which commits to informing affected customers.

Documents available on request

Full access-security overview
SOC 2 Type II report (under NDA)
Incident-response and data-retention policies
Penetration-test summary

Contact

For security questions, documents or to request an IP allowlist or SSO connection, email info@worknet.ai.