Falaah Falaah AI

Operations Settings

Get an alert when a connector stops syncing and choose who receives it, set how far back the background-failure list opens, which mobile devices are enrolled, and which document-creation modes your team may use.

Four small screens that keep day-to-day operations honest: alerting, triage defaults, device enrollment and document-creation modes.

When you’d use this

  • A connector stopped syncing and nobody noticed for a week.
  • The background-failure list opens on a quarter of history when you only ever triage this week.
  • Someone left and their phone still has Muin Go on it.
  • You want to limit how documents may be created, or raise the notes-analysis limits.

Connector alerts

  1. Go to Settings → Communication and AI → Connector Alerts.
  2. Alerts enabled is the master switch. Turning it off suppresses all threshold alerts for this organization.
  3. Stale-failure threshold (hours) sets how long a connector may be failing before an alert goes out.
  4. Recipient emails is a comma-separated list, for example alice@example.com, bob@example.com.
  5. Select Save, or Reset to drop your edits.

Async failure list settings

  1. Go to Settings → Communication and AI → Async Failure List Settings.
  2. Default list window (days) sets how far back Async Failures opens when nobody has narrowed it. The screen’s reasoning: “An incident is usually this week, not this quarter.”
  3. The value must be a whole number between 1 and the platform ceiling of 90 days.
  4. Select Save changes. Success offers Open Async Failures so you can see the list on the new window.

How long failure records are kept is not set here. It is set with your other audit retention windows, and the platform ceiling is 90 days. The screen links to Open retention settings.

Mobile devices

  1. Go to Settings → Security → Mobile Devices.
  2. Enrolled devices lists each device with its platform, when it was last seen, its location and its mode. A locked device is labelled Locked.
  3. Edit screen rotation changes how a wall-mounted screen is oriented.
  4. Reset pairing keeps the device’s place, settings and history but clears its pairing, so the tablet in front of it stops working until it re-pairs and the next tablet presenting that serial number is accepted. Use it on a screen that was factory-reset and says it needs to be reset in Muin. Do not use it on a working screen.
  5. Revoke removes a device’s access entirely. It must be re-enrolled, with a fresh PIN, to use Muin Go again.

A forgotten mobile PIN cannot be reset remotely, because the PIN is stored on the device. Revoking the device is the way to force a fresh setup with a new PIN at the next pairing.

Document assembly settings

  1. Go to Settings → Communication and AI → Document Assembly.
  2. Creation Modes turns each path on or off:
    • Guided Creation: pick a document type, answer guided questions, get professional output.
    • From a Template: choose a pre-built template and let AI help fill it in.
    • From Your Notes: AI-powered creation from unstructured notes, emails and files.
  3. Rate Limits sets Notes analysis per hour, Max file upload size and Max files per analysis.

What it affects

  • Turning connector alerts off means a broken integration will not page anyone. Nothing else changes about the connector.
  • The default list window changes the page every on-call person lands on, not what is stored.
  • Revoking a device signs it out and forces a full re-enrollment, including a new PIN.
  • Turning a creation mode off removes that button from the Document Composer for everyone.

When it goes wrong

What you see What to do
“Could not load alert settings. Refresh to try again.” Reload. Your saved thresholds and recipients are unchanged.
“The window must be a whole number of days between 1 and 90.” Enter a whole number in range. Fractions and zero are rejected.
“Could not save” with “Nothing was changed. Check that the window is between 1 and 90 days, then save again.” Correct the value and save. The list keeps opening on its current window meanwhile.
“Couldn’t load devices. Please try again.” then Retry Reload. No device was revoked.
“Couldn’t revoke device. Please try again.” Reload and revoke again. The device still has access until you see the confirmation.
“Couldn’t reset pairing. Please try again.” Reload and retry. A zero-touch screen recovers on its own within a minute; a screen paired with a setup code needs a new code.
“No mobile devices have been enrolled yet.” Nothing is wrong. Install Muin Go to enroll the first one.
“Checking availability” never clears on Document Assembly Reload. The feature check could not complete; your mode settings are unchanged.

Next step