Skip to content

docs/abc: Document collaboration roles and whose credentials each action uses - #2171

Open
bahrmichael wants to merge 20 commits into
mainfrom
michaelbahr-cpl-1333-docs-document-abc-collaboration-roles
Open

bahrmichael wants to merge 20 commits into
mainfrom
michaelbahr-cpl-1333-docs-document-abc-collaboration-roles

Conversation

@bahrmichael

@bahrmichael bahrmichael commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Document ABC collaboration: roles, whose credentials each action uses, and the exceptions.

⚠️ Merge after sourcegraph/sourcegraph#19388. The secret approval bullets describe its behavior.

Closes CPL-1333.

Changes

  • New agentic-batch-changes/collaboration.mdx, in sidebar.
  • configuration.mdx (Ownership) and index.mdx: link to it.
  • admin/access-control/batch-changes.mdx: collaborator rows.
  • index.mdx: replace "The agent cannot merge changesets from the conversation." The agent has a merge_changesets tool with an approval card since sourcegraph/sourcegraph#18351 (job.go, merge_changesets.go).

Code references (sourcegraph/sourcegraph 18869d997c)

Generated with an agent.

@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sourcegraph-docs Ready Ready Preview Nov 19, 2026 2:15pm UTC

Request Review

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor
Page Before After Diff
/admin/access-control/batch-changes prod preview −7 +7
/agentic-batch-changes/collaboration 🆕 — preview +82
/agentic-batch-changes/configuration prod preview −1 +1
/agentic-batch-changes prod preview −2 +2

@github-actions

This comment has been minimized.

Co-authored-by: Michael Bahr <1830132+bahrmichael@users.noreply.github.com>
@bahrmichael
bahrmichael marked this pull request as ready for review November 18, 2026 09:50
@bahrmichael
bahrmichael requested review from a team and constantin-cyber November 18, 2026 09:50
…' into michaelbahr-cpl-1333-docs-document-abc-collaboration-roles

Amp-Thread-ID: https://ampcode.com/threads/T-01a1e4d8-de7d-7217-baa1-3fb2338878a6

# Conflicts:
#	docs/agentic-batch-changes/collaboration.mdx

@constantin-cyber constantin-cyber left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few proposals on credential use and access boundaries.

- The agent researches and runs Deep Search as that user. Repository names the agent sees are limited to repositories that both the owner and that user can read.
- Guidance and skills come from that user's settings and from the site and organization settings that apply to them.
- Workspaces and coding agent steps run as that user, with that user's secrets, connectors, and Sourcegraph MCP identity. Coding agent step runs count against that user's [entitlement](/admin/entitlements).
- Tool approvals belong to the user who gave them. An approval from one user does not count for a turn that runs as another user, also when the approval was for this agent or for all agents.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we verify this guarantee for already-prepared plans before rollout? Unchanged steps skip approval, while execution resolves the current actor’s secrets. I propose adding a regression test where A approves the plan and B runs it without having approved secret access.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This branch was successfully deployed

1 active deployment
Preview — 437f26d3 Deployed Nov 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants