Skip to content

Write-back policies and approvals

Outcome

You will choose when Threadory may write to connected systems automatically, when a human must approve, and how many inferred relationship proposals reach the approval queue.

Before you begin

  • You need the Admin or Owner project role to change these settings or resolve approvals.
  • Connect and verify the target system before enabling any write-back.
  • Review the approval workflow with the people who will own the queue.

Configure review and reply behavior

  1. Open Settings → Review.
  2. Use Enable ticket / issue review to control automated triage comments on new or updated tickets and GitLab issues.
  3. Use Reply to human follow-ups to control one bot reply to a person who responds under the bot's review.
  4. Keep Auto-post reviews & replies (skip approval) off until the workflow has been tested in a safe project.
  5. Select Save.

With auto-post off, proposed reviews and replies wait for an administrator or owner in Approvals. Enabling auto-post requires a confirmation because it allows supported review and reply skills to publish without a pre-publication approval.

Use sampled review for auto-post

  1. Enable Auto-post reviews & replies (skip approval) only after reviewing representative accepted and rejected proposals.

  2. Set Auto-post audit rate:

  3. 0% sends no auto-post sample for quality review;

  4. 100% samples every auto-post and is effectively full manual review for quality monitoring;

  5. an intermediate value samples that share of auto-posted work.

  6. Select Save.

  7. Watch Approvals, Activity, and the external system during the trial.

An item selected for the audit sample is routed through Approvals instead of being auto-posted. It is a pre-publication gate for that sampled item only; non-sampled items still publish automatically.

The Link Resolver finds likely relationships across sources. Its tuning controls are advanced settings.

  1. Open Settings → Advanced / Operator → Link Resolver.
  2. Set Daily approval budget to the maximum number of medium-confidence proposals that may enter Approvals each day.
  3. Set Approval confidence threshold between 0 and 1.
  4. Select Save settings.
  5. Use Run now only when you deliberately want an admin-triggered scan.

Behavior at the boundaries:

  • a daily budget of 0 drops all medium-confidence proposals instead of routing them to Approvals;
  • a threshold of 1.0 means only high-confidence relationships are auto-persisted and no medium-confidence relationships are sent for review;
  • lowering the threshold increases the number of borderline proposals a human may need to review;
  • low-confidence proposals are discarded.

Apply risky policy changes safely

Enabling auto-post can publish external comments without pre-publication approval. Selecting Run now starts a scan immediately. A daily approval budget of 0 drops medium-confidence proposals instead of retaining them for later review.

  1. Record the current settings and connector identity.
  2. Use a safe project or a quiet change window, and avoid generating unrelated source events while changing the policy.
  3. Change one control, save, and generate one low-risk test event.
  4. Verify Activity, Approvals, and the external system before resuming triggers.

Turning auto-post off prevents future automatic publications but does not recall comments already published. Restore the recorded setting to recover from an incorrect configuration; correct or remove an external write in its source system under that system's policy. After fixing a dropped-proposal budget or threshold, run a new deliberate scan—do not assume discarded proposals will reappear automatically.

Verify the policy

  1. Generate one safe test event in the connected system.

  2. Open Activity and confirm the expected skill ran.

  3. Confirm that the result follows the chosen path:

  4. manual policy: a pending item appears in Approvals and nothing is written before approval;

  5. auto-post policy: the external comment appears and sampled items follow the configured audit rate;

  6. link policy: medium-confidence proposals respect the threshold and daily budget.

  7. Check the source context and external result, not only the run status.

Common problems

Symptom Likely cause What to do
A review was posted without a pending approval Auto-post is enabled for the project Turn it off, save, and inspect recent Activity
Auto-post is enabled but an approval appears The item was selected by the audit sample or another skill always requires approval Check the approval type and current audit rate
No link proposals appear The daily budget is 0, threshold is too high, or no candidates were found Review Link Resolver settings and the latest run
Too many low-value proposals appear The confidence threshold is too low Raise it gradually and compare acceptance rate
A member cannot resolve an approval Resolution is limited to admin and owner Assign queue ownership to an administrator; do not broaden a role solely to clear one item
An approved write fails The connected system rejected the action or the credential changed Inspect Activity, verify connector identity and permissions, then retry safely

Next step

Set budgets and model controls, then monitor decisions through the audit log.