Project Role Permission for Viewing Execution Logs

Feature Requests
1

The idea is:

I’ve noticed lately that the only users that can view execution log errors are Admins. However, I feel like that within a Project, users should be able to select whether a given Project Role can view those execution logs inside the given project or not.

My use case:

I am an MLOps Engineer and our AI/ML Team has an n8n DEV and PROD instance that is self-hosted as an enterprise edition (we have the bigger version because other BUs in our organization have their own instances of n8n as well).

Our team is deploying its first PROD workflow, but during UAT we’re noticing some intermittent errors retrieving a secret via External Secrets. Unfortunately, I’m the only one able to see the errors while it’s running because I’m an Admin user. I expected the Project Admin, an ML Engineer, to be able to see that themselves, but it seems they are not.

I think it would be beneficial to add this because:

While we are both admins of different scopes, I fully believe that an admin of a Project should be able to view execution logs scoped within their project rather than exclusively relying on the system-wide Admin.

Any resources to support this?

Are you willing to work on this?

2

oi @sswanson-ensono , bem vindo à comunidade n8n.

The docs confirms project-scoped execution permissions, but it is not entirely clear whether full execution logs/error details follow the exact same granularity. That could strengthen the case for an explicit “view execution logs/errors” permission at the Project Role level. To make the feature request more actionable, it would help to include evidence of the current behavior: which role the user has, which screen/error details they cannot access, and whether the execution itself is visible while the logs/details remain hidden. It would also be useful to confirm whether execution data redaction is enabled, since that can affect the visibility of execution data.