> 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

Fix disconnected accounts, reassign accounts to entities, and manage your integration settings.

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. Add the bank again and Kick links it back to your existing account.

1. On the **Accounts** tab, click **Add account**, *not* **Fix connection** on the broken account
2. Choose your bank and log in with the same credentials you used before
3. Kick asks whether this is a new login or the same login, because you've already connected this bank. Select **This is the same login**

Kick saves the new connection and links each account to the existing Kick account with the same last 4 digits. Your history, categories, and rules stay on that account, and new transactions sync into it, so there's nothing to merge or re-categorize.

{% hint style="info" %}
After you reconnect, the old connection can stay listed on the **Integrations** page in **Settings**, sometimes still showing **Fix connection**. Your accounts now sync through the new connection, so leave the old one alone and don't add the bank again. To confirm it's working, open the account on the **Accounts** tab and check that new transactions are arriving. If they aren't, [contact support](/troubleshooting/contact-us.md).
{% endhint %}

{% hint style="warning" %}
Don't click **Remove integration** on the old connection. Removing it also deletes the transactions that connection brought in, even though your account stays, so you lose that history.
{% endhint %}

Kick links an account only when all of these match. Otherwise it adds it as a separate account:

* **Last 4 digits.** Exactly one of your existing accounts at this bank has the same last 4 digits, and your bank returns only one account with those digits.
* **Bank.** It's the same bank as the original connection.
* **Person.** You're the person who connected the original account in Kick.
* **Entity.** If you're adding it to an entity, it's the same entity as the original, or the original isn't assigned to one.
* **Account type.** It's the same kind of account, for example checking or credit card. Kick checks this only while the original account is still active.
* **Archived accounts.** If the original account is archived, no other working connection still syncs it.

If your bank issued a new account or card number, Kick can't match it and adds a separate account. [Contact support](/troubleshooting/contact-us.md) with your bank name and the account you reconnected, and we merge it into your original account so you keep one account with its full history. Don't remove the original account, support needs it in place to complete the merge.

{% hint style="warning" %}
Select **This is a new login** only when you're connecting a different set of credentials at the same bank, such as a second business login. It adds a separate account for every account that's still active in Kick, even when the last 4 digits match. Closing the question without choosing does the same.
{% 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

1. Go to the **Accounts** tab
2. Click ⋯ on the account → **Settings**
3. Click **Remove account**
4. Choose whether to keep the account's historical data:
   * Keep it and click **Archive account**. Kick disables the account and keeps its transactions in your books.
   * Remove it and click **Remove account**. Kick deletes the account and all its transactions.

Workspace admins, accountants, and the person who connected the account can remove it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/integrations/manage-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.