Self-hosted: Query/Dashboards routes work, but Observability menu is hidden unless org has hasQueryAccess

[shrinidhi4u]

On self-hosted Trigger v4.4.4, the Query and Dashboards pages are accessible by direct URL, but the Observability sidebar section can still be hidden.

What happened:

• /orgs/:org/projects/:project/env/:env/query loads
• /orgs/:org/projects/:project/env/:env/dashboards/overview loads
• but the sidebar does not show Query/Dashboards unless the org feature flag hasQueryAccess is set

Why this seems inconsistent:

• route access appears to be allowed by QUERY_FEATURE_ENABLED / runtime access checks
• sidebar visibility appears to depend on organization.featureFlags.hasQueryAccess

In our case this made the feature look broken even though the pages existed and worked.

There was a second related issue:

• /admin/* was inaccessible for a GitHub-auth user even though ADMIN_EMAILS matched the email
• after checking the code, it looks like admin is assigned on create for magic-link users, but GitHub user creation does not set admin the same way
• after manually setting User.admin = true in Postgres, we could access admin feature flags and set hasQueryAccess, which made the menu appear

Questions:

1. Should sidebar visibility use the same access logic as the route?
2. Should GitHub-auth users matching ADMIN_EMAILS be granted platform admin on create as well?
3. Is this expected behavior or a bug?

[matt-aitken]

Thanks @shrinidhi4u. Answers below:

1. We intentionally do it like this while a feature is still in preview. It makes it easy to give access through direct URLs to specific customers.
2. We should add support for this, could you create a separate GitHub issue?

I have on my list to remove the query feature flag now it’s been public and well tested for a while.