Skip to main content
The Forge Console filters navigation with the current navigation registry. When an item carries a permission, the corresponding page is expected to refuse without that permission too. Navigation is still presentation: the server remains the authority, and some pages keep an administrator gate or apply stronger checks to individual controls.

What decides whether an item appears

Four things affect a navigation item, and each one looks different: An item without a navigation permission can still contain controls that require stronger access. Navigation is presentation, not enforcement: the server checks every protected read or write.
While the Console is still confirming your session, every item is shown. The sidebar then settles to the items you can open, so it never appears empty on first load.

What you see when you open a page you cannot use

If you open a gated page directly, for example from a bookmark or a shared link, the page shows an Access restricted notice in place of its content. The notice names what the page needs:
  • A permission, such as audit:read or policies:read on Trust Fabric pages or workforce:read on Workforce Structure. Ask an administrator to grant it to you.
  • Several permissions together, such as grants:read, policies:read, and audit:read on Observe → Logs. You need all three to open Logs, and its navigation item uses the same requirements.
  • The Console administrator gate, on pages that still use it while their page-level gates are reviewed individually, including the administrator analytics and platform operations pages.
  • The review queues’ own permissions: Synthesis and Admissions open with platform:read, and their decision controls appear only with synthesis:approve; Curator Queue needs synthesis:approve.
While the Console is confirming your session, the page shows a loading placeholder instead of the notice, so a page you can use never flashes a refusal first. Opening Platform → Schedules without the administrator role redirects you to Production → Workflows → Schedules (/production/workflows/convex/schedules), where you manage workflow-scoped schedules.

Pages whose controls need stronger access

A page can be readable while an action on it is unavailable. Current examples include Synthesis, where platform:read opens the queue and synthesis:approve enables decisions, and Trust Fabric → Policies, where policy management is stronger than reading the catalog. Read the refusal or disabled control for the permission that applies to that action; do not infer write access from a visible page.

Where to go next

Policies

Review the governance policies that decide what agents and people may do.

Using help

Get guidance for the page in front of you.