Shared vs Private Links

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

Private Links

Private links allow members to connect relevant apps without centralized IT or administrative intervention. The access and visibility of these links, along with the indexed data, are restricted solely to the member who established the connection. This makes private links 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 links, not shared company-wide.

Shared Links

Shared links (organizational) streamline data sharing within your organization by allowing workspace owners and admins to connect an app account and share its resources with specific groups or all members. Shared links enable members 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 links 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 links and define permissions for app resources, known as permission-based links.

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

Provisioned Links

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

• Microsoft 365

• G Suite

• Atlassian

Provisioned links 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.