Skip to main content

​
Disabling Incorrect Scores

When you spot an AI-generated score that is clearly wrong, admins can disable it directly from the analysis surfaces. Disabling a score hides it from every table, modal, and metric that relies on that value so the rest of the team is not misled.

​
Who Can Disable Scores

  • Admins (or internal users flagged as admins) can disable scores anywhere they view score details.
  • Non-admins can still open the score detail modal, but the confirmation dialog explains they do not have permission and lists the admins who can help.

​
Where the Disable Option Appears

Admins will see a Disable score button in every place the score detail view is rendered:
  1. Analysis Tables
    On both the Calls and Documents tabs of an Analysis Field, each score row has a column with the score details. Click the row’s score to expand the drawer, then use Disable score in the detail panel.
  2. Expandable Analysis Cards
    When reviewing an interaction (call or document) from the analysis sidebar, expand the relevant configuration and open the score detail. The same Disable score button is available.
  3. Parent Context Modal
    From the parent-context badge, open the modal and choose the score. The disable option is surfaced inside the score section.

​
What Happens When You Disable

  1. Click Disable score and confirm the destructive action. The dialog reminds you it cannot be undone in-app.
  2. The score disappears from the current table or modal immediately after the mutation succeeds.
  3. Downstream counts, averages, and bucketed charts automatically exclude the disabled score on the next refresh, keeping team metrics accurate.
Irreversible: Re-enabling a disabled score is not supported in the UI. If you disabled something by mistake, contact the Fabius team for assistance.

​
How Non-Admins Are Guided

Non-admins who open the score modal see a message explaining they do not have access, along with a list of workspace admins (names and emails). They can reach out directly without guessing who can help.

​
Tips for Accurate Reviews

  • Use the See Rubric button to verify whether the score actually violates the grading instructions before disabling it.
  • If several scores for the same field look suspect, pause and loop in your admin or RevOps owner—they can investigate configuration or model issues before mass disabling.
Keeping scores accurate is critical to maintaining trust in the analysis. A quick disable by an admin keeps the system clean without waiting on engineering.