> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting data sources via link sharing

> Delegate the connection step to a colleague or client who has the platform credentials by sharing a link to the connection page.

When the person setting up the dashboard doesn't have credentials for the source platform — common with agencies, contractors, or partners — link sharing delegates the OAuth step to someone who does. The recipient signs into the source platform from their own account; no extra workspace user is created.

## When to use it

Link sharing works for OAuth-based data sources. Examples include **Meta Ads**, **Google Ads**, **LinkedIn Ads**, **TikTok Ads**, **Microsoft Ads**, **Snapchat Ads**, **Pinterest Ads**, and the OAuth-based organic, public, analytics, and CRM data sources.

It does not apply to file or database connections — **CSV File**, **Google Sheets**, **BigQuery**, **PostgreSQL**, and similar — because those don't use OAuth on the source platform.

## Share a connection link

<Steps>
  <Step title="Open the Data sources page">
    Navigate to **Data sources** in the top navigation.
  </Step>

  <Step title="Copy the connection link">
    Click **Copy link** in the page header. The link is copied to the clipboard.
  </Step>

  <Step title="Send the link to the credential holder">
    The link works without requiring the recipient to have an Adriel account. Treat the link as sensitive — anyone who opens it can connect a data source to the workspace.
  </Step>

  <Step title="Recipient connects the data source">
    The recipient opens the link, signs into the source platform (for example **Meta Ads Manager**), authorizes Adriel, and selects the accounts to connect.
  </Step>

  <Step title="Data source appears in the workspace">
    Once the recipient finishes, the new data source shows up on the Data sources page in the workspace. The account ID and name display in the standard connection row.
  </Step>
</Steps>

## What the recipient sees

When the recipient opens the link, they land on a branded connection page (whitelabel-aware where configured). They don't see workspace dashboards or other data sources — only the OAuth flow for the platform being connected.

The recipient:

1. Sees a "Connect your account" prompt with the platform's logo.
2. Clicks **Connect** to start the platform's OAuth flow.
3. Signs into the platform with their own credentials.
4. Authorizes Adriel.
5. Picks the accounts to connect.
6. Sees a confirmation.

The recipient does not need to enter the workspace, doesn't see other data sources, and doesn't have ongoing access to anything after the connection is created.

## Disconnect a data source

When a connected data source is no longer needed:

<Steps>
  <Step title="Open the Data sources page">
    Navigate to **Data sources**.
  </Step>

  <Step title="Find the data source">
    Locate the row for the data source to disconnect.
  </Step>

  <Step title="Open the row actions and choose Disconnect">
    Click the row's action menu and select **Disconnect**.
  </Step>

  <Step title="Confirm in the dialog">
    A confirmation dialog asks to confirm. Click **Disconnect** to remove the connection. Widgets that referenced the disconnected data source stop returning data; historical cached data is removed.
  </Step>
</Steps>

Disconnecting a data source removes its data from the workspace. If the source needs to be re-added later, re-run the connection flow — historical cached data is not automatically restored.

## Security considerations

* The connection link is bearer-style — anyone who opens it can connect a data source to the workspace. Send it through trusted channels (direct message, encrypted email) rather than public ones.
* The link doesn't grant dashboard access to the recipient. It only allows them to add a connection.
* Workspace admins see every data source added through the link in the standard Data sources list and can disconnect any of them.
* The recipient's OAuth session is on the source platform, not on the workspace — they don't get a workspace account just by completing the connection.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The recipient connected successfully but the data source isn't showing in the Data sources list">
    Refresh the Data sources page. New connections appear immediately for most platforms; some platforms take a few minutes to surface accounts. If the connection still doesn't appear after 10 minutes, check whether the recipient finished the account-selection step at the end of the OAuth flow — abandoning at that step doesn't create a connection.
  </Accordion>

  <Accordion title="The recipient sees an error during OAuth">
    Common causes: (1) the recipient doesn't have the right role on the source platform (most platforms require admin or reporting-level access); (2) the source platform blocked the OAuth request due to a security setting (two-factor, IP allowlist); (3) the recipient used the wrong source platform account. Ask the recipient to try with an account that has admin access to the relevant account.
  </Accordion>

  <Accordion title="Want to remove the connection without the recipient's involvement">
    Workspace admins can disconnect any data source from the Data sources page, regardless of who created it. The recipient doesn't need to do anything on their end.
  </Accordion>

  <Accordion title="Need to share the link with multiple people">
    The same link works for any number of recipients. Each recipient creates their own connection independently. If the same platform account is connected twice (by two different recipients), the workspace shows two rows in the Data sources list — disconnect either one to clean up.
  </Accordion>
</AccordionGroup>

Related: [Permissions and access](/data-sources/managing/permissions-and-access) · [Connector catalog overview](/data-sources/overview) · [Managing members & access](/workspace-and-access/managing-members)