Private Preview
Join Waitlist →

Manage notification settings

Choose which Redactorr notifications you need without exposing document names or private work in support.

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

Outcome

You can adjust email or in-app notification preferences and confirm the change applies to the intended event type.

Your progress

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

0 / 3 steps complete

Before you start

Use the account that should receive notifications.
Know whether the change is personal or team-wide.
Check spam or filtering rules before assuming a notification failed.

Visual frame

Review asset

Notification settings storyboard

Synthetic notification frame only. It uses fake events and avoids promising that every external inbox or device will receive notifications.

EventChoose trigger
PreferenceSave setting
DeliveryCheck channel

Synthetic frame

Notification events

Choose the workflow signal first.

Share accessEnabled
Package expiryReview
MarketingSeparate preference
Start by naming the event, not the channel.

Manage notification settings workflow frame

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

FindChoose the notification event
DecideSave the preference
VerifyVerify delivery or silence

Guided steps

Follow the task, then check the result.

Choose the notification event

Find the event type you care about, such as scan complete, share viewed, expiry, security alert, or product update.

Success check: The selected setting matches the event you want to change.

Save the preference

Change only the relevant preference and save. If there are separate email and in-app controls, check both.

Success check: The saved state matches your intended notification channel.

Verify delivery or silence

Trigger a safe event where possible or wait for the next expected event, then check inbox filters and in-app notification areas.

Success check: Notifications behave according to the saved preference.

Branch questions

Completion check

Event type and channel were selected deliberately.
Personal versus team scope was checked.
Delivery was verified without sharing private document names.

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/notification-settings
Selected issue: A saved preference does not persist.
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

Manage notification settings

Choose which Redactorr notifications you need without exposing document names or private work in support.

Use this guide when the notification 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 adjust email or in-app notification preferences and confirm the change applies to the intended event type.

Before You Start

  • Use the account that should receive notifications.
  • Know whether the change is personal or team-wide.
  • Check spam or filtering rules before assuming a notification failed.

1. Choose the notification event

Find the event type you care about, such as scan complete, share viewed, expiry, security alert, or product update.

Check before you continue: The selected setting matches the event you want to change.

2. Save the preference

Change only the relevant preference and save. If there are separate email and in-app controls, check both.

Check before you continue: The saved state matches your intended notification channel.

3. Verify delivery or silence

Trigger a safe event where possible or wait for the next expected event, then check inbox filters and in-app notification areas.

Check before you continue: Notifications behave according to the saved preference.

Completion Check

  • Event type and channel were selected deliberately.
  • Personal versus team scope was checked.
  • Delivery was verified without sharing private document names.

Safe Examples

  • A fake notification for Demo package viewed.
  • A masked email address domain only.

If You Need Support

Contact support when:

  • A saved preference does not persist.
  • Expected notifications do not arrive after filters are checked.

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: notification-settings
Route: /knowledge-base/notification-settings
Selected issue: A saved preference does not persist.

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