Cloud Logging — testIamPermissions succeeds for organization LogView, but entries.list returns 403

We are investigating a Cloud Logging IAM permission inconsistency involving an organization-scoped LogView.

A temporary roles/logging.viewAccessor binding was configured with an IAM condition restricting access to one specific LogView by resource.type, resource.name, and UTC start/expiration times.

The IAM condition was validated successfully.

During the temporary grant:

  • testIamPermissions confirmed logging.views.access on the intended LogView.
  • Control views remained inaccessible.
  • POST /v2/entries:list, using only the intended LogView in resourceNames, returned 403 IAM_PERMISSION_DENIED for logging.views.access.
  • The LogView’s existence had been independently confirmed.

The temporary binding was removed and its absence verified.

Has anyone encountered a difference between IAM permission testing and effective entries.list access to an organization-level LogView?

Are there additional requirements concerning resource context, IAM condition evaluation, or access propagation?

We are seeking a least-privilege solution without granting organization-wide log access.

No sensitive logs or organization identifiers are included.

Check that the request uses the correct LogView path and has the right permissions. Try giving roles/logging.viewAccessor directly to the specific LogView. If it works, the issue may be with the IAM condition.

Reference: Google Cloud – Log Views