Skip to main content
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

Compliance analyst

Work the Decision Queue, review evidence in the Decision Console, request information from customers, approve or decline.

Engineer

Build and activate decision flows, connect data sources, manage API keys and webhooks, tune risk rules.

Admin and manager

Set up the tenant, create roles from templates, invite the team, oversee decisions and correct them when needed.

​
The one case that ties them together

One transfer, three desks 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.
Roles are not fixed product roles. 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.