Skip to content
Private Preview
Join Waitlist →

Use security score recommendations

Turn security score recommendations into review actions without treating the score as a certification.

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

Outcome

You can understand recommended actions, decide which ones apply, and verify the result after making changes.

Your progress

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

0 / 3 steps complete

Before you start

Know the account, team, or workspace scope of the score.
Treat recommendations as prompts for review.
Do not make bulk settings changes without understanding the effect.

Visual frame

Review asset

Security score recommendations storyboard

Synthetic recommendations frame only. It treats recommendations as review prompts, not security certification or proof that a workspace is safe.

RecommendationReview prompt
DecisionApply if relevant
ProofVerify outcome

Synthetic frame

Security recommendation

Understand the reason before acting.

RecommendationReview share expiry
ReasonLong-lived links
ScopeWorkspace setting
Recommendations are easiest to verify when handled one at a time.

Use security score recommendations workflow frame

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

FindRead one recommendation at a time
DecideDecide whether it applies
VerifyVerify the result

Guided steps

Follow the task, then check the result.

Read one recommendation at a time

Open the recommendation details and check which workflow it affects before acting.

Success check: You know what the recommendation wants you to change.

Decide whether it applies

Some recommendations may not fit your workflow or policy. Apply only the recommendations you understand and are authorised to change.

Success check: The action is appropriate for your workspace.

Verify the result

After applying a recommendation, check the affected workflow and then return to the score view to confirm the state updated.

Success check: The recommendation is resolved or you know why it remains open.

Branch questions

Completion check

Recommendations were reviewed individually.
Only applicable changes were made.
The affected workflow was verified after the score changed.

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-score-recommendations
Selected issue: A completed recommendation remains unresolved.
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

Use security score recommendations

Turn security score recommendations into review actions without treating the score as a certification.

Use this guide when the security score recommendations 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 understand recommended actions, decide which ones apply, and verify the result after making changes.

Before You Start

  • Know the account, team, or workspace scope of the score.
  • Treat recommendations as prompts for review.
  • Do not make bulk settings changes without understanding the effect.

1. Read one recommendation at a time

Open the recommendation details and check which workflow it affects before acting.

Check before you continue: You know what the recommendation wants you to change.

2. Decide whether it applies

Some recommendations may not fit your workflow or policy. Apply only the recommendations you understand and are authorised to change.

Check before you continue: The action is appropriate for your workspace.

3. Verify the result

After applying a recommendation, check the affected workflow and then return to the score view to confirm the state updated.

Check before you continue: The recommendation is resolved or you know why it remains open.

Completion Check

  • Recommendations were reviewed individually.
  • Only applicable changes were made.
  • The affected workflow was verified after the score changed.

Safe Examples

  • A masked recommendation label.
  • A synthetic before/after score state.

If You Need Support

Contact support when:

  • A completed recommendation remains unresolved.
  • A recommendation points to a screen you cannot access.

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-score-recommendations
Route: /knowledge-base/security-score-recommendations
Selected issue: A completed recommendation remains unresolved.

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