Document sharing agents and whose access what they use runs with

A new "Sharing agents and what they use" section covers viewers and
editors, whose access each tool, source and prompt runs with as the share
dialog labels it, sponsors, stopped resources, what API, widget and
public-link users can't do without the write allowlist, the wiki switch
and research steps. The sharing rules now mention the editor switches and
member-mode tools, the guardrails page no longer says editors can't
change guardrails, the connector guide uses the new tool share labels,
and related pages link to the section.
This commit is contained in:
arc53-machine committed 2026-09-29 17:35:17 +01:00
1 parent 05bac6dc7f
commit da75845fcf
5 files changed
+35 -8

No files matched your search

+4 -2
View File
@@ -42,8 +42,10 @@ If a provider rejects a token that DocsGPT cannot refresh, the connection is mar
Sharing a tool that uses a connection asks whose account team members use:
- **Team members use my account.** Everyone acts as your account on that service. When the tool can write, you confirm this before sharing, and a member's write actions always need approval.
- **Each member connects their own account.** Members see a **Connect** prompt the first time they use the tool.
- **Your account.** Everyone acts as your account on that service. When the tool can write, you confirm this before sharing, and a member's write actions always need approval.
- **Each person's own.** Each person uses their own account, and sees a **Connect** prompt the first time they use the tool.
An editor you let share the tool sees your choice as **The owner's account** and can't change it. An agent's share dialog shows the same words for each connected tool on the agent (see [Sharing agents and what they use](/Deploying/Access-Control#sharing-agents-and-what-they-use)).
Tools from OAuth MCP servers default to each member's own account. An admin can force one mode for a connector.