Introduction
Sana Agents integrations play a crucial role in enhancing the functionality of our AI assistant by enabling it to access, read, and index data from various external systems. These integrations allow Sana Agents to deliver precise and contextually relevant responses based on the data it can access. Sana Agents provides three types of integrations: private, shared, and centralized. These are designed to enhance team collaboration by offering customized access to external systems.
Different integration types
| Private | Centralized | Shared |
Mirrored user access from integration | Yes | Yes | No, manage access in Sana |
Set-up | Per user | Workspace owner | Workspace owner |
Private integrations
Private integrations in Sana Agents are designed to cater to individual users by allowing them to connect their personal accounts from external services like Google Drive, SharePoint, or Outlook Calendar. This setup ensures that the data Sana Agents interacts with is exclusively the data accessible to that specific user under their account permissions. Here are some key features and benefits of private integrations:
User-specific Insights: Since the integration is linked to an individual's account, the insights and data retrieved are uniquely relevant to that user, making Sana Agents a highly personalized assistant.
Security and Privacy: By adhering to the permissions associated with the user's account, private integrations ensure that data privacy is maintained. Sana Agents accesses only the data that the user is authorized to view, preventing any unauthorized data exposure.
Centralized integrations
Centralized integrations, on the other hand, are set up to provide access to a common set of data across multiple users within an organization, while still adhering to underlying permissions. These are also configured by administrators who determine the scope of data accessibility based on team or organizational requirements.
Here are some important aspects of centralized integrations:
Collaboration: Shared integrations facilitate access to common data sources such as company-wide Google Drive folders or SharePoint sites, which are essential for collaborative work environments.
Security and Privacy: By adhering to the permissions associated with the user's account, centralized integrations ensure that data privacy is maintained. Sana Agents accesses only the data that the user is authorized to view, preventing any unauthorized data exposure.
Efficiency and Consistency: By providing multiple users access to the same data sets, centralized integrations ensure that everyone is on the same page, which is crucial for maintaining consistency in collaborative tasks and decision-making processes.
Shared integrations
Shared integrations are set up to provide access to a common set of data across multiple users within an organization. These are typically configured by administrators who determine the scope of data accessibility based on team or organizational requirements. Source permissions are not auto‑mirrored in Sana; visibility depends on who can access the shared integration in Sana and what you include during setup.
Here are some important aspects of shared integrations:
Collaboration: Shared integrations facilitate access to common data sources such as company-wide Google Drive folders or SharePoint sites. Admins explicitly choose which sites, libraries, or folders to include.
Admin Control: Administrators define which users or groups can access the shared integration in Sana, ensuring only authorized personnel can view synced content. If access is broad, users may see included content in Sana even without matching SharePoint permissions.
How to set limitations for who can access the integration (step by step):
Open the integration setup screen (or edit an existing integration).
Go to the final step of the setup flow and find “Share with a folder”
Open the dropdown and choose one of:
Everyone in [workspace] — grants access to all workspace members.
Specific folder — select an existing access folder (or create a new one).
If you chose a Specific folder, add only the users or groups who should access this integration to that folder.
Save.
Notes and best practices:
Keep the audience as narrow as possible; if someone can see an item in Sana they can’t in SharePoint, reduce who can access the shared integration and/or remove that site/folder from scope.
File-level restriction isn’t supported; scope folders tightly during setup.
Efficiency and Consistency: By providing multiple users access to the same data sets, shared integrations keep teams aligned. A shared integration can include multiple folders/sites—keep the scope as narrow as possible to avoid unnecessary exposure.
All files from integrations are re-synced every 24 hours to ensure that the most up-to-date information is available.
For further information about Sana Agents, please contact [email protected] via email.
