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

# Guides

> Step-by-step guides to Frayme for compliance analysts, engineers and managers, with screenshots and short clips from the real product.

export const Shot = ({id, alt, caption}) => <Frame caption={caption}>
    <img className="block dark:hidden rounded-lg" src={`/images/guides/${id}.light.png`} alt={alt} loading="lazy" decoding="async" />
    <img className="hidden dark:block rounded-lg" src={`/images/guides/${id}.dark.png`} alt={alt} loading="lazy" decoding="async" />
  </Frame>;

These guides walk through the Frayme console the way each role actually uses it. Every screenshot comes from a running Frayme instance, and every step was executed before it was written down. Where a control exists on screen but does not do anything yet, the guide says so.

## Who these guides are for

<CardGroup cols={3}>
  <Card title="Compliance analyst" icon="user-check" href="/guides/analyst/overview">
    Work the Decision Queue, review evidence in the Decision Console, request information from customers, approve or decline.
  </Card>

  <Card title="Engineer" icon="code" href="/guides/engineer/overview">
    Build and activate decision flows, connect data sources, manage API keys and webhooks, tune risk rules.
  </Card>

  <Card title="Admin and manager" icon="users-gear" href="/guides/admin/overview">
    Set up the tenant, create roles from templates, invite the team, oversee decisions and correct them when needed.
  </Card>
</CardGroup>

## The one case that ties them together

[One transfer, three desks](/guides/end-to-end) follows a single 50,000 USD transfer from the moment an engineer wires the tenant, through the analyst's review and information request, to the manager's override, with a screenshot at every hand-off.

## What each persona sees

The sidebar is driven by the scopes your role holds. The sidebars below are the same product signed in as different roles.

<Tabs>
  <Tab title="Analyst">
    <Shot id="shared/sidebar-03-analyst" alt="Sidebar as an analyst: Dashboard, Decision Queue, Decision Console, Cases, Team, Settings" caption="The analyst template sees the review surfaces only." />
  </Tab>

  <Tab title="Engineer">
    The engineer template sees the same navigation as a tenant admin (next tab): Workflow, Risk Management and Data Sources join the review pages. Only the Settings tabs it can edit differ.
  </Tab>

  <Tab title="Tenant admin">
    <Shot id="shared/sidebar-02-tenant-admin" alt="Sidebar as a tenant admin" caption="The reserved admin role sees every tenant surface." />
  </Tab>

  <Tab title="Frayme operator">
    <Shot id="shared/sidebar-01-super-admin" alt="Sidebar as a Frayme super-admin, with the Admin group" caption="Super-admins get the Admin group on top: Tenants, Super Admins, Poller, Tenant Switch." />
  </Tab>
</Tabs>

Roles are not fixed product roles. [Personas and permissions](/guides/personas-and-permissions) explains the scope model and gives the exact templates these guides assume.

## Conventions used in these guides

* **Bold** text is a label you see on screen, quoted exactly.
* `Code` is a value you type, a path, or a field name.
* Keyboard shortcuts appear as `⌘↵`. On Windows and Linux, use `Ctrl` where a guide says `⌘`.
* Links into the console point at `https://console.us.frayme.io`.
* A **Not available today** note marks a control that renders but has no behaviour yet, so you do not wait on it.