> 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/addons/google-sheets-addon/drive.google.com-refused-to-connect.md).

# drive.google.com refused to connect

This is a known issue that refers to the way Google manages multiple accounts. Google allows users to sign in to multiple accounts at once. All your accounts have separate settings but, in this case, the settings from the default account apply.

#### The error:

<div align="left"><figure><img src="/files/yUpr5ANiBDm2r8gKZPbm" alt="" width="188"><figcaption></figcaption></figure></div>

When you try to open a Coupler.io dashboard, you will see this error: *`error: drive.google.com refused to connect`*

#### To resolve this:

1. Sign out from all your Google accounts.
2. Sign in with the Google account that you used to install Coupler.io (it is required for this account to be the first one you sign in).


---

# 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/addons/google-sheets-addon/drive.google.com-refused-to-connect.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.