Document SharePoint sharing settings required for Visible for - #422
Merged
Conversation
Adds a new "SharePoint sharing settings required for Visible for" section to permissions-in-sharepoint.mdx, with a cross-reference from the service account section. Adds short warning callouts pointing to it from the SharePoint documents overview page (Things to consider, Data rights for a role).
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The changes are documentation-only and low risk, with only minor readability/duplication nits to consider.
Pull request overview
This PR updates the SharePoint Documents documentation to clearly explain a critical SharePoint site sharing prerequisite for using Visible for safely, and adds cross-references from other relevant pages so admins can find and validate the required configuration.
Changes:
- Adds a new detailed section in
permissions-in-sharepoint.mdxexplaining why SharePoint sharing settings must allow members/Edit users to share files/folders for Visible for to work. - Adds short warning/cross-reference callouts from the overview, configuration wizard, requirements, and troubleshooting pages pointing to the new section.
- Updates page metadata (author/date) for the edited docs.
File summaries
| File | Description |
|---|---|
| integrations/sharepoint-documents/troubleshooting.md | Adds a new troubleshooting entry for 403 / restrictions not being applied, linking to the new SharePoint sharing settings section. |
| integrations/sharepoint-documents/requirements.mdx | Adds an explicit prerequisite bullet pointing to the sharing settings requirements for Visible for. |
| integrations/sharepoint-documents/permissions-in-sharepoint.mdx | Introduces the primary detailed guidance section (explanation, required configuration, validation, symptoms/resolution). |
| integrations/sharepoint-documents/index.mdx | Adds warning callouts on the overview page that link to the new detailed section. |
| integrations/sharepoint-documents/configure-superoffice.mdx | Adds a warning in the configuration flow to verify the SharePoint sharing setting before enabling Visible for. |
Review details
- Files reviewed: 5/5 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…r-sharing-settings # Conflicts: # integrations/sharepoint-documents/troubleshooting.md
- Remove index.mdx's duplicate <Warning> block (same content pasted twice) and extract the remaining one into a shared snippets/warn-sharing-settings-required.mdx, matching this repo's existing caution-/warn- snippet convention. - Give it its own heading in index.mdx so it no longer stacks directly under the page's <Danger> callout, per the house style rule against stacked call-outs. - Trim the redundant Troubleshooting subsection out of permissions-in-sharepoint.mdx in favor of linking to troubleshooting.md's equivalent entry. - Standardize *Visible for* to italic (the dominant convention) instead of bold in the two new Warning blocks. - Reword "tick"/"ticked" to "select"/"cleared" on configure-superoffice.mdx to match Microsoft style guidance for checkbox interactions. - Shorten the new heading anchor to #visible-for. - Use a reference-style link in the new snippet instead of inline.
This reverts commit cbe5464.
digitaldiina
previously approved these changes
Sep 9, 2026
digitaldiina
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the clarifying warning, @schildea. I extracted it to a snippet for reuse.
added 2 commits
September 9, 2026 09:35
…r-sharing-settings
…ettings' into sharepoint-visible-for-sharing-settings
This reverts commit 559a849.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
share files and folders when using Visible for — otherwise SuperOffice
can't apply the restriction, and documents can end up more widely
accessible than intended.
this is required, the required configuration, validation steps, and
troubleshooting.
overview page, the configuration wizard, the requirements page, and the
troubleshooting page, all pointing to that new section.