You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Domain-scoped "Domain Only Access Role" blocks glossary term page access despite assets appearing correctly in RBAC-enabled search #33356
A user with a Domain Only Access Role assigned is unable to view a glossary term page when that term's domain matches the user's assigned domain, and receives a permissions error. Notably, the same domain-scoped asset does appear correctly when the user performs a search with RBAC enabled — indicating the search-layer permission evaluation and the glossary term detail-page permission evaluation are inconsistent.
To Reproduce
Assign a domain to a Glossary Term.
Create/assign a user the Domain Only Access Role, scoped to that same domain.
As that user, perform a search — confirm the domain-scoped glossary term/asset appears correctly in RBAC-enabled search results.
As that user, navigate directly to the Glossary Term page for that same term.
Observe a permissions error is shown, despite the user having domain access to that term.
Expected behavior
A user with Domain Only Access Role scoped to a domain should be able to view glossary term pages for terms within that domain — consistent with what they can already see via RBAC-enabled search.
OS
No response
Python version
No response
OpenMetadata version
2.0.1
OpenMetadata Ingestion package version
No response
Additional context
No response
Pre-submission checklist
I searched for duplicate issues.
I removed credentials, hostnames, emails, and other sensitive data from logs and config.
Activity
Prakhar-Mishra1107 commentedon Sep 15, 2026
Hi Team, I have faced similar issue, instead of domain level access, I was trying to with owner/team level access but was getting permissions error.
fix(permissions): use view-only conditional allow at resource level (#…
fix(ui): treat resource-level conditional access as permitted for Vie…
fix(ui): treat resource-level conditional access as permitted for Vie…
anuj-kumary commentedon Oct 1, 2026
Closing this issue as it is not reproducible. It seems to have been fixed in the latest release, 2.0.3.