Skip to main content
For most users, this is how you’ll contribute to the ontology day-to-day: as you work in Threads with Ana in Threads, you’ll come across definitions worth saving, rules that should apply everywhere, or data quirks Ana figured out mid-analysis. You can ask Ana to propose those as additions to the ontology — they go through a review queue, and an admin approves them before anything goes live. If you’re an admin setting up the ontology systematically, want to upload different file types, connect a repository, or define objects and metrics from scratch, see the Setting Up Your Ontology guide for the full walkthrough. Every analysis you run with Ana has the potential to make the ontology better. When Ana learns something new about your data — a metric that doesn’t behave as expected, a definition that needs a caveat, a join condition that isn’t obvious from schema alone — you can ask her to save that knowledge. Nothing you propose affects anyone else until an admin approves it.

​
How It Works

  1. You find something worth saving. During a Thread, Ana figures out how your team calculates churn rate, or surfaces a quirk about how a specific Salesforce field behaves. Instead of letting that knowledge disappear, you ask Ana to save it.
  2. Ana proposes a change. She writes up the new definition, rule, or note as a diff against the existing ontology. You can see exactly what she’s proposing before it’s submitted.
  3. The change lands in Reviews. Proposed changes are held in the Reviews tab of the ontology editor — visible to admins, not yet live. Nothing goes live without explicit admin approval.
  4. An admin approves or rejects it. Once approved, the change is committed to the ontology and available to Ana in every subsequent Thread.

​
What You Can Propose

Any plain-language knowledge that would help Ana answer questions more accurately:
  • A metric definition or calculation rule your team uses (“exclude refunded orders from revenue”)
  • A fiscal calendar or date convention (“Q1 starts February 1”)
  • A data quirk or known issue (“the status column in orders uses 1/0, not true/false”)
  • A business rule or exclusion (“don’t include test accounts in any analysis”)
  • A clarification about what a table or column represents
You can also ask Ana to update or correct an existing definition if you know it’s wrong.

​
How to Ask Ana

Just say it in plain language at the end of a Thread:
“Save this revenue definition to the ontology.”
“Add a note that test accounts use account_type = 'internal'.”
“The churn calculation we just worked out — can you save that?”
Ana will draft the change and show you what she’s proposing. Review it, ask her to adjust if needed, then confirm to submit it for review.

​
What Happens Next

Once submitted, the change appears in the Reviews tab as a diff. An admin will review it and either approve it into the ontology or leave a comment. You’ll see the change go live once it’s approved — from that point on, every user on your team benefits from it.