Skip to content

Commit c267f35

Browse files
committed
docs: correct how a non-admin reveals the Webhooks nav section
The left nav reads only org-level feature flags, so a global FeatureFlag row makes the pages reachable by URL but does not reveal the nav section for a non-admin. Point the onboarding step at the org-level flag.
1 parent 7b8ad85 commit c267f35

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

ONBOARDING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ curl -s http://localhost:3030/healthcheck # verify
8787
The dashboard is gated by a feature flag, `hasWebhooksAccess` (default off).
8888

8989
- The seeded dev user `local@trigger.dev` is an **admin**, and admins bypass the flag, so on a fresh seed the Webhooks nav section is already visible to you. Nothing to do.
90-
- If you use a non-admin user, flip the flag on the org: set `featureFlags.hasWebhooksAccess = true` on the `Organization` row, or add a global `FeatureFlag` row with key `hasWebhooksAccess`.
90+
- If you use a non-admin user, set `featureFlags.hasWebhooksAccess = true` on the `Organization` row to reveal the nav section. (A global `FeatureFlag` row with key `hasWebhooksAccess` makes the pages reachable by URL, but the left nav reads only org-level flags, so the section stays hidden for non-admins.)
9191

9292
If the "Webhooks" section is missing from the left nav, this flag is why.
9393

0 commit comments

Comments
 (0)