> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/integrations/manage-integrations.md).

# Manage Integrations

All your connected accounts are managed from the **Accounts** tab. Click the options menu (⋯) on any account to access its settings.

***

### Fix a disconnected account

Bank connections can occasionally disconnect, usually because your bank requires re-authentication after a password change or security update. When this happens, the account shows a connection error on the Accounts tab.

1. Go to the **Accounts** tab
2. Click **Fix connection** on the affected account
3. Re-authenticate with your bank

Once reconnected, Kick automatically syncs any missed transactions.

#### When Fix connection won't reconnect

Sometimes a connection drops completely and **Fix connection** won't bring it back, even though your bank may show the login as successful. This usually means the account has *churned* on the bank's side: your bank changed the underlying account details (a new card, a renamed account, a replacement after fraud, or a migration), and Plaid lost its link to the original account. The original connection no longer exists to restore, so it has to be reconnected as a new account and merged back into the original.

1. On the **Accounts** tab, click **Add account**, *not* **Fix connection** on the broken account
2. Complete the login flow with your bank
3. When asked whether this is a new login or the same login, select **This is a new login**. This creates a duplicate account, which is expected
4. [Contact support](/troubleshooting/contact-us.md) with your bank name and which account(s) you reconnected
5. We merge the new connection into your original account on the back end

The merge moves the live connection onto your original account, removes the duplicate account and its transactions, and preserves your existing categorizations, rules, and manual edits, so you keep your full history with nothing to re-categorize.

{% hint style="warning" %}
Choosing **This is a new login** intentionally creates a duplicate. Don't remove the original account, support needs it in place to complete the merge.
{% endhint %}

***

### Reassign an account to a different entity

If an account is connected to the wrong business entity, you can reassign it without disconnecting.

1. Go to the **Accounts** tab
2. Click ⋯ on the account → **Settings**
3. Change the entity in the **Details** section

***

### Change the sync start or end date

The start date controls how far back Kick pulls in [transactions](/common-workflows/transactions.md). It defaults to your bookkeeping start date. The end date stops syncing after a specific date.

1. Go to the **Accounts** tab
2. Click ⋯ on the account → **Settings**
3. Click **Edit** next to the **Start date** or **End date**
4. Pick a new date and click **Set Date**

{% hint style="warning" %}
Changing the start date may pull in additional historical transactions or remove existing ones. If you've already categorized transactions in that range, check with your accountant before making changes.
{% endhint %}

***

### Remove an account

To disconnect an account entirely, go to the **Accounts** tab → click ⋯ → **Remove account**. Transactions already synced are not deleted, so they remain in your books.


---

# 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.kick.co/integrations/manage-integrations.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.