Batch Changes permissions

Created by: malomarrec

Context

Currently, Batch Changes permission model works like documented here. In a nutshell:

• there are two levels of access: read and admin
• all users can read all batch changes.
• the batch change creator and site-admins have admin access to it
• having read access to a batch change does not give you read access to the changesets it contains. You can only view changesets you have view access to according to repository permissions.
• there are two namespaces, the user's and the org's. All users in an org are admin of a batch change in the org's namespace.

Problem

This permission model is insufficient:

• in security use cases, the security team might want to keep a batch change private to only one person or their team.

Customer issues and impacted customers

Also see this product gap

This issue needs feedback. If you encounter an instance of this, please document it in the comments or privately and link back here.

Proposed solution

We are in the process of collecting additional feedback on this issue.