Falaah Falaah AI

Platform Console

The administration console: one page for platform health, background work that failed, document processing quality, search analytics, payment disputes and statement parser patterns.

The Administration console is where an owner or admin checks that the platform itself is behaving. Every screen below is owner and admin only.

When you’d use this

  • Something did not happen and you need to know whether it failed or never ran.
  • A connector or service looks down and you want one place to confirm it.
  • Documents are coming out with poor extraction and you want the numbers.
  • A card payment was disputed and you need to respond before the deadline.

Administration overview

  1. Go to Administration in the sidebar. The direct route is /platform/admin.
  2. The top of the page is either Everything looks good with “No issues require your attention right now”, or Needs Attention with the specific problems listed.
  3. Tiles summarize System Health, Security (audit events over 30 days), Search Quality, E-Signatures (completion rate) and Doc Assembly (total projects).
  4. Quick Links open the rest of the console: Audit and Security, System Health, Async Failures, Search Analytics, E-Signatures, Document Assembly, Team and Roles, 1099 Filing, Profile Approvals, Insight Templates, Facility Rentals and Statement Parser Patterns.

System health

  1. Go to Administration → System Health.
  2. Overall Status is the single answer. Services lists each one with its own state.
  3. Integrations reports your connectors. “All integrations are working normally” is the clean state; Configure Integrations takes you to fix one.
  4. The status refreshes automatically every 30 seconds, so leave the page open during an incident.

Async failures

Everything the platform tried to do in the background and could not finish.

  1. Go to Administration → Async Failures.
  2. One tile per background system. The number is failures not yet resolved. clear means that system has none; -- means it did not report.
  3. Filter by source, by kind (Non-money or all), by age, or search. The age filter is how long ago the first attempt failed, not the last.
  4. Open a row to see what was attempted, how many attempts were made, the first and last failure times, and the recorded error, plus a plain-language “What this usually means”.
  5. Requeue re-drives the work. It retries within a minute and the page refreshes itself. Requeueing twice is safe: “Someone already requeued this one. Nothing was reset a second time.”
  6. Open in {source} jumps to the surface that owns the problem.

Read the state column carefully. retired means every retry is spent and nothing will try again. retrying means the next run will pick it up on its own. partial means some subscribers received the event and some did not.

Money failures are never re-driven from this page. Muin says so and routes you to the surface that can charge safely without double-charging.

The page is honest when it cannot see everything: “{reported} of {total} sources reported. The rest could not be read, so this list is incomplete.” An empty list with unreported sources reads “No failures from the stores that answered. This is not an all-clear.”

Failed records are pruned after 90 days. Export anything you need for an audit before then.

Processing pipeline

  1. Go to Administration → Processing (/platform/processing).
  2. The counters cover Total Processed, Pending, Processing, Completed and Failed.
  3. Quality Metrics reports Extraction Confidence, Fields Extracted, Search Chunks and Review Rate.
  4. Document Types breaks the volume down by classification. Recent Issues lists documents requiring attention.

Search analytics

  1. Go to Administration → Search Analytics (/platform/search).
  2. Metrics Overview reports Total Searches, Avg Results per search and Zero Results Rate.
  3. Top Search Queries shows what your team actually looks for.
  4. The page grades itself: “Search quality is excellent” at a low zero-result rate, through to “High zero-result rate, users may not be finding what they need”.
  5. Tips to Improve Search Quality names the three fixes: descriptive titles, text-searchable content rather than scanned images, and metadata tags for the terms your team uses.

Payment disputes

  1. Go to Administration → Disputes (/admin/disputes).
  2. Filter by status: Needs Response, Warning - Needs Response, Under Review, Lost or Accepted.
  3. Work the Needs Response rows first; a dispute with no response is lost by default.

Statement parser patterns

Used when reconciling bank statements, where a payment’s description has to be parsed into a donor name.

  1. Go to Administration → Statement Parser Patterns (/admin/reconciliation/parser-patterns).
  2. Tabs separate Platform patterns (which apply to every organization), Custom patterns (yours, which override them) and Proposed patterns awaiting review.
  3. Review and Activate opens a pattern. Paste a real description into Test against a sample description and Muin reports “Pattern matches.”, “Pattern does not match.” or “Pattern is not a valid regex.”
  4. Confirm to activate. Activating runs the pattern against every matching bank row in scope.
  5. Pattern Accuracy and LLM Cost Summary report how well the patterns are doing and what the fallback is costing, with total calls, the second-tier rate and an estimated cost for the period.

What it affects

  • Requeueing an async failure re-runs real work, so the downstream effect happens for real: an email sends, a receipt generates, a webhook fires.
  • Activating a parser pattern changes how future and in-scope bank rows are attributed, which changes donor matching and receipts.
  • Accepting a dispute concedes the money. Responding does not.
  • Nothing on the health, processing or search screens changes data; they are read-only.

When it goes wrong

What you see What to do
“The source counts could not be read, so this page cannot tell you whether anything is stuck.” Treat it as unknown, not clear. Reload; if it persists, check System Health.
“Unable to reach platform services” on System Health The console itself cannot reach the platform. Retry; if it continues, this is an outage, not a configuration problem.
“Could not load failures” with “The counts above are the last good ones and may be stale.” Reload. Do not act on the stale counts.
A failure you requeued returns to the list The underlying cause is unfixed. Open the recorded error and fix the subscriber before requeueing again.
“Failed to load parser patterns. Admin role required.” You are not an owner or admin. Ask one to open it.
“Managed in muin.admin” beside a pattern That pattern is platform-level and not editable from your organization.
“No search data available yet.” Nobody has searched yet. Analytics appear once your team starts using document search.

Next step