Introduction
Sana is built with a "Security First" architecture, ensuring enterprise-grade protection for all customer data. Sana protects your organization's data through:
SSO authentication and user provisioning
Data isolation
Advanced encryption methods at both transit and rest
No LLM model training
Permissions mirroring your native platforms
Secure data handling and storage practices
Least privilege principle
Whether you are interacting with Workday data or connecting to third-party apps, your information remains private, secure, and under your control.
Authentication and user provisioning
All access to Sana is authenticated through Workday:
Single Sign-On (SSO): Sana uses Workday SSO as the sole authentication path. Users can open Sana from Workday and land in the app without an extra login, or go directly to the Sana URL and be routed through the same SSO for their tenant.
User provisioning: All users are provisioned and managed via Workday using SCIM. There is no separate user lifecycle management in Sana.
Core security principles
Principle | Description |
Data Isolation |
|
Encryption |
|
No model training on your data |
|
Permission mirroring |
|
Data handling and storage
Sana's architecture ensures that your data is handled securely throughout its lifecycle:
Workday data: Data retrieved via the Workday Self-Service Agent is stored in your encrypted chat history and retained long term. Any tool calls made while generating a response are stored securely in the database.
File uploads: Files uploaded by users are stored in dedicated Google Cloud Storage (GCS) buckets, isolated per customer. Files are used as per-chat context only — they are not pre-indexed and are not searchable outside of the chat where they were uploaded.
Connector data: Connectors do not ingest or index data from your third-party applications. Instead, they make real-time API calls to fetch the relevant information and generate an answer. This means your data in those systems is never stored or cached by Sana.
Sana least privilege principle
Access to data in Sana is governed by the principle of least privilege:
Private by default: All chats and uploaded files are private to the user who created them. No other user can see your conversations or documents.
Admin access is limited: Workspace Admins can manage settings and toggle features (such as connectors and email-domain restrictions), but they cannot access the content of other users' chats or files.
Source-based access control: When you search for information through a connector (e.g., Google Drive), Sana checks your credentials against the source system in real time. You will only see results for files you actually have access to in that system.
With "Privacy" settings, you can review how your data is handled and what controls are available to you.
FAQ
Q: Does Sana use my data to train any LLMs?
A: No. We have strict agreements with our model providers that ensure your data is never used for training purposes. Your data remains yours.
Q: Is my connector data stored by Sana?
A: No. Connectors make real-time API calls to the source application. Sana does not ingest, index, or cache the data from your connected tools.
Q: Can my Workspace Admin see my chats?
A: No. Admins can manage workspace-level settings and connectors, but they cannot see other users' private chats or files. Chat and file access are private to the signed-in user.