> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nylon.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Reconnect an account

> Restore a connection whose authorization stopped working, without losing the profile or its history.

When a profile shows **Reconnect**, the stored authorization no longer works. The profile, its id and its history all survive — only the credential needs replacing, and reconnecting replaces it in place.

Reconnecting does **not** create a new profile. The profile id your application stored stays valid, so there is nothing to migrate on your side.

## Reconnect from the dashboard

<Steps>
  <Step title="Find the profile">
    Open **Connections** and find the row. Use the **All networks** filter or the **Search profiles** box if the list is long.
  </Step>

  <Step title="Select Reconnect">
    Open the **⋯** menu at the end of the row and select **Reconnect**.
  </Step>

  <Step title="Authorize again">
    You are sent back through the network's own permission screen. Sign in with the account that owns the profile, and approve every permission asked for.

    For Facebook and Instagram, Nylon takes you straight back into the Meta flow with the right profile pre-selected, so you do not have to find it again in a list of Pages.
  </Step>
</Steps>

The badge returns to **Active** when it finishes.

## If reconnecting does not stick

Work through these in order — the first two cover most cases:

1. **You signed in with the wrong account.** The network account you authorize has to be the one that administers the profile. Being an editor is often not enough.
2. **You skipped a permission.** Networks let you approve selectively. Nylon needs everything it asked for; dropping one is the most common reason a reconnect appears to succeed and then fails at publish time.
3. **The profile changed type.** An Instagram account converted back to personal, or a Facebook Page whose admin changed, cannot be reconnected as it was. Fix it on the network first.
4. **Your own OAuth app changed.** If the profile's **OAuth app** column says *Your app*, the credentials come from [your BYOK entry](/help/configure-byok). Rotating or deleting a client secret there breaks every profile connected through it.

## Have your users reconnect their own accounts

If the account belongs to one of your users rather than to you, do not send them to the Nylon dashboard. Generate a connection URL from the API and open it in your own product; running it against an existing profile reconnects it.

Subscribe to `profile.needs_attention` so you can prompt the user the moment the credential fails, rather than finding out when their next post does not go out.

<Columns cols={2}>
  <Card title="Connecting from your own app" icon="square-terminal" href="/connections">
    The connection URL endpoint and its redirect contract.
  </Card>

  <Card title="Webhook events" icon="webhook" href="/help/webhook-events">
    Be told when a credential stops working.
  </Card>
</Columns>

## Related

<Card title="An account says Reconnect" icon="triangle-alert" href="/help/account-needs-attention">
  What causes it, and what your application should do in the meantime.
</Card>