Connecting your tools

ddx PMO is only as useful as the communications it can see. The more sources you connect, the more complete the registers, graph, and health picture become.

You set these up per project under Settings → Connections (the onboarding checklist links straight there).

The sources

Email

Each project has one or more email aliases. Forward or copy project mail to an alias and it arrives in the project Inbox, where it’s classified into the right registers. Aliases also help route mail to the correct project.

Meetings

Meeting transcripts and notes (for example exported markdown, or Granola transcripts from your drive) come in as a source and become entries in the Meetings register, with actions and decisions extracted.

Documents

Upload standalone PDF / Word / PowerPoint documents. Their content is extracted and classified just like any other source, and the files are kept and linked to what was derived from them.

Slack

Bind a project to one or more Slack channels. Messages are ingested as a source (with back-fill of recent history when you connect), so decisions and actions raised in chat aren’t lost.

ClickUp (Flow)

Bind a project to a ClickUp space, folder, or list. ddx PMO uses ClickUp as a process signal — how work actually moves — not as a task mirror. That powers the Flow view: rework, ageing tasks, cycle time.

Tip

After you bind ClickUp, re-run the backfill — that’s what registers the ClickUp webhook so future changes stream in automatically. Don’t create the webhook by hand in ClickUp; the app manages it for you.

Turning a source off

Sources are organised as modules you can enable or disable per project under Settings → Modules. Disabling one stops new processing and hides it from the sidebar but keeps existing data; re-enable it and run a backfill to catch up.