Member management

The People section of the community admin dashboard is where you manage your community's roster. It supports individual actions, bulk operations, and imports. Join requests have a section of their own, Join requests, listed right after People (see Join requests).

Reading the roster

At the top, From profile to member counts the roster at each stage: All profiles, Internal, Claimable and Members, with the average completeness and, on a plan with a profile limit, the profile slots used. Select a stage to list just those profiles; All profiles clears the filter. Beside the counts sit the pending invitations to people who already have a JOGL account (+N invited from JOGL), the members who archived their own profile, and Invite N claimable, which sends the invitation email again to every claimable profile. Beside it, Needs attention lists the checks that find something, under Data quality (internal profiles that match a member, duplicate profiles, invalid LinkedIn URLs, warnings) and AI enrichment (enrichment failed, left out of enrichment, LinkedIn matches to confirm, profiles that can be enriched from LinkedIn, and those with no OpenAlex author, classification or web research yet); select one to filter the roster. The counts are cached. Adding, converting or removing people from the dashboard refreshes them, and so does an invitation being answered while People is open; when one still looks behind (after someone joined on their own, say), Refresh stats under Actions recomputes them.

Beside the search box, filters narrow the table by quality (missing email or LinkedIn, duplicates, incomplete, enrichment failed, and so on) and by role (Owner, Admin, Member); sort by name, completeness, join date, or last update.

Profile types

• Members — claimed profiles: real people who have signed in.
• Internal profiles — records you created or imported for people who haven't joined.
• Claimable — internal profiles marked claimable against a real address (see Turning internal profiles into members); they become members the moment that person signs in with that email, whether or not an invitation email was sent.
• Pending invitations — existing JOGL users you invited who haven't accepted yet.
• Archived — members who archived their own profile. They are still members; the roster marks them Archived, and the archived count above the roster lists them.

Adding people

The roster's Add people menu offers:

• Create profile — an internal profile for someone not yet on the platform.
• Invite members — search existing JOGL users by name, or by the whole email address they sign in with (which finds only your connections and members of communities you run), pick Member or Admin, and send. Each result says how you know the person, such as Your connection or Also in another of your communities. The invitation arrives as a message they Accept or Decline, and it also waits in their community picker. It uses a profile slot only once accepted: a community at its plan's limit cannot take the person in, and their invitation stays open.
• Import CSV or Excel — the guided import (mapping, review, execute). The mapping step can put a column into one of your community's custom fields, or create a new one. A file saved without a header row is recognized when its first row holds an email address in a column whose values below are mostly email addresses, starting with the next filled one, and none of the next nine rows looks like a header row (no email address, and a cell that matches a column name, such as web in a tags column): its first row is then imported as a person, and its columns are named Column 1, Column 2 and so on for you to map. If the first person in such a file has no email, or a row like that follows it, add a header row, or that person is read as the header and left out.
• Import LinkedIn Connections — upload your LinkedIn data-export archive.

To add someone who already has a JOGL account without waiting for them to accept, open Invite (on the sidebar's People page, or in the dashboard's top bar) and choose Add people: it adds them straight away, as a member or an admin, from the same search. It adds only people with an account of their own; platform admins also have Add members in the menu above, for any profile.

The Actions menu holds what acts on the profiles already here:

• Send email… — email members from the platform, up to 500 recipients per send; a wider audience is refused rather than truncated.
• Merge duplicate profiles — pick what counts as a duplicate (LinkedIn, Email or Full name), click Find duplicates, then merge the pairs it found in one go. The scan holds back pairs with different names, different LinkedIn profiles, different emails (unless matched on LinkedIn), or neither profile internal; merge those from the member's profile (two claimed profiles cannot be merged). What a merge keeps depends on the pair. When one profile is claimed, it is kept as it is: the other profile's community tags and community data move onto it and the other profile is archived, but its profile details and emails do not. If that claimed person is not in this community, merging invites them instead (Merge & Invite), and the merge completes once they join. Until then the internal profile's row and the invitation's row both show Merge pending. If they decline the invitation, or you withdraw it, the merge is cancelled, and it does not happen even if they join later some other way. Otherwise the more complete profile is kept. Merged from the member's profile, you choose which value to keep where the two differ; merged in one go, nothing is asked: the emails of both are combined, and where they differ in headline or organization, or in LinkedIn URL on a LinkedIn match, the kept profile's value wins, unless only the other profile's headline or organization was entered by hand, by an admin, by an import or in a profile interview, or has no record of where it came from, and the kept profile's came from enrichment. Either way, the kept profile ends with the higher of the two roles in this community (a merge never makes anyone owner), and the profile merged away leaves any other community it belonged to.
• Resend invitations — shown while the community has claimable profiles: sends the invitation email again to all of them (see Turning internal profiles into members).
• Sync with CRM — opens the Import & sync section, where Airtable, HelloAsso and Odoo are synced (see CRM sync).
• Refresh stats — recomputes the counts above the roster.

The Import & sync section of the dashboard (under Community) gathers these doors in one place: a spreadsheet (CSV or Excel), LinkedIn connections, a link to event guests in Events, the CRM cards and the import history. An import or sync opened from it returns to it, and one opened from People returns here. Every one of these pages links to How imports work, which says how someone already in the community is recognised and what an import never does.

Once a CSV or LinkedIn import starts creating profiles, it runs on our servers, so it carries on if you close the page. It sends no notice when it ends: come back to People to see the new members. A CRM sync does tell whoever started it, if they still administer the community (see Integrations).

Members a CSV, LinkedIn or CRM import adds are indexed for search before the import reports that it has finished, so they can usually be found straight away; any it could not index in time are picked up later by a background sweep.

Everyone who may invite into the community has a personal invite link: every admin, and in a public community every member too. They find it under Invite on the People page (the sidebar's People), where they can copy it or Make a new link, which stops the old one. A link does not expire, and everyone who uses it is recorded as invited by its holder. What it does follows the community's Who can join setting: with Admins approve requests, whoever uses it sends a join request, without a note (that page gives the one exception); otherwise an admin's link lets people in directly, and a member's link works like the join page. Making the community private stops its members' links; admins' links keep working.

Someone with no JOGL Network account can create one from a link while its holder can still share it and their own account's trust level does not read unverified. An admin's link can create as many accounts as needed; a member's link creates at most 50 over its lifetime. An account the platform has not verified cannot join through a member's link on its own: the link sends you a join request for it instead, even while Anyone can join is set, unless that link brought it to JOGL Network, which lets it in. An admin's link lets it in while Anyone can join is set.

The Invite links list above the roster appears once someone has made a link, and only admins see it. It shows each person's link, how many people joined through it and how many requests through it are still waiting, and Who used it. Turn off stops that one link, say one shared too widely; whoever joined or asked to join through it keeps their place. It does not stop its holder inviting: the next time they open Invite or copy their link, they get a new one, unless they have made five links in that community in the last 24 hours, the turned-off one included. When a holder loses the right to share (above), their link stops working while they lack it, but a link that was not turned off works again if they get that right back, so turn off a link that spread too far even then. The app also offers your own link with a Copy invite link button when an invitation email was not sent because the person unsubscribed (see below). Event guests come in through the Events section rather than Add people.

Join requests

A community whose Who can join setting is Admins approve requests (in the General section, see Who can join) does not let people join on their own: they send a request. One sent from a public community's join page or Discover Communities can carry an optional note; one sent through an invite link carries none. Requests wait in the dashboard's Join requests section, oldest first, and its entry in the dashboard's navigation shows how many are pending. Each one shows the applicant's name, photo, headline, organization, note, the member whose invite link sent it, when one did, and the date they asked. A community where Anyone can join gets requests too, from accounts the platform has not verified that used a member's invite link:

• Approve makes them a member. On a plan with a profile limit, an approval counts toward it like any profile you add, and a full community refuses it. It also admits an account the platform has not verified, which cannot join a community on its own.
• Decline closes the request; they can ask again after 30 days.

When a request arrives, the community's admins are told by push and by email, as each one's own notification switches allow. Each admin is told at most once an hour per community; when more than one request is waiting, the notice says how many. Once an applicant has filed five requests in 24 hours, across communities, their further requests are not announced, but they still wait in the panel. A request counts toward the five even when the hourly limit meant no admin was told about it. The applicant is told when you approve or decline, by push and by email as their own notification switches allow, so one who turned both off hears nothing; an applicant withdrawing a request sends no notice. The applicant's note is deleted once the request is decided. If you switch back to Anyone can join, requests already waiting stay in the panel for you to decide; making the community private or archiving it closes them.

Turning internal profiles into members

• Invite to join (per row, or in the bulk toolbar) marks an internal profile claimable: "This profile can now be claimed. They become a member once they log in with <email>." The address is also added to the profile's emails, and the person is emailed an invitation: inviting always sends it, and there is no switch to skip it. This is the only way a profile becomes claimable. Every import (a spreadsheet, LinkedIn connections, a CRM, an event's guests, the API) creates internal profiles, which nobody can sign in to and nobody is emailed about, so who gets invited is always your choice. A claimable profile nobody has emailed yet, such as one made claimable before this rule, shows Send invitation in its row, which asks you to confirm before the email goes.
• When the address already belongs to someone else on JOGL Network, the profile stays internal and the invitation still goes out. If the address holds a profile one other community made that nobody has signed in to, the invitation waits: the row shows Invitation sent, the address is added to the profile's emails while it waits, and Withdraw invitation cancels it. Whichever community's invitation the person opens first, they sign in through it, and the others then reach them as invitations in their JOGL messages, where accepting merges that community's profile into their account. If the address belongs to someone who already has an account, the invitation goes to their messages straight away, from the row or the bulk toolbar alike, and accepting it merges the profile into their account.
• Resend invitation email per row, or Resend invitations for every claimable profile at once.
• Revert to internal profile undoes a claimable state. A claimable profile keeps the address it was made claimable with: to change it, revert it first, then Invite to join again with the new address.

The invitation email carries a one-click unsubscribe. If the person has used it, no email is sent, from your community or any other, and the profile still becomes claimable: you are told so (Profile is ready, but no invitation was sent, or No invitation was sent to <name> on a resend, and an "unsubscribed" count in a bulk summary) with a Copy invite link button. If you know them, send them the link yourself and ask them to sign in with the address on their profile; JOGL Network does not send the email anyway.

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

Roles and ownership

Per row: Make Admin / Remove Admin, and Transfer Ownership. The owner is whoever pays for the community, so the owner's own row offers none of these, nor Remove: the role moves only with the payment (see Owner vs. admin).

Transfer Ownership is offered to the owner or a platform admin, on the row of a member who has signed in. The new owner pays for the community's owner-paid actions from then on, the previous owner stays on as an admin, and every personal delegation rule on the community is paused (see Roles). It is not offered on a community an organization pays for: the organization's owner owns that one, and unlinking it from the organization is how it gets an owner of its own (see Organizations).

A community always keeps at least one admin or owner who has signed in: removing or demoting the last one is refused.

Bulk actions

Select rows to open the bulk toolbar: Manage Tags, and under Actions — Send email (the same 500-recipient cap as the roster action above), Smart Enrich..., Add to event…, Invite to join, Transfer to another community…, Resend invitations, Revert to internal profile, Reset enrichment — plus Remove / Delete and Export CSV.

Removing people

• Removing a claimed member from their row keeps their data: "Member removed. Their data has been preserved as an internal profile." Their values in your community's custom fields stay with that internal profile, readable by your community's admins only. The bulk Remove action does not: it drops the membership and the community's enrichment data for those members, with no internal-profile snapshot.
• Deleting an internal or claimable profile removes it permanently. A profile that has been claimed cannot be hard-deleted.
• Withdrawing a pending invitation cancels it, and with it a Merge & Invite that was waiting on that invitation (see Adding people).
• The owner can't be removed, from their row or in bulk.

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