Issues with calendar connections, notification tools, and email integrations.

Cause: The calendar connection authorizes In Parallel to read your calendar, but the Transcriber only joins meetings that are explicitly linked to an Execution Scope. Connecting the calendar in Settings is a prerequisite, not sufficient on its own.

Fix: Open the meeting in In Parallel and confirm that the Transcriber is enabled for that meeting (the Capture actions toggle should be on). If you've connected the calendar but haven't linked any meetings to a scope yet, follow the steps in Connect a recurring meeting.

Cause: Slack has two separate steps: the In Parallel app must be installed in your Slack workspace (admin task), and then each user must individually click Connect notifications to enable their personal DMs. Completing only the workspace install doesn't activate personal notifications.

Fix: Open Settings → Integrations and check the Slack section. If the status shows Installed to In Parallel workspace but no personal connection, click Connect notifications and authorize your personal Slack account. If Slack doesn't appear at all, ask a workspace admin to install the In Parallel app first.

Cause: An integration is feeding more signals into the Living Execution Plan than are useful for the scope — often because too much task-level detail is being treated as execution-relevant.

Fix: Keep the Living Execution Plan high-signal: priorities, milestones, accountable actions, and decisions. Granular task breakdowns, sprint states, and ticket-level detail should stay in Jira, Asana, or your delivery tool. If signals from an integration are consistently low-value for a scope, consider whether that integration is the right one to connect for that scope.

Contact the In Parallel support team.