A calendar connection makes meetings available to In Parallel; automatic joining is controlled separately.

Open Settings → Personal → Integrations and review Meeting Recorder settings for internal and external meetings. Then open the individual meeting and confirm that Recorder joining is on. This per-meeting toggle controls whether the Recorder joins regardless of Workspace linkage; linking determines whether the meeting contributes to that Workspace's shared context, while an unlinked meeting can still produce a meeting summary. If it is a Zoom meeting, also confirm that Zoom is connected.

Under Calendar, select Disconnect for the incorrect provider or account, then connect the calendar that contains your work meetings. Disconnecting can affect future meeting capture, so check upcoming meetings afterward.

Select Update available and complete the provider's authorization flow. This adds newly required permission scopes without removing the healthy connection first. Slack may separately show Update notifications for the personal notification connection.

The update action does not detect every revoked or expired token. If the connection still fails and no update appears, disconnect and reconnect it after checking the impact. See Update calendar and Slack permissions.

The Slack app installation and your personal notification authorization are separate steps. In Settings → Personal → Integrations, find Slack and select Connect notifications. If the app is not installed, ask a Slack administrator to install it first.

Check whether the Microsoft Teams integration shows Personal notifications enabled. Follow the integration's reinstall or uninstall instructions if the personal app connection is not working. Also review Settings → Personal → Notifications for the event types you expect.

The In Parallel chat can look normal in Teams while connect gets no reply. Other messages may still get a response. In one observed case, Teams rejected the sign-in card with a 403 response saying User blocked the conversation with the bot. even though the conversation did not appear blocked in the user's Teams client.

Blocking and then unblocking restored the connection in that case. The cause has not been confirmed, so if connect still gets no reply or those menu options are unavailable, contact In Parallel support. Tell them that connect is silent while the chat looks unblocked, and whether other messages receive replies.

Under Zoom, select Connect and authorize the integration. Also review the external-meeting Recorder switch and confirm that the meeting host allowed the Recorder to join.

MCP does not bypass In Parallel permissions. A missing Workspace may be an access issue rather than a connector failure.

Change Preferred AI client for Send to AI under Settings → Personal → Integrations, or select Always ask. The setting's label has not yet been updated everywhere.

Contact the In Parallel support team with the integration name, the status shown on screen, and the last step that succeeded. Do not send access tokens or authorization codes.