> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/functionality/how-to-manage-connected-accounts/accounts-access-requests.md).

# Accounts access requests

{% columns %}
{% column %}
{% hint style="success" icon="user-key" %}
Role requirement: Workspace admin & Organization owner
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="cart-circle-plus" %}
Plan requirement: Active, Pro, Agency & Enterprise
{% endhint %}
{% endcolumn %}
{% endcolumns %}

When you set up an integration in Coupler.io, you sometimes need someone else to connect their data source — a client, a teammate, or a contractor. But asking them to create a Coupler.io account just to authorize one connection adds friction and confusion.

**Accounts access requests** solves this. You generate a shareable link for a specific source, send it to the person who owns the account, and they connect it directly — without signing up to Coupler.io.

***

### How it works

{% @arcade/embed flowId="swmv87sb2Avmsi5Csjrq" url="<https://app.arcade.software/share/swmv87sb2Avmsi5Csjrq>" %}

{% stepper %}
{% step %}
Go to **Sources → Accounts access requests**
{% endstep %}

{% step %}
Click **+ Generate new link** and select the source you need connected (e.g. Shopify, LinkedIn Ads, Google Ads)
{% endstep %}

{% step %}
Copy the link and send it to the person who owns the account
{% endstep %}

{% step %}
They open the link, review what access they're granting, and click **Start** to authorize
{% endstep %}

{% step %}
Once connected, the account appears in your workspace and is ready to use in integrations
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Each link is single-use and expires after 7 days.
{% endhint %}

***

### Who is this useful for?

**Agencies and consultants** working with clients Your client owns the Facebook Ads or Google Analytics account. Instead of asking them to log into Coupler.io, you send them a link. They authorize in seconds, and you get access to pull their data.

**Teams where data is owned by someone outside your workspace** A finance team member needs to connect a QuickBooks or Xero account owned by the accounting department. Rather than sharing credentials or adding them as a user, you send them a link to connect it directly.

**Anyone setting up integrations on behalf of others** You're building a reporting pipeline and need a client or partner to connect their source. No account setup required on their end.

***

### Managing links

All generated links are listed in **Sources → Accounts access requests** with their status, expiry date, and who created them.

| Status  | Meaning                                     |
| ------- | ------------------------------------------- |
| Active  | Link is valid and ready to use              |
| Used    | Someone has already connected via this link |
| Expired | Link has passed its expiry date             |

You can delete a link at any time. Deleting a link does not disconnect an account that has already been connected through it - it only prevents the link from being used again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/functionality/how-to-manage-connected-accounts/accounts-access-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.