> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Navigation and page access

> Why a Forge Console sidebar item is hidden, grayed out, or opens a refusal: permissions, the admin role, and feature flags.

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:

| Cause | What you see | What it means |
| - | - | - |
| You do not hold every permission the item requires | The item is **not shown** in the sidebar, the tab bar, or the command palette | The page reads data the server only returns to holders of all its required permissions |
| A feature flag is off | The item is shown **grayed out** and labelled "Feature not enabled" | The feature is switched off for your workspace. It has nothing to do with your permissions |
| A feature flag is off and the item opts out of graying | The item is not shown | Same as above, for the few items that hide instead |
| The page has no sidebar entry by design | The page is not in the sidebar or a tab bar. It opens from another page, the command palette (`⌘K` / `Ctrl+K`), or its URL | Nothing is missing. These docs list such a page under the entry that opens it: **Skill Sets** under **Skills**, **Graph Builder (v2)** under **Workflows** |

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.

> [!NOTE]
>
> 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

> [card] [Policies](https://docs.gloo.com/forge/console/trust-fabric/policies.md)
>
> Review the governance policies that decide what agents and people may do.

> [card] [Using help](https://docs.gloo.com/forge/console/help.md)
>
> Get guidance for the page in front of you.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.