Manage automations as a Project Admin

Project Admins can now create, edit, dry-run, enable, disable, delete, and inspect Activity for automation rules in their project. Open the project’s Automations view to start. The same permissions apply to humans, project agents, and personal agents with inherited access.

Project Admin rules stay in one project. They cannot change scope, create tasks in another project, or send webhooks. An existing rule with privileged actions can still be stopped or deleted; an organization owner or admin must edit, test, or enable it.

Project rules continue within their saved boundary after their creator loses project access. Explicit agent lifecycle stops and project archives still stop execution. Creator attribution is retained. Organization-wide management remains in Settings for organization owners and admins.