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 non-admin users blocked from Services list and Ingestion Runner field despite correct backend permissions #31783
Two related UI permission-gating bugs prevent domain-scoped non-admin users from accessing features that the backend already permits. Direct API testing (GET/POST) confirms correct backend permission enforcement in both cases below — these are frontend-only defects.
Database Services list page shows "No permission"
A non-admin user with a hasDomain()-scoped ViewAll permission on databaseService sees "No permission" when navigating to Settings → Services → Databases, even though their domain matches services in the list.
Ingestion Runner dropdown never renders for non-admins
In the create/edit database service form, the "Ingestion Runner" dropdown never renders for a non-admin user, at any permission level (unconditional, +ViewBasic, hasDomain()-scoped, fully unconditional).
To Reproduce
Bug 1:
Create a role with ViewAll on databaseService, scoped via a hasDomain() condition.
Assign the role to a non-admin user in that domain.
Log in as that user and navigate to Settings → Services → Databases.
Observe "No permission" error, despite GET /permissions returning conditionalAllow and matching services existing in the domain.
Bug 2:
As a non-admin user with create/edit permission on a database service (any grant level), open the create or edit service form.
Observe the "Ingestion Runner" dropdown is not shown, at any permission level.
Directly POST a service payload with ingestionRunner and domains set as this non-admin user — the request succeeds and both fields persist.
Expected behavior
The Services list page should render and show services within the user's domain when the backend permission is conditionalAllow, with visibility of individual services still governed by domain-scoping at the instance level.
The Ingestion Runner field should render based on the user's actual permission to create/edit the service, not a hardcoded admin check.
OS
No response
Python version
No response
OpenMetadata version
1.13.3
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
kn-dev-code commentedon Aug 19, 2026
Hi @jnrimjhim, I can work on this issue
zhang-arvin commentedon Aug 20, 2026
I would like to work on this issue.
refactor(ui): centralize permission derivation behind useEntityPermis…
fix(permissions): use view-only conditional allow at resource level (#…
test(playwright): cover the domain-scoped Database Services list (ope…
fix(ui): treat resource-level conditionalAllow as permitted for View …
fix(ui): treat resource-level conditionalAllow as permitted for View …
fix(ui): treat resource-level conditionalAllow as permitted for View …
fix(ui): treat resource-level conditionalAllow as permitted for View …
fix(ui): treat resource-level conditional access as permitted for Vie…
fix(ui): treat resource-level conditional access as permitted for Vie…
fix(ui): treat resource-level conditional access as permitted for Vie…
sonika-shah commentedon Nov 5, 2026
Status on latest main:
Services list shows "No permission" for a user whose access is a domain-scoped (
hasDomain()) policy/permissionsfirst and treat a conditional answer as "no", so the list API is never called. They need to call the list and let the backend decide. Fixes #33834, #31783 & #33356 - [RBAC W1] Domain-scoped RBAC View over pages #34091 is the open PR in this direction.paging.totalstill counts all rows, not only readable ones.Ingestion Runner field not shown to non-admins with add/edit permission: fixed, released in 1.13.5.
Keeping this open until the UI part of point 1 lands.