Team-owned Automations should support collaborative editing by team members

[T.H]

Feature request for product/service

Background Agent (GitHub, Slack, Linear,…)

Describe the request

Hi Cursor team,

I’d like to request a new permission mode for Automations.

Right now, the current ownership / visibility options are helpful for billing and execution context, but they do not seem to support a true team collaboration workflow.

What I want is:

• Billing / execution should use the team’s shared automation / service account
• Editing should be allowed for multiple team members, not only the original creator or only team admins
• Ideally, this would be configurable as something like:
  • team collaborative editing
  • editable by all team members
  • editable by selected members / groups
  • editable by admins only

Why this matters

In many teams, an automation is not “owned” by one person in practice.

Examples:

• A deployment or triage automation is created by one engineer, but later maintained by another
• A workflow is used operationally by the whole team, so editing should not depend on a single original owner
• We want the automation to be team-billed and team-executed, while still being maintainable collaboratively

At the moment, team-owned is useful for charging and team-level execution, but it would be much better if it also supported shared editing / maintenance.

Suggested model

It may help to separate permissions into two axes:

1. Execution / billing owner

   • personal
   • team service account

2. Edit permissions

   • creator only
   • admins only
   • all team members
   • selected team members / groups

That would make Automations much easier to operate as shared team infrastructure.

Would love to know if something like this is already planned.

Thanks!

[mohitjain (Mohit)]

Hi @T.H,

Thanks for the detailed feature request. The two-axis model you’ve described (billing/execution vs. edit permissions) is a really clean way to frame the need.

You’re correct about the current behavior: the Automations permissions model today supports three scopes (Private, Team Visible, Team Owned), and in Team Owned mode, only team admins can manage the automation. There is no way to grant non-admin members edit access while keeping the automation team-billed.

I’ll make sure this feedback is noted. The use cases you’ve outlined (handoff between engineers, operationally shared workflows) are clear and well-articulated. No timeline to share at this point, but the request is tracked.

[Soph11]

+1000. Because of this limitation, all feedback on the automation goes through the creator/admins who are then responsible for maintaining it, which creates unnecessary friction.

[T.H]

Hi @mohitjain, Thank you. The new Team editable option fixes the collaboration issue I described. Really appreciated.