<span id="连接插件账号与恢复授权"></span>

# Connect plugin accounts and recover authorization

Use a plugin's installation or connection card to authorize the external account it needs. Plugin account authorization, manually entered tool credentials, and managed IM connections use different flows.

<span id="完成授权"></span>

## Complete authorization

1. Start authorization from the original card.
2. Wait while it shows **Preparing authorization**.
3. Open the authorization page, review the account and permissions, and confirm on the external platform.
4. Return to MOI and check the connection status.
5. Return to the original task and verify its progress and result.

<span id="授权中断后继续"></span>

## Resume interrupted authorization

If you closed the external page or installation card, reopen the original entry to continue that authorization flow. Check the existing status before creating another connection. External authorization success and task completion must be verified separately.

Confirm authorization-page success separately from original-task completion. After returning to MOI, check connection state, then execution progress/results in the original conversation.

<span id="凭证过期后重新登录"></span>

## Sign in again after credentials expire

Use the existing account connection's sign-in control when credentials expire. After authorization, inspect the original task before resubmitting it, especially when it can write data or send messages.

<span id="排查问题"></span>

## Troubleshooting

| Symptom | Check and action |
| --- | --- |
| Authorization remains pending | Retain the current page message and operation time, then reopen the original card to inspect its state. |
| Authorization is confirmed externally but MOI shows no connection | Return to the original connection card to check authorization, rather than relying only on the external page. |
| Account connected, but execution is unauthorized | Check the authorized account and target object privileges. Successful connection does not grant access to all data. |
| Tool failure with an unavailable execution environment message | Check account authorization and the [runtime environment](../runtime-environments/index.md) separately, then handle the specific error. |

For manual API Key, Token, or email authorization-code changes, see [maintain tools and credentials](manage-tools.md). To configure external MCP services, see [add custom MCP tools](add-tools.md).
