Issue Summary

Rovo Studio automations and their audit logs are visible to all users with Studio access. Unlike Jira/Confluence automations, there are no fine-grained permissions to restrict viewing to owners or admins.

Steps to Reproduce

1. Create a Studio automation that processes sensitive data (e.g., {}{{issue.description{}}}).

1. Trigger the automation to generate an audit log.

1. Log in as a standard user (non-owner/non-admin) with Studio access.

1. Navigate to the automation's Audit log.

Expected Results

Access to automation configurations and audit logs should be restricted to the Owner and Admins by default.

Actual Results

Standard users can view the full automation logic and all sensitive data captured in the audit logs.

Workaround

Removing Studio access entirely is the only option, which is not viable for organizations actively rolling out Rovo.