> ## Documentation Index
> Fetch the complete documentation index at: https://neuraltrust-92b43583-develop.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs cover three products: TrustGate (AI agent gateway), TrustGuard (runtime security), and TrustTest (AI red teaming). Start from each product overview for the definition and How it works. Prefer the .md URL next to a page in /llms.txt when you need the full article. Use /llms-full.txt for a single-file dump of the site.

# Portal

> The self-service side of MCP: people browse the catalogue, install servers for themselves, connect their own accounts, and ask for what they cannot have — while admins keep the shelf.

Applications are for things your team built. The **Portal** is for people.

Every gateway has one. A person opens it, signs in with their NeuralTrust login,
and sees the catalogue: what they can install, what they already have, and the
state of their own account on each server. Everything they install becomes
available to their agents through one fixed MCP URL — the same catalogue, reached
by a client instead of a browser, with three tools to search, install and
uninstall.

Neither governs applications and applications do not govern it. An application's
surface is what an admin bound; a person's Portal is what they installed, bounded
by their [Access](/trustgate/access/overview) level.

## Installing

Installing a catalogue server creates or reuses **one registry entry per
catalogue code** on the gateway. What is per person lives elsewhere: their
account on a forwarded-auth server, vaulted under their identity, and any
per-user setup values a server's URL is built from.

An install answer is a state, not a success flag:

| State                  | What it means                                                                        | What happens next                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| **Installed**          | Tools are on the Portal's MCP URL now.                                               | Nothing.                                                                                             |
| **Connect**            | The server needs the person's own account.                                           | They open the connect link and sign in once.                                                         |
| **Needs setup**        | The server's address is built from values only they know — a subdomain, a workspace. | They supply them on a hosted form. Secrets are entered only there, never through the tool.           |
| **Choose an instance** | An admin connected several instances.                                                | They pick one.                                                                                       |
| **Request access**     | The server is outside their selection.                                               | They write why, and it goes to [Approvals](/trustgate/access/overview#requests-instead-of-refusals). |
| **Needs admin setup**  | The server wants a shared credential only an admin can add.                          | An admin finishes the registry entry.                                                                |

The person's Portal shows the same states — **Installed**, **Connect**,
**Reconnect needed**, **Pending**, **Needs admin setup** — and under **My Access**
what they hold, with the state of their own account on each.

## Open or curated

A gateway's **default access** decides what the Portal offers everyone who has no
level of their own:

| Default      | Effect                                                                                                                  |
| ------------ | ----------------------------------------------------------------------------------------------------------------------- |
| **All**      | The whole catalogue is browsable and installs instantly. A server with no registry entry yet gets one on first install. |
| **Selected** | Only the shelf and what is granted are browsable; anything else becomes a request.                                      |
| **None**     | The Portal is closed: nothing to browse, installs are refused.                                                          |

A level set on a person or a group overrides the default. The effective level is
evaluated on every request, so a change lands immediately.

Curated is the setting most organisations end at. It is not a refusal of
everything else — it turns "I need this" into a request with a reason attached,
decided by an admin, and approving a group instead of a person is how the same
request stops arriving.

## Reconnecting

A connection is reported as **connected** only while its credential can still be
redeemed. When a provider stops honouring the refresh, the person sees
**Reconnect needed** and the server contributes no tools until they sign in
again. The gateway never replays a refresh token a provider already rejected.

## Instances

A server that can be connected more than once — two Snowflake schemas, two API
keys — holds instances, added by admins from the registry. When several exist the
Portal asks which one to install or uninstall, and each holds its own set of
per-user accounts.

## Where it is

The Portal's MCP URL is under the gateway's settings, next to the LLM and MCP
gateway URLs. Employees without console access reach the Portal from the platform; admins
can preview it as any user from [Access](/trustgate/access/overview#seeing-what-someone-else-sees).