A calendar is connected but the Recorder does not join
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 feeds that Workspace's Living Execution Plan, while an unlinked meeting can still produce a meeting summary. If it is a Zoom meeting, also confirm that Zoom is connected.
The wrong calendar account 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.
Slack is installed but I receive no notifications
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.
Teams notifications are missing
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.
External Zoom meetings are not recorded
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.
An MCP-connected AI client cannot see a Workspace
Confirm that you can open the Workspace in In Parallel.
Recheck the client-specific setup under MCP connectors.
Reauthorize the connection if the token or session has expired. On the OAuth consent screen, select the missing Workspace and click Allow access.
Start a fresh client conversation and request the Workspace explicitly.
MCP does not bypass In Parallel permissions. A missing Workspace may be an access issue rather than a connector failure.
Run with AI opens the wrong client
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.
Still stuck?
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.