JOGL Network Docs

Enrichment

Smart Enrich — depth tiers, cost preview, and run history.

Smart Enrich builds rich member profiles automatically from public sources (LinkedIn, OpenAlex, Semantic Scholar, web research). You run it from a community's Enrichment tab, or during the creation wizard, or as a bulk action on selected members.

Depth tiers

Smart Enrich has three depth levels. Each level is a superset of the one before it — a deeper tier runs everything the shallower tiers do, plus more.

TierAlso labeledWhat it addsRelative cost
QuickRapideDiscovery, classification, auto-fill, LinkedIn mergeLowest
StandardStandard+ web researchRecommended (default)
DeepApprofondi+ LinkedIn-URL discovery, publications (OpenAlex), DoctolibMost complete

Deep exposes an expert customize section to toggle individual add-ons (LinkedIn finder, publications, Doctolib). A checked add-on only sets the ceiling — the worker still decides per profile whether each step applies (e.g. it won't chase publications for a non-researcher).

What you control before launching

The Smart Enrich form shows:

  • the eligible member count,
  • a Force refresh switch (include_already_enriched) to re-run already-enriched profiles,
  • an ETA estimate, and
  • a credit-cost preview (a min–max range from the live rate card).

If the estimated cost exceeds the community billing owner's balance, an amber over-budget warning appears. See Billing.

Run history

The Enrichment tab includes a run history table where you can monitor progress, and resume or cancel runs. There's also a separate Publication refresh action.

Enrichment is billed post-hoc, at a flat per-tier rate: each enriched profile bills exactly one tier marker (enrichment_quick / enrichment_standard / enrichment_deep) for the depth the run was started at. It is not metered per individual step — skipping an optional add-on (e.g. no publications for a non-researcher) does not lower the charge for that profile. The pre-launch estimate is therefore the actual per-profile tier cost, not a ceiling most profiles come in under.

Data sovereignty

For claimed profiles (owned by a real member), enrichment results are stored as community-scoped suggestions and never overwrite the person's public profile directly. Fields sourced from protected origins (manual entry, CSV import, CRM) are never overwritten by automated enrichment.

On this page