Private Preview
Join Waitlist →

Set organisation detection defaults

Choose default detection behaviour for an organisation while preserving user review and document-specific judgement.

Updated 31 May 20266 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: May 2026

Outcome

You can set sensible defaults for domains, categories, thresholds, or shared patterns and verify they apply to new reviews.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Use an authorised organisation admin account.
Know which document types and teams the default should support.
Keep final human review in every workflow.

Visual frame

Review asset

Organisation detection defaults storyboard

Synthetic organisation defaults frame only. It uses fake categories and keeps defaults conservative so users still review each output.

ScopeOrganisation default
ModeConservative
ReviewStill required

Synthetic frame

Detection defaults

Set scope before changing categories.

OrganisationDefault baseline
Team overrideReview allowed
New workspaceInherits defaults
Broad defaults should be scoped before categories are changed.

Set organisation detection defaults workflow frame

Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.

FindChoose the default scope
DecideSet defaults conservatively
VerifyTest a new review

Guided steps

Follow the task, then check the result.

Choose the default scope

Decide whether the default applies to a team, workspace, domain, or all new organisation reviews.

Success check: The scope is narrower than or equal to the policy need.

Set defaults conservatively

Enable domain choices, categories, or shared patterns that match common work. Avoid aggressive defaults that create too many false positives.

Success check: The defaults are saved and understandable to reviewers.

Test a new review

Start a new review with a synthetic or low-risk sample and confirm the defaults appear without overriding reviewer control.

Success check: New reviews start with the expected defaults and still allow review decisions.

Branch questions

Completion check

Default scope was intentionally chosen.
Defaults match common document work.
A new review confirmed the settings without removing human control.

Support boundary

Support can use by default

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Intent ID
  • Article slug
  • App route

Requires your consent

  • User-written description
  • Email address
  • Explicit attachment
  • Redacted sample
  • Support bundle previewed to the user

Not collected by default

  • Raw original document text
  • Full local file paths
  • Pasted private content
  • Unmasked screenshots
  • Replay capture

Safe support summary

Copy a scrubbed handoff.

Redactorr KB support summary

Article: /knowledge-base/org-detection-defaults
Selected issue: Defaults do not apply to new reviews.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route

Requires explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture

User note:
- Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.

Article details

Set organisation detection defaults

Choose default detection behaviour for an organisation while preserving user review and document-specific judgement.

Use this guide when the organisation detection defaults surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.

Outcome

You can set sensible defaults for domains, categories, thresholds, or shared patterns and verify they apply to new reviews.

Before You Start

  • Use an authorised organisation admin account.
  • Know which document types and teams the default should support.
  • Keep final human review in every workflow.

1. Choose the default scope

Decide whether the default applies to a team, workspace, domain, or all new organisation reviews.

Check before you continue: The scope is narrower than or equal to the policy need.

2. Set defaults conservatively

Enable domain choices, categories, or shared patterns that match common work. Avoid aggressive defaults that create too many false positives.

Check before you continue: The defaults are saved and understandable to reviewers.

3. Test a new review

Start a new review with a synthetic or low-risk sample and confirm the defaults appear without overriding reviewer control.

Check before you continue: New reviews start with the expected defaults and still allow review decisions.

Completion Check

  • Default scope was intentionally chosen.
  • Defaults match common document work.
  • A new review confirmed the settings without removing human control.

Safe Examples

  • A synthetic HR sample for an employment domain default.
  • A fake ID pattern used to test shared defaults.

If You Need Support

Contact support when:

  • Defaults do not apply to new reviews.
  • Defaults override user decisions unexpectedly.

Include only support-safe context:

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.

Still stuck?

Copy a safe article handoff.

Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: org-detection-defaults
Route: /knowledge-base/org-detection-defaults
Selected issue: Defaults do not apply to new reviews.

Safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
- Screen name or article section
- Action name

Only include with explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
- Hidden diagnostic uploads

User note:
- Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.

Support case builder

One case format, wherever you start.

This is the same support case shape used by diagnostics and article handoffs.

Safe to include
  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Article slug
  • Selected issue
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide