docs: clarify agent share/public permission semantics for agents and remote agents#695
Open
Educg550 wants to merge 1 commit into
Open
docs: clarify agent share/public permission semantics for agents and remote agents#695Educg550 wants to merge 1 commit into
Educg550 wants to merge 1 commit into
Conversation
Explain that share grants the SHARE permission but that picking specific users depends on the VIEW_USERS people-picker permission, so specific-user sharing is usually an admin concern. Non-admins with share can still target the groups and roles they can see and toggle public when allowed. Rewrite the share/public sub-key descriptions, add a "How share and public work" section covering principal types and the built-in roles, cross-link remoteAgents to it, and align the SHARE vs SHARE_PUBLIC note in access_control.
|
@Educg550 is attempting to deploy a commit to the LibreChat's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
Explain that share grants the SHARE permission but that picking specific users depends on the VIEW_USERS people-picker permission, so specific-user sharing is usually an admin concern. Non-admins with share can still target the groups and roles they can see and toggle public when allowed.
Rewrite the share/public sub-key descriptions, add a "How share and public work" section covering principal types and the built-in roles, cross-link remoteAgents to it, and align the SHARE vs SHARE_PUBLIC note in access_control.