Skip to main content

Guides

Help center

Short, illustrated guides for the redaction path, Fast Track, cases, integrations, and compliance.

All articles
Integrations
2 min read

HighQ write-back certification

Sandbox evidence checklist for HighQ Collaborate write-back before production go-live.

How it works

Connect

Admin credentials

Browse

Folder or case scope

Import

Into a Northdocs case

Apply

Then verify

Write-back

Optional, off by default

Sandbox Collaborate folder only. Do not write back into a live client site.

Audience: Northdocs solutions plus firm IT. Plan: Trial or Enterprise with connectors. Use a sandbox HighQ site/folder only. Do not write back into a live client Collaborate site.

Prerequisites: connectors entitlement; HighQ System Admin API application; instance URL (for example https://firm.highq.com/firm); redirect URI {APP_URL}/api/connectors/oauth/highq/callback; sandbox folder scoped to a non-production matter site area; Northdocs org admin.

  1. 1

    Connect

    Integrations → HighQ → enter instance URL + OAuth credentials → Authorize once (refresh token). Evidence: connector status connected, no lastError.

  2. 2

    Scope

    set root folder id to the sandbox area only. Evidence: browse limited to that site/folder tree.

  3. 3

    Import

    browse at least two levels; import one allowed PDF. Evidence: document in Northdocs with source provenance; processing starts.

  4. 4

    Redact

    review → apply → verify succeeds. Evidence: redacted export; verify green.

  5. 5

    Write-back (sandbox)

    choose create-new or native-version mode. For native version, provide the existing sandbox file id. Run certification and confirm SHA-256 verified.

  6. 6

    Audit

    confirm connector.connect, connector.import, connector.writeback. Evidence: audit screenshot or CSV snippet.

  7. 7

    Teardown

    disable write-back; disconnect if the sandbox engagement is over.

Pass criteria (all required): scoped sandbox import; verify before trusting export; selected mode succeeds; read-back SHA-256 matches; evidence downloaded; admin sign-off recorded; no live client site write-back.

Product notes: create-new uses the HighQ Upload API. Native-version uploads content to the existing HighQ file and retains its version id when returned. A certification cannot pass without a usable remote id and successful read-back.

See also: HighQ connector and Write-back of redacted PDFs. Contacts: sales@northdocs.com, security@northdocs.com.

Related articles

Still need a hand?