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.

When a channel, repository or space becomes private

Slack channels, GitHub repositories and ClickUp spaces can be made private after you bind them. ddx PMO checks every time it syncs. When one has become private, everything it already brought in — the messages, issues and tasks, and the risks, actions and decisions read out of them — is restricted to your internal team, the same as if it had been private from the start. That includes what it brought into other projects, and what a binding you have since removed left behind.

ddx PMO treats a channel, repository or space it can no longer see the same way: a channel made private with the app removed from it, a repository removed from the GitHub App, a space deleted or closed to the connected ClickUp user. It only concludes that when the connection itself still works — a revoked token is not taken to mean every channel went private.

It never works the other way on its own. If a private channel, repository or space is made public again, it stays private in ddx PMO. To let new content in openly, unbind it and bind it again; what it already brought in stays restricted.

A small shield icon beside a binding in Settings → Connections says when any of this is happening — hover or click it for the detail: earlier content is being restricted; ddx PMO is waiting for the provider to confirm the change before restricting anything; the provider now calls it public but it is still treated as private; or some tasks restricted with it belong to a company outside your internal team, which can no longer see them — reassign or re-class those if that company should still see them. No icon means there is nothing to say.

If ddx PMO cannot reach Slack or GitHub to check, a public channel or repository waits rather than bring anything new in, and its row shows why. A ClickUp backfill does the same.

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.

The other direction: Claude

Everything above is a source ddx PMO reads from. The Claude connector goes the other way: it lets Claude ask ddx PMO questions, so you can look up projects, registers and document contents — and ask for a document to be drafted — from inside a Claude conversation. It shows you only what you can already see in the app, and it cannot change your record: the one thing it writes is a new version of a document, which Claude asks you to confirm first. It is off unless it has been enabled for your workspace, and then switched on project by project.