Skip to main content
The Policy Editor is your main workspace for building and refining policies in Clavata. This page gives you the essentials to get started quickly. Policy Editor 8 20 2025 Pn

Name Your Policy

  • Choose a clear, descriptive name.
  • Helps you stay organized and makes collaboration easier.
Text Policy
Username and Profile Text Policy

Select a Dataset

  • Pick a dataset to test against:
    • Using your own dataset with labels is always best
    • Ensure the labels in your dataset match the labels in your policy

Select a Test

  • All labels: This will run a test against your entire dataset. Can be useful for seeing everything together but can feel overloaded with a large dataset
  • All metrics: This will give you an overview of how each label in your policy is performing against the dataset. You can find troublespots or low performers easily here
  • Label focused: This runs a test against a singular label and give you the metrics for that label. Much smaller than running the All labels view
  • Testing helps you:
    • See which items are flagged or missed in real time
    • Use the results to refine conditions

Metrics Breakdown

  • After testing, review key performance indicators:
    • F1 score: balance between precision and recall (higher = better overall performance)
    • Accuracy: overall percent of correct results (both positives and negatives)
    • Precision: of the items flagged, how many were actually correct
    • Recall: of the items that should be flagged, how many you caught
    • False negative %: share of harmful items missed
    • False positive %: share of safe items wrongly flagged
    • True positives: correctly flagged content
    • True negatives: safe content correctly ignored
    • False positives: safe content incorrectly flagged
    • False negatives: harmful content missed
  • Metrics guide your next iteration and help you understand how your policy will perform in production

Commit Versions

  • Save changes with a commit.
  • Add a short commit note (e.g., “Added rule for image spam”).
  • Commits create a version history so you can track progress and roll back if needed.
  • Click the Versions tab, the version you want, then click Make current version to set that version as the one used by your API

We’d Love to Hear From You

Whether you have a suggestion, feedback, or a bug to report, here are the best ways to get in touch:
  • In the App: Use the Feedback button for direct suggestions.
  • On Slack: Reach out to the team in your shared channel.
  • With your AM: Talk to your dedicated account manager.
  • Via Email: Send a message to [email protected].