Private Preview
Join Waitlist →

Configure security settings

Review security-related settings and understand which choices affect access, sharing, and local workflow safety.

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

Outcome

You can review security settings deliberately and verify the change affects the workflow you care about.

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 account with permission to change settings.
Know whether you are changing personal, team, or organisation behaviour.
Record the current setting before changing it if you may need to roll back.

Visual frame

Review asset

Security settings storyboard

Synthetic settings frame only. It avoids listing unavailable enterprise controls as universal product behaviour.

ScopeAccount / team / workflow
ChangeOne at a time
VerifyAffected workflow

Synthetic frame

Security settings

Check what this setting controls.

Current scopeTeam sharing
Not scopePersonal Vault
WarningAffects packages
A security setting is safe to change only after its scope is clear.

Configure security settings workflow frame

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

FindFind the setting and scope
DecideChange one setting at a time
VerifyVerify the affected workflow

Guided steps

Follow the task, then check the result.

Find the setting and scope

Confirm whether the setting applies to your account, a team, a workspace, or a specific sharing workflow.

Success check: You know the scope before changing anything.

Change one setting at a time

Make one deliberate change, save it, and check for any warning text before moving to the next setting.

Success check: The saved state matches the intended choice.

Verify the affected workflow

Open the workflow the setting should affect, such as sharing, Vault, or review defaults, and confirm the behaviour changed.

Success check: The setting is visible in the workflow it controls.

Branch questions

Completion check

Setting scope was understood before saving.
Only intentional settings were changed.
The affected workflow was verified.

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/security-settings
Selected issue: A saved setting 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

Configure security settings

Review security-related settings and understand which choices affect access, sharing, and local workflow safety.

Use this guide when the security 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 review security settings deliberately and verify the change affects the workflow you care about.

Before You Start

  • Use an account with permission to change settings.
  • Know whether you are changing personal, team, or organisation behaviour.
  • Record the current setting before changing it if you may need to roll back.

1. Find the setting and scope

Confirm whether the setting applies to your account, a team, a workspace, or a specific sharing workflow.

Check before you continue: You know the scope before changing anything.

2. Change one setting at a time

Make one deliberate change, save it, and check for any warning text before moving to the next setting.

Check before you continue: The saved state matches the intended choice.

3. Verify the affected workflow

Open the workflow the setting should affect, such as sharing, Vault, or review defaults, and confirm the behaviour changed.

Check before you continue: The setting is visible in the workflow it controls.

Completion Check

  • Setting scope was understood before saving.
  • Only intentional settings were changed.
  • The affected workflow was verified.

Safe Examples

  • A screenshot with user names and workspace names masked.
  • A synthetic description such as changed share expiry default.

If You Need Support

Contact support when:

  • A saved setting does not persist.
  • A setting applies to a different scope than the screen suggests.

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: security-settings
Route: /knowledge-base/security-settings
Selected issue: A saved setting 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