Private Preview
Join Waitlist →

Configure organisation compliance settings

Set organisation-level compliance preferences as workflow defaults, not as a claim of certification or legal advice.

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

Outcome

You can choose relevant compliance workflow defaults and understand what those settings do and do not prove.

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 organisation admin account where this surface is available.
Know which framework or policy your organisation wants to support.
Confirm changes with your internal owner when policy matters.

Visual frame

Review asset

Organisation compliance settings storyboard

Synthetic organisation settings frame only. It treats frameworks as workflow labels and report defaults, not legal advice, certification, or audit approval.

FrameworksWorkflow labels
DefaultsReport settings
BoundaryNot certification

Synthetic frame

Compliance settings

Choose workflow labels carefully.

Framework labelInternal policy
Region noteTeam-owned
Legal adviceNot provided
Framework settings organise workflow evidence; they do not certify compliance.

Configure organisation compliance settings workflow frame

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

FindChoose relevant workflow frameworks
DecideSet report and review defaults
VerifyDocument the boundary

Guided steps

Follow the task, then check the result.

Choose relevant workflow frameworks

Select only frameworks or presets that match the work your organisation actually reviews.

Success check: Selected settings match the organisation workflow.

Set report and review defaults

Choose report detail, retention, or review defaults only where those controls are visible and understood.

Success check: Defaults are saved and visible in the relevant report or review workflow.

Document the boundary

Make clear internally that these settings support review workflows and do not create certification by themselves.

Success check: The team understands what the setting supports and what it does not claim.

Branch questions

Completion check

Only relevant frameworks or presets were selected.
Report or retention defaults were checked in the affected workflow.
No certification or legal-advice claim was made from the setting alone.

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-compliance-settings
Selected issue: A saved compliance setting does not appear in reports.
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

Configure organisation compliance settings

Set organisation-level compliance preferences as workflow defaults, not as a claim of certification or legal advice.

Use this guide when the organisation compliance settings 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 choose relevant compliance workflow defaults and understand what those settings do and do not prove.

Before You Start

  • Use an organisation admin account where this surface is available.
  • Know which framework or policy your organisation wants to support.
  • Confirm changes with your internal owner when policy matters.

1. Choose relevant workflow frameworks

Select only frameworks or presets that match the work your organisation actually reviews.

Check before you continue: Selected settings match the organisation workflow.

2. Set report and review defaults

Choose report detail, retention, or review defaults only where those controls are visible and understood.

Check before you continue: Defaults are saved and visible in the relevant report or review workflow.

3. Document the boundary

Make clear internally that these settings support review workflows and do not create certification by themselves.

Check before you continue: The team understands what the setting supports and what it does not claim.

Completion Check

  • Only relevant frameworks or presets were selected.
  • Report or retention defaults were checked in the affected workflow.
  • No certification or legal-advice claim was made from the setting alone.

Safe Examples

  • A synthetic policy note saying AU Privacy workflow review.
  • A masked organisation settings screenshot.

If You Need Support

Contact support when:

  • A saved compliance setting does not appear in reports.
  • A framework option is unclear or mismatched to its article.

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-compliance-settings
Route: /knowledge-base/org-compliance-settings
Selected issue: A saved compliance setting does not appear in reports.

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