> ## Documentation Index
> Fetch the complete documentation index at: https://dataleap-469bb19d-docs-from-commits-2026-08-19-upload-limits.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your tools

> Connections are the agent's arms — set up once per account, activated per workflow with exactly the permissions needed.

Connections are the agent's **arms** — they define what it can reach and act on in your systems. Connecting happens on two levels, and both live in the build conversation.

## Level 1: Connect the tool to your account — once

The first time a workflow needs a tool you've never connected, Dataleap tells you and prompts the sign-in right in the chat:

> *"No existing Jira connection in your account, so I'll create a new one — this will prompt an OAuth authorization on your end."*

You click **Connect**, sign in once, done. From then on, that connection exists for your whole account.

<Frame caption="First-time connection: one click, one OAuth sign-in.">
  <img src="https://mintcdn.com/dataleap-469bb19d-docs-from-commits-2026-08-19-upload-limits/9b7WCSBKC0-1NVfb/images/connections-first-connect.png?fit=max&auto=format&n=9b7WCSBKC0-1NVfb&q=85&s=b83a7f6de90d0203a47bfaa3eed3e6cf" alt="Dataleap chat requesting a new Jira connection with a Connect button" width="1480" height="604" data-path="images/connections-first-connect.png" />
</Frame>

<Info>
  You can also set up connections ahead of time under **Settings** > **Connected Apps** — the same place where you reconnect an expired login or review what's connected.
</Info>

## Level 2: Activate it for the workflow — with exactly the permissions needed

An account-level connection doesn't give every agent free rein. For each workflow, the agent requests the **specific tools** it needs from that connection — and you see every single permission before approving:

<Frame caption="Every permission is visible — and the set is as small as the workflow allows.">
  <img src="https://mintcdn.com/dataleap-469bb19d-docs-from-commits-2026-08-19-upload-limits/9b7WCSBKC0-1NVfb/images/connections-workflow-permissions.png?fit=max&auto=format&n=9b7WCSBKC0-1NVfb&q=85&s=c17b7d77a396140d358d900dc5794dea" alt="The agent requests to activate connections: Gmail and Notion, each listing the exact tools requested, with an Approve All button" width="1448" height="1090" data-path="images/connections-workflow-permissions.png" />
</Frame>

The gray labels are the permissions — *Create Draft*, *Create Label*, *Download Attachment*, and so on. Dataleap keeps this set **as small as possible**: enough for the workflow to run, and nothing beyond it. One click on **Approve All**, and the agent is equipped.

## What this means in practice

<Steps>
  <Step title="You describe the job">
    *"Give me a briefing before every meeting, based on my calendar and my emails."*
  </Step>

  <Step title="Dataleap names what it needs">
    *"For that I'll need access to your calendar and your email — please connect your Google Calendar and your Gmail."* New tools get the one-time account connection; known tools go straight to the permission request.
  </Step>

  <Step title="You approve">
    Review the requested permissions and click **Approve All**. Connections are reusable — the next agent that needs Gmail skips level 1 entirely.
  </Step>
</Steps>

Workspace-wide governance (reviewing, reconnecting, removing connections centrally) is an admin topic: see [Connected apps management](/admin/connected-apps-management).

<Card title="Watch: Connecting your tools" icon="clapperboard" href="/video-series/section-2#connecting-your-tools" horizontal>
  See the connection flow in action.
</Card>

<CardGroup cols={2}>
  <Card title="Add knowledge" icon="database" href="/build/add-knowledge">
    Next: give the agent your reference material.
  </Card>

  <Card title="Apps & permissions" icon="plug-circle-check" href="/admin/connected-apps-management">
    The admin view: tool-level permissions and governance.
  </Card>
</CardGroup>
