Skip to content

docs(platgovsalesforce): update permission set assignment requirements AB#426233#758

Merged
claudi-dev merged 5 commits intodevfrom
feature/419088
Apr 14, 2026
Merged

docs(platgovsalesforce): update permission set assignment requirements AB#426233#758
claudi-dev merged 5 commits intodevfrom
feature/419088

Conversation

@claudi-dev
Copy link
Copy Markdown
Contributor

Summary

  • Added clarification that the Permission Set must also be assigned to users running scheduled jobs or background processes
  • Added explanation of why this is required (metadata scanning and automated operations)

Files changed

  • docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md

@claudi-dev claudi-dev requested a review from a team as a code owner April 14, 2026 19:21
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md

  • Clarity — Line 79: "This is required because..." opens with a vague pronoun — it's not immediately clear what "This" refers to (assigning the Permission Set to all the named user categories). Suggested fix: "The Permission Set is required for these users because it grants access to..."

  • Clarity — Line 79: "grants access to the data and system processes" is an awkward pairing — you access data, but you run or execute processes. Suggested fix: "grants access to the data and processes used by Platform Governance"

  • Clarity — Line 79: "other automated operations" is vague and adds no useful information for the reader. Suggested fix: Either enumerate the specific operations or remove the phrase: "...including metadata scanning."

  • Completeness — Lines 77–79: The PR adds that users running scheduled jobs or background processes also need the Permission Set, but provides no guidance on how to identify those users. A reader following this installation procedure would not know which user accounts qualify. Suggested fix: Add a note directing readers where to look — for example: "To identify which users run scheduled jobs, navigate to Setup > Scheduled Jobs and note the user listed in the Submitted By column."

Summary

4 editorial suggestions across 1 file. Vale and Dale issues are auto-fixed separately.


What to do next:

Comment @claude on this PR followed by your instructions to get help:

  • @claude fix all issues — fix all editorial issues
  • @claude help improve the flow of this document — get writing assistance
  • @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

Auto-Fix Summary

22 issues fixed, 2 skipped across 1 files

Category Fixes
Contractions 4
FirstPersonPlural (rewrite) 3
Dale: passive-voice 12
Dale: wordiness 3
Skipped (needs manual review) Reason
docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md:83 — Netwrix.SetupUsage 'Setup' is the name of the Salesforce admin UI page (proper noun), not the verb form — no fix needed
docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md:102 — Netwrix.SetupUsage 'Setup' is the name of the Salesforce admin UI page (proper noun), not the verb form — no fix needed

Ask @claude on this PR if you'd like an explanation of any fix.

Copy link
Copy Markdown
Contributor

@lferreronetwrix lferreronetwrix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@claudi-dev claudi-dev merged commit 8312400 into dev Apr 14, 2026
10 checks passed
@claudi-dev claudi-dev deleted the feature/419088 branch April 14, 2026 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants