JOGL Network Docs

Member management

Add, import, claim, merge, and remove community members.

The Members tab is where you manage your community's roster. It supports individual actions, bulk operations, and imports.

Member types and filters

Members are grouped into Claimed (real users), Internal (cold/scraped profiles), Archived, and Pending invitations. A large set of quality filters helps you find members that need attention (missing email or LinkedIn, duplicates, enrichment failed, and so on).

Adding members

  • Add existing users to the community.
  • Create an internal profile for someone not yet on the platform.
  • Invite users by email.
  • Import in bulk from CSV, Airtable, Luma, or LinkedIn (via the creation wizard or the dedicated community import flow).

Claimed vs. internal profiles

Communities often start with internal ("cold") profiles — records created from an import before those people join. You can:

  • Make claimable — invite the real person to claim their profile (single, bulk, or all-claimable), optionally sending an invitation email.
  • Revert to internal — undo a claimable state.
  • Resend claim invitations.

When a member claims a profile, the community's data links to their real account.

Roles and ownership

Promote a member to admin or demote back to member, and transfer ownership to another member (owner or platform admin only). Guards prevent removing the last admin or owner.

Bulk actions

Select members to: send email, Smart Enrich, add to an event, transfer to another community, reset enrichment, manage tags, or export CSV. You can also merge profiles, choosing which field wins on conflicts (duplicates are also auto-detected by normalized name / LinkedIn handle).

Removing members

  • Claimed members are removed with their data preserved as an internal profile (snapshot-and-remove).
  • Internal / claimable profiles are fully deleted.
  • Plain membership removal just drops the community link.

For a GDPR erasure that removes a member's data from a single community, see the API's community-scoped erasure.

On this page