In one sentence
Connect your Microsoft or Google account and the actions assigned to you show up as tasks in that account — completing one there marks it complete in QFormance, until the action is verified, at which point the QMS record stops taking outside edits.
Why it exists
Corrective and preventive actions get assigned to people who don't live in the QMS. A production supervisor with eight actions open is not going to check a quality system three times a day, and an action nobody sees is an action nobody does.
So instead of asking everyone to come to the actions register, the register goes to them — into the task list already open on their second monitor.
Connecting
Each person connects their own account. This is not an org-wide switch an admin flips; it's per user, and it has to be, because the tasks land in that person's personal task list.
- Go to Profile → Integrations.
- Pick Microsoft or Google and choose Connect. You can connect both.
- Sign in with that provider and approve the access it asks for.
You come back to your profile with the connection listed and a health pill next to it.
- Each person connects their own account. There's no org-wide switch, and no way for an admin to connect on someone's behalf — the tasks land in that person's private task list.
- If an assignee hasn't connected, nothing syncs for them. Their actions still work normally in QFormance; they just won't appear anywhere else. There's no penalty for opting out.
- You can connect both providers if you use Microsoft in one place and Google in another.
What goes out
Once connected, QFormance pushes a task whenever one of your actions is created, updated, verified, cancelled or deleted.
The task is titled with the originating record's reference in front — so you get
[NCR-042] Replace the seal on line 3 rather than a title with no context. Below
that, the body carries any closure notes written so far, the action's
description, and the due date, then a divider and a short instruction.
Everything above the divider is yours to write in.
It happens in the background and is deliberately non-blocking: if the provider is slow or down, your change in QFormance still saves. The connection gets flagged unhealthy and the push is retried — you're never left staring at a spinner because Microsoft is having a morning.
Where the tasks land
Under each connection there's a Task organization setting with two choices:
| Setting | What you get |
|---|---|
| A list per module | Separate lists — NCR actions in one, audit actions in another. Better if you want to triage by where the work came from. |
| One combined list | Every QFormance action in a single list. Better if you already have a system and don't want nine new lists in it. |
Lists are created as needed, so you don't have to set anything up beforehand.
What comes back
This is the half that makes it worth connecting.
- Complete a task in your task app → the QFormance action moves to completed, awaiting verification.
- Un-complete it (before anyone has verified it) → the action reopens in QFormance.
- Anything you typed above the divider comes back as the action's closure notes.
That last one is the point of the whole feature. You don't tick a box and then go and write up what you did somewhere else — you write it in the task, tick it off, and the explanation lands on the QMS record where the auditor will read it.
Type above the ─── divider. Everything below it — the description, the due
date, the Source: line — is written by QFormance and is ignored on the way
back. Leave it alone and it stays accurate; edit it and your changes there are
simply discarded.
The pull runs on a schedule rather than instantly, and the interval adapts to how active a connection is. Expect changes to land within minutes, not seconds. If you need it immediately, the Actions page has a sync button — it appears once you have a connection.
What stops syncing, and why
Once an action is verified, the link freezes. Changes you then make to the task in Microsoft or Google are recorded against the QFormance action as activity — so the trail shows someone touched it — but they no longer change the action.
That's deliberate rather than a limitation, and the reason is worth understanding if you manage a quality system.
That's deliberate. A verified action is a signed record: someone with the authority to do so confirmed the work was effective. Letting a checkbox in a personal task list quietly reopen or alter it afterwards would mean the QMS record could be changed by someone outside the QMS, with no reason captured. So the sync goes one way after verification — and if the action genuinely needs reopening, that happens in QFormance, with a reason, in the audit trail.
Deleting the task in your task app doesn't delete the action either. Nothing on the outside can remove a QFormance record.
Connection health
Each connection shows one of three states:
| State | Meaning |
|---|---|
| Healthy | Syncing normally. The last successful sync time is shown next to it. |
| Unhealthy | A recent sync failed. Usually transient — it retries on its own. |
| Needs reconnect | Your access has expired or been revoked at the provider. Nothing will sync until you choose Connect again. |
"Needs reconnect" is the one to act on. It happens when a password changes, when an IT admin revokes app access, or when a token simply ages out.
Disconnecting
Profile → Integrations → Disconnect. Syncing stops immediately.
Tasks already in your task app stay there — QFormance doesn't reach in and clean up after a disconnect, because by then they may carry your own notes and sub-tasks. Delete them yourself if you want them gone. Your QFormance actions are untouched: disconnecting changes how you're notified, never the record.
What this is not
Being straight about the boundaries, because the wrong expectation here is worse than the missing feature:
- It is not a replacement for the actions register. Closure notes, verification, evidence and the audit trail live in QFormance. The task app gives you a checkbox and a due date.
- It is not instant. Outbound is prompt; inbound is polled.
- It is not org-wide reporting. A manager can't see their team's actions in their own task app — everyone sees only what's assigned to them.
- It does not carry evidence. Closure notes come back; files, links and document-version references don't. If an action needs supporting evidence, attach it in QFormance.
- It doesn't verify anything. Ticking a task proposes completion. Somebody with the authority to verify still does that in QFormance, which is the point of having verification as a separate step.
Related
- Actions — the register itself, closure notes and verification
- How modules connect — the cross-module wiring inside QFormance, which is a different kind of "integration" from this one