What you see depends on what is installed
Stacklok Enterprise has one tier. There are no editions, no per-feature entitlements, and no administrator-facing feature flags to switch things on.
What any given person sees in the console is decided by two things: which components you installed, and what that person is allowed to do. Nothing else.
Why a section is missing
Each area of the console is backed by a service. The navigation only offers an area when its service is both installed and reachable, and the route behind it is gated the same way, so a hidden link and its page can never disagree. Follow a stale bookmark to an area whose service is not installed and you get a not-found response rather than a broken page.
The practical consequence: if an administrator cannot see Connectors, the answer is almost never permissions. It is that the MCP gateway is not enabled in the platform chart, or it is enabled but not answering.
| Console area | Requires |
|---|---|
| Organization spend, Budgets, Model usage | The AI Gateway |
| Connectors, Tool usage | The MCP gateway |
| User management, Identity providers, Managed secrets | The directory service |
Both gateways are off by default. See Configure the AI Gateway and Configure the MCP gateway.
Why an area is visible but empty
Installed and reachable is not the same as configured. A visible area with no content usually means the service is running and has nothing to show yet: no connectors registered, no budgets created, no traffic recorded. The console says so in place rather than hiding the section, because an empty list and an uninstalled component are different problems with different fixes.
The two consoles
Signing in lands you in one of two experiences. The user experience covers your own work: the connectors available to you, your own model and tool usage, your own API keys. The administration experience covers the organization: spend, budgets, connector registration, users, and groups.
Administrators can switch between them from the account menu. Someone with no administrative access simply never sees the administration side, which is a permissions boundary rather than a navigation preference.
What this means for rollout
Because visibility follows installation, you can bring the platform up in stages, and each stage is self-describing: install a component, and its areas appear for the people entitled to them. There is no separate step to reveal a feature after deploying it, and no flag to forget.
Related information
- The two group models, the other thing that decides what someone can reach.
- Deploy the platform for the install sequence and its toggles.