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

**URL:** <https://discuss.google.dev/t/cloud-logging-testiampermissions-succeeds-for-organization-logview-but-entries-list-returns-403/409478>\
**Category:** Cloud Foundations & Onboarding\
**Tags:** cloud-logging\
**Created:** [October 30, 2026, 12:52pm UTC](https://discuss.google.dev/t/cloud-logging-testiampermissions-succeeds-for-organization-logview-but-entries-list-returns-403/409478 "2026-10-30T12:52:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![VICTOR\_FERREIRA\_DIAS](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/victor_ferreira_dias/32/286457_2.png) [@VICTOR\_FERREIRA\_DIAS](https://discuss.google.dev/u/VICTOR_FERREIRA_DIAS)\
**Post date:** [October 30, 2026, 12:52pm UTC](https://discuss.google.dev/t/cloud-logging-testiampermissions-succeeds-for-organization-logview-but-entries-list-returns-403/409478/1 "2026-10-30T12:52:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Ad.Guide](https://d3byx8b92xw3lq.cloudfront.net/user_avatar/discuss.google.dev/ad.guide/32/287371_2.png) [@Ad.Guide](https://discuss.google.dev/u/Ad.Guide)\
**Post date:** [November 6, 2026, 4:57pm UTC](https://discuss.google.dev/t/cloud-logging-testiampermissions-succeeds-for-organization-logview-but-entries-list-returns-403/409478/2 "2026-11-06T16:57:33Z")

</div>

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](https://docs.cloud.google.com/logging/docs/logs-views)
