Integrations with other apps

You already use…

What to do in R&U

QC Approvals

Page Version Control → Based on QC Approvals. Confirmations wait until the page is approved.

QC Documents (revision value)

Page Version Control → Based on QC Revision Value.

AppFox Workflows (draft → published space)

Same version strategy in both spaces. Assign and notify on the published page.

Comala Publishing (draft → published space)

Same as Workflows, after Comala Sync.

1Password (OTP only)

Not a space setting. Use a one-time password.

QC Approvals and Read & Understood

Use both apps when a page must be approved before people confirm they have read it.

  1. Install QC Approvals on the same Confluence Cloud site (from the Marketplace), if it is not already there.

  2. Run your QC Approvals process on the page as you already do.

  3. Open the space → Space settings → Integrations → QC R&U - Space Settings → Settings.

  4. Set Page Version Control to Based on QC Approvals.

  5. Click Update. Confirm the warning if the app asks — changing strategy can change who is Accepted vs Accepted older version.

You should see: On the page, QC - R&U follows the approval state:

If in QC Approvals…

QC Read & Understood will…

Approvals are not finished

Read and Understood stays unavailable. Message: approvals are not complete in QC Approvals yet.

This version is Minor

No new confirmation is required. Message: marked as Minor in QC Approvals.

This version was rejected

Confirmation is blocked. Message: rejected in QC Approvals and is not available for R&U.

The version is approved for R&U

People can click Read and Understood as usual.

Do not choose this strategy if QC Approvals is not in use on the space. The byline will look broken.

Related reading: A Simpler Way to Manage Approvals and Read & Understood.

QC Documents (based on QC Revision Value)

Use this when the official version is a QC Revision Value from QC Documents, not the Confluence version number.

  1. Install QC Documents on the same site, if it is not already there.

  2. On each document page, set the revision in QC Page Revision Overview (QC Documents).

  3. Open the space → Space settings → Integrations → QC R&U - Space Settings → Settings.

  4. Set Page Version Control to Based on QC Revision Value.

  5. Click Update.

You should see: The byline version matches the QC revision. If the revision is missing, the byline shows an error instead of Read and Understood. To fix it see: https://support.qc-analytics.com/qc-read-and-understood-for-confluence-cloud/the-app-cannot-detect-the-version

Do not choose this strategy if QC Documents is not in use. Extra fields and the Export QC Revision Report button are on https://support.qc-analytics.com/qc-read-and-understood-for-confluence-cloud/qc-r-u-space-settings.

Draft space to published space


Integration with AppFox Workflows

  1. Set up the draft space and the published space in Workflows, following AppFox’s documentation.

  2. Use the same QC R&U version strategy in both spaces.

  3. After a page is published, open the published page → ••• → Apps → QC R&U - Page Overview.

  4. Assign people or groups.

  5. On Settings, turn on Notify users for page changes.

  6. Give QC Read & Understood and Workflows Edit on that published page (page restrictions). See The app cannot access the page.

When a new official version lands in the published space, assigned people can get an email to confirm again.

When using a third-party app to publish your pages from a draft space to a public one, it’s important that both space have the same R&U version strategy. QC Read & Understood works best here with Confluence version or Page properties, not QC Revision Value.

Integration with Comala Publishing

  1. Configure draft and published spaces in Comala Publishing.

  2. Match version strategy in both spaces.

  3. Publish with Comala’s Sync.

  4. On the published page, assign people in Page Overview and enable Notify users for page changes.

  5. Give QC Read & Understood Edit on the published page.

When using a third-party app to publish your pages from a draft space to a public one, it’s important that both space have the same R&U version strategy. QC Read & Understood works best here with Confluence version or Page properties, not QC Revision Value.

Integration with 1Password

1Password is a secure way to save your OTP for confirming you’ve read and understood a page. To learn more about how to set up 1Password for R&U, see this guide: https://support.qc-analytics.com/qc-read-and-understood-for-confluence-cloud/use-one-time-password-otp-to-r-u.