Docs/accessanalyzer sharepoint permissions dedupe 11 6 12 0 20260219#406
Docs/accessanalyzer sharepoint permissions dedupe 11 6 12 0 20260219#406
Conversation
Expand access.md into a canonical permissions reference covering all required SharePoint permissions for Enterprise Auditor: application server (agent-less only), farm, web application, database, and MySites/OneDrive. Adds Overview section, Application server permissions from agentlesspermissions.md, and MySites/OneDrive section. Applies style guide: numbered steps, sentence-case headings, backticks for technical identifiers, bold UI elements. Fixes ShaerPoint_Config typo. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…s and add cross-links Remove duplicated farm, web application, and database permission configuration steps from agentlesspermissions.md. Replace with a cross-reference to the canonical permissions page (access.md). Update overview.md link text to match the new canonical page title. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Expand access.md into a canonical permissions reference covering all required SharePoint permissions for Access Analyzer: application server (agent-less only), farm, web application, database, and MySites/OneDrive. Adds Overview section, Application server permissions from agentlesspermissions.md, and MySites/OneDrive section. Applies style guide: numbered steps, sentence-case headings, backticks for technical identifiers, bold UI elements. Fixes ShaerPoint_Config typo. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…s and add cross-links Remove duplicated farm, web application, and database permission configuration steps from agentlesspermissions.md. Replace with a cross-reference to the canonical permissions page (access.md). Update overview.md link text to match the new canonical page title. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| Enterprise Auditor to call the SharePoint web services to gather permissions, site hierarchy, and | ||
| content information remotely. | ||
|
|
||
| Follow these steps to configure farm-level permissions on SharePoint 2013 through SharePoint 2019: |
There was a problem hiding this comment.
[Netwrix.FollowTheStepsTo] Avoid 'Follow these steps to'. Use a direct heading and numbered list instead.
| permissions at the web application level. This allows Enterprise Auditor to execute web service | ||
| calls against **Central Administration**. | ||
|
|
||
| Follow these steps to configure web application-level permissions on SharePoint 2013 through |
There was a problem hiding this comment.
[Netwrix.FollowTheStepsTo] Avoid 'Follow these steps to'. Use a direct heading and numbered list instead.
|
|
||
| Follow the steps to configure the SharePoint database server permissions on SharePoint 2013 through | ||
| SharePoint 2019 farms. | ||
| Follow these steps to configure database server permissions: |
There was a problem hiding this comment.
[Netwrix.FollowTheStepsTo] Avoid 'Follow these steps to'. Use a direct heading and numbered list instead.
| Access Analyzer to call the SharePoint web services to gather permissions, site hierarchy, and | ||
| content information remotely. | ||
|
|
||
| Follow these steps to configure farm-level permissions on SharePoint 2013 through SharePoint 2019: |
There was a problem hiding this comment.
[Netwrix.FollowTheStepsTo] Avoid 'Follow these steps to'. Use a direct heading and numbered list instead.
| permissions at the web application level. This allows Access Analyzer to execute web service calls | ||
| against **Central Administration**. | ||
|
|
||
| Follow these steps to configure web application-level permissions on SharePoint 2013 through |
There was a problem hiding this comment.
[Netwrix.FollowTheStepsTo] Avoid 'Follow these steps to'. Use a direct heading and numbered list instead.
|
|
||
| Follow the steps to configure the SharePoint database server permissions on SharePoint 2013 through | ||
| SharePoint 2019 farms. | ||
| Follow these steps to configure database server permissions: |
There was a problem hiding this comment.
[Netwrix.FollowTheStepsTo] Avoid 'Follow these steps to'. Use a direct heading and numbered list instead.
There was a problem hiding this comment.
Issues in PR changes
docs/accessanalyzer/11.6/requirements/sharepoint/sharepoint/sharepoint/access.md
Line 75: Passive voice. "The service account is provisioned as" should use active voice per the style guide requirement "Always use active voice rather than passive voice." Change to "The service account now has Site Collection Auditor privileges on" for consistency with line 45.
Line 94: Passive voice. "The service account is provisioned with" should use active voice per the style guide requirement. Change to "The service account now has" for consistency with line 45.
docs/accessanalyzer/12.0/requirements/sharepoint/sharepoint/sharepoint/access.md
Line 75: Passive voice. "The service account is provisioned as" should use active voice per the style guide requirement "Always use active voice rather than passive voice." Change to "The service account now has Site Collection Auditor privileges on" for consistency with line 45.
Line 94: Passive voice. "The service account is provisioned with" should use active voice per the style guide requirement. Change to "The service account now has" for consistency with line 45.
To apply suggested fixes to the updated documentation, individually or in bulk, comment @claude on this PR followed by your instructions (@claude fix all issues or @claude fix all linting issues or @claude fix only the spelling errors).
To review the updated documentation for preexisting issues, comment @claude on this PR followed by your instructions (@claude detect preexisting issues).
Note: Automated fixes are only available for branches in this repository, not forks.
| then click **Finish**. | ||
| 6. Repeat step 5 for each web application in scope. | ||
|
|
||
| The service account is provisioned as `Site Collection Auditor` on all web applications to be |
There was a problem hiding this comment.
| The service account is provisioned as `Site Collection Auditor` on all web applications to be | |
| The service account now has `Site Collection Auditor` privileges on all web applications to be |
| databases begin with `WSS_Content`, but they can be customized) | ||
|
|
||
| **Step 2 –** Provision the service account to have: | ||
| The service account is provisioned with the required SharePoint database permissions. |
There was a problem hiding this comment.
| The service account is provisioned with the required SharePoint database permissions. | |
| The service account now has the required SharePoint database permissions. |
| then click **Finish**. | ||
| 6. Repeat step 5 for each web application in scope. | ||
|
|
||
| The service account is provisioned as `Site Collection Auditor` on all web applications to be |
There was a problem hiding this comment.
| The service account is provisioned as `Site Collection Auditor` on all web applications to be | |
| The service account now has `Site Collection Auditor` privileges on all web applications to be |
| databases begin with `WSS_Content`, but they can be customized) | ||
|
|
||
| **Step 2 –** Provision the service account to have: | ||
| The service account is provisioned with the required SharePoint database permissions. |
There was a problem hiding this comment.
| The service account is provisioned with the required SharePoint database permissions. | |
| The service account now has the required SharePoint database permissions. |
1 participant
No description provided.