Shared vs Private Sources

Unleash allows users to connect souces at individual and organizational levels, depending on the availability of the APIs.

Private Sources

Private sources allow users to connect relevant apps without centralized IT or administrative intervention. The access and visibility of these sources, along with the indexed data, are restricted solely to the user who established the connection. This makes private sources ideal for individuals who prefer to access resources exclusive to them without making them accessible to the entire organization. For example, email, calendars, and drives are generally private sources, not shared company-wide.

Shared Sources

Shared sources (organizational) streamline data sharing within your organization by allowing workspace owners and admins to connect a source and share its resources with specific groups or all users. Shared sources enable users to discover and access resources indexed from the linked app, contingent upon their permissions. Clicking on a specific resource in Unleash redirects users to the original app, where they must adhere to its access rules.

Creators of shared sources can also apply restrictions. Opting for "restricted access only" means recipients can see titles of specific data in search results but cannot preview or access the content itself.

For certain apps, admins and workspace owners can create shared sources and define permissions for app resources, known as permission-based sources.

Note: We recommend creating a dedicated service account for Shared sources for ease of maintenance.

Provisioned Sources

Provisioned sources are designed to automatically create personal sources for users, eliminating the need for additional effort from them. These sources are a type of meta-source, set up centrally by the workspace owner. Upon first login, users receive a personal source to the relevant app without manual intervention. Currently, provisioned sources are supported on the following integrations:

• Microsoft 365

• G Suite

• Atlassian

Provisioned sources work by utilizing a specialized API from the third-party vendor. This API creates a secure, impersonated token with restricted access based on a master token. Each user receives a private link to the specific data source, ensuring no data is shared between users.