DOCS-1787 - Clarify Feature Management access paths for MSSP orgs - #6979
Open
kimsauce wants to merge 2 commits into
Open
DOCS-1787 - Clarify Feature Management access paths for MSSP orgs#6979kimsauce wants to merge 2 commits into
kimsauce wants to merge 2 commits into
Conversation
MSSP parent orgs don't see the AI features/MCP Server access toggles on their own Feature Management page, but the docs never explained where MSSP admins actually go instead, causing customer confusion in an EMEA support escalation. Cross-links the AI docs (Mobot, SOC Analyst Agent, AI/ML overview, MCP server) to the existing MSSP "Manage features" flow, names the exact permissions involved (Manage Organizations vs. Manage Organization Settings), and notes that Support account users can't manage child-org AI settings from an MSSP parent org. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ndhar-sumo
reviewed
Aug 3, 2026
|
|
||
| As an MSSP administrator, you can manage feature availability for your child organizations directly from the Organizations UI. This allows you to opt in or opt out individual child organizations from specific Sumo Logic features without needing to contact Sumo Logic support. | ||
|
|
||
| This includes the **AI features** toggle (Mobot, Parse Assist, and the SOC Analyst Agent) and the **MCP Server access** toggle — see [AI and Machine Learning with Sumo Logic](/docs/get-started/ai-machine-learning/#can-i-opt-out-of-ai-features). Unlike standalone orgs, MSSP parent orgs don't see these toggles on their own **Feature Management** page; manage them per child org here instead. |
Collaborator
There was a problem hiding this comment.
"App Catalog" is a toggle offered as well.
Collaborator
Author
There was a problem hiding this comment.
@ndhar-sumo I don't see that on my end. Can you confirm where I can find it?
Collaborator
There was a problem hiding this comment.
This is just for Mssp parent Org UI. See snapshots:
Collaborator
Author
@ndhar-sumo thanks for the quick turnaround |
Resolve conflict in mcp-server.md: keep the now-uncommented Micro Lesson block from main plus this branch's MSSP cross-link addition to the Enable/disable MCP server section.
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
2 participants
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.
Purpose of this pull request
MSSP parent orgs don't see the AI features / MCP Server access toggles on their own Feature Management page, but none of the AI docs explained where MSSP admins actually go instead — this caused real customer confusion in an EMEA support escalation (internal Slack thread, confirmed by Neha Dhar).
This PR:
Administration > Organizations > Manage Account> child org >Manage Features).role-capabilities.md.manage-orgs-for-mssps.mdconfirming AI features / MCP Server access are among the manageable features there.Out of scope:
role-capabilities.md's "Manage Organization Settings" row description doesn't currently mention Feature Management access. Left that alone pending separate confirmation with Neha, rather than assume it's accurate.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1787