Skip to content

Domain-scoped non-admin users blocked from Services list and Ingestion Runner field despite correct backend permissions #31783

Description

@jnrimjhim

Affected module

UI

Describe the bug

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.

  1. 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.

  2. 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:

  1. Create a role with ViewAll on databaseService, scoped via a hasDomain() condition.
  2. Assign the role to a non-admin user in that domain.
  3. Log in as that user and navigate to Settings → Services → Databases.
  4. Observe "No permission" error, despite GET /permissions returning conditionalAllow and matching services existing in the domain.

Bug 2:

  1. As a non-admin user with create/edit permission on a database service (any grant level), open the create or edit service form.
  2. Observe the "Ingestion Runner" dropdown is not shown, at any permission level.
  3. Directly POST a service payload with ingestionRunner and domains set as this non-admin user — the request succeeds and both fields persist.

Expected behavior

  1. 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.
  2. 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

  1. kn-dev-code commented on Aug 19, 2026

    @kn-dev-code

    Hi @jnrimjhim, I can work on this issue

  2. zhang-arvin commented on Aug 20, 2026

    @zhang-arvin
    Contributor

    I would like to work on this issue.

  3. added theissue type on Aug 26, 2026
  4. added this to Shipping and removed this from Roadmapon Aug 26, 2026
  5. moved this to Release Backlog 🚧 in Shippingon Aug 26, 2026
  6. added a commit that references this issue on Sep 11, 2026
    b5319ed
  7. moved this from Release Backlog 🚧 to In Review / QA 👀 in Shippingon Oct 28, 2026
  8. sonika-shah commented on Nov 5, 2026

    @sonika-shah
    Collaborator

    Status on latest main:

    1. Services list shows "No permission" for a user whose access is a domain-scoped (hasDomain()) policy

    2. 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.

  9. added this to the 2.2 Release - Wave 1 milestone on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

UIUI specific issuesbugSomething isn't working

Type

Projects

  • Status
    No status
  • Status
    In Review / QA 👀

Relationships

None yet

Development

No branches or pull requests

Issue actions