> ## 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.

# Roles

> Every Forge role as a card: the core ladder of person roles, what each role is for and where it may be given, who holds it, and a comparison of any two roles.

**Roles** (`/trust-fabric/access/roles`) is the second tab of [Access](https://docs.gloo.com/forge/console/trust-fabric/access). It shows every role as a
card and compares any two roles. It needs See roles (`roles:read`), which the Base role includes.
The old roles page at `/platform/members/roles` redirects here.

![Access → Roles (light)](https://mintcdn.com/gloo-b243725a/Ndtg9NEpwGc2OULA/forge/images/console/trust-fabric/access-roles-light.png?fit=max\&auto=format\&n=Ndtg9NEpwGc2OULA\&q=85\&s=25f17cf4e3deedaa93737605cf53e396)

Access → Roles — Forge Console at `/trust-fabric/access/roles`

## What you can do

* **Read the core ladder.** See how Base, Builder and Operator build on each other, and what each adds.
* **Read what a role is for.** Each card says what the role is for and where it may be given.
* **See who holds a role.** With See access (`grants:read`), each card counts who was given it at your company or above.
* **Check what you may give.** With Manage access (`grants:manage`), each card says whether you may give it.
* **Open a role.** A role's page shows its full grid of permissions and the roles it relates to.
* **Compare two roles.** See what each adds over the other.

## How roles are organized

Role definitions are set in code and change only with a release; the Console can't create, edit or
delete them. With Manage access, **Give or remove roles in Members** links to where holders change.

The built-in person roles are cumulative: **Base**, then **Builder**, then **Operator**, each
including everything in the one before. **The core ladder** draws them as indented steps, each
saying in words how many permissions it adds and in which families ("Adds 18 permissions across
Build, Run, Govern, Org and Platform"), worked out from the roles themselves; for example Operator
adds `workflows:manage` where Builder has `workflows:write`. An agent can never hold a role that
includes an approve permission, so an agent is never given Operator.

**Roles given alongside** lists the other roles people, keys and apps are given, and **Roles for
agents** the bundles agents are given. Each says what the role is for and where it may be given,
when it is given only at the platform or only per company.

With See access (`grants:read`) as well, each role shows who was given it and where, counted from
the same list the Holders tab reads: grants given at your current company, at a unit above it, or at
the platform ("Counts show who was given each role at … or above it"). Grants given only at a unit
below your company are not counted here; the Holders tab shows them at that unit. A role reads, for
example, "12 given at the platform" or "3 given at Gloo LLC · 12 at the platform". A role with no
such grant shows a muted "None"; Base reads "None directly · included in Builder and Operator",
because a Builder or Operator holds everything in Base without being given Base itself. Without See access no count is shown at all, rather than a zero.
When the grant list is too long to count, the counts are left out and the page says so.

With Manage access (`grants:manage`), each role also says whether **you** may give it: only when it
is within what you hold yourself. Giving happens from Members.

A role's page, at `/trust-fabric/access/roles/<role>`, shows its full grid of permissions and the
roles it relates to:

* **Includes everything in**: the roles whose permissions it holds in full;
* **Included in**: the roles that hold all of its permissions.

Forge works these relations out from the permissions themselves, not from the role's description.

**Compatibility** roles are the per-key and per-app roles given to each API key and External App
that held scopes before roles decided authority. They can be revoked but not given. The older
compatibility roles that people held (Member, Operator, Viewer and External inference) are retired:
their holders were moved to the standard roles, and the roles themselves were deleted.

## Compare two roles

Under **Compare two roles**, choose two roles; with none chosen it compares Builder with Operator. A
sentence says it in plain words ("Everything in Builder is also in Operator. Operator adds 18
permissions; 30 are in both."), and **What … adds** shows each side's additions as chips. **Compare every permission side by side** opens the grid that
marks each permission as in both, only in one, or in neither. The choice is kept in the address
(`?a=<role>&b=<role>`), so a link shares the same comparison.

## Key state to watch

* **No counts.** Without See access, no holder count is shown. When the grant list is too long to count, the page says so and leaves the counts out.
* **None directly.** Base reads "None directly · included in Builder and Operator": a Builder or Operator holds everything in Base without being given Base itself.
* **Compatibility roles.** They can be revoked but not given.

## Related

* [Permissions](https://docs.gloo.com/forge/console/trust-fabric/access): every permission, and the roles that include it.
* [Holders](https://docs.gloo.com/forge/console/trust-fabric/access-holders.md): who holds a role at a scope, and how roles are given and revoked.
* [Members](https://docs.gloo.com/forge/console/platform/members.md): where roles are given and revoked.
* [Permission reference](https://docs.gloo.com/forge/reference/permissions): every permission, generated from the catalog.


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