Skip to content

Admin

Fromenance is a communication provenance platform administered from app.fromenance.com. This page covers roles and the map of the admin app; the two pages after it cover users and keys, and retention and privacy.

By the end you will know which role to give each person on your team and where every setting is.

Every user in a tenant has exactly one role. Sign in is by email magic link or passkey; there are no passwords.

Role Intended for Can
Owner The accountable executive or the tenant creator Everything an admin can, plus billing changes and deleting the tenant
Admin Security or IT lead who owns the account Settings, users and roles, API keys, domains, sources, reply templates, webhooks, submissions, overrides, fraud list, indicators, exports, audit log, billing (read)
Analyst Fraud or security team member working incidents Submissions and their detail, raw MIME download, overrides, fraud list, indicators, exports, registrations, dashboards, webhook delivery logs (read), audit log (read)
Integrator The developer or ESP admin wiring registration in API keys, domains, sources, reply templates, webhooks, registrations and coverage, dashboards, test tools. No submission content
Viewer Anyone who needs the numbers Dashboards, indicators, registrations, and read only lists

Permissions by area:

Area Owner Admin Analyst Integrator Viewer
Tenant settings, branding, retention yes yes
Users and roles yes yes
API keys yes yes yes
Domains and reply identity yes yes yes
Sending sources yes yes yes
Reply templates yes yes yes
Webhook endpoints (write) yes yes yes
Webhook delivery log (read) yes yes yes yes yes
Submissions, detail, raw MIME yes yes yes
Overrides yes yes yes
Fraud list (write) yes yes yes
Indicators and exports yes yes yes yes
Registrations and coverage yes yes yes yes yes
Dashboards and stats yes yes yes yes yes
Audit log yes yes yes
Billing yes read
Delete tenant yes

The same permission set applies to API keys: a key with the admin scope acts as an admin, read as a viewer plus submissions, and register only registers. See Users and keys.

Screen What is there
Overview Today and 30 days: submissions by outcome, registrations by source, reply p95, replay attempts, coverage gap count, top indicators
Submissions The main table with filters and the detail drawer. See Verifications
Indicators Extracted indicators with fraud list status, bulk add, CSV and STIX export
Fraud list The tenant block list with source and history
Campaigns Placeholder until the intelligence tier ships
Registrations Search by code, message id, template, and date; coverage per source against expected volume
Sources Sending sources with health, webhook URL, secret rotation, adapter instructions, and the test event button
Domains Domains with TXT status and the copyable record, re-check, role toggles, reply identity setup
Verify page Site keys, allowed origins, embed snippets, live widget preview
Reply templates One MJML template per outcome with the locked verdict block, preview with sample data, send test
Webhooks Endpoints, event selection, delivery log with replay, send test
Settings Profile, branding (logo, accent, display name, support URL, fraud contact), retention days, Authoritative Mode (read only), users and roles, API keys, audit log, billing
Setup The six step wizard, re-enterable from Settings

Every write in the admin app and API is recorded with the actor (user or API key), action, target, and before and after values: key minted or revoked, user invited or role changed, domain added, template saved, override recorded, raw MIME downloaded, fraud list entry added. Settings, Audit log lists it; GET /v1/audit returns it with cursor pagination.