For community owners & admins
Run a community on JOGL Network — from creation to enrichment, events, and integrations.
This section is for people who own or administer a community: creating it, building the roster, enriching member profiles, tuning search, running events, reading analytics, and connecting integrations.
The admin dashboard
To manage a community you administer, pick it in the community switcher, then choose
Admin Dashboard in the side menu. The dashboard opens full screen, at /community/<id>;
members without admin rights see "You don't have permission to view this page" instead. On a
computer, its header shows the community's name and your role, a back arrow that returns you to
your chats, an Admin guide link that opens this guide in a new tab, at the page for the
section you have open, and an Invite button. Invite opens the dialog with your own
invite link and, for someone who already has a
JOGL account, Add people; it shows unless the community or your own profile is archived. On a
phone, the guide link (a book icon, which opens this page) and Invite sit at the top of the
list of sections.
The dashboard is split into sections, in four groups:
| Group | Section | What it does | Documented in |
|---|---|---|---|
| Community | Engagement | What the community's members have been doing, as counts only, over 7, 30, 90 or 365 days. Admins only | This page, below |
| General | Logo, name, description, visibility, who can join, which engagement figures to show, AI processing, delegation rules, and the danger zone | Create & configure | |
| People | Everyone's Invite links, and the profile roster: add, invite, import, claim, merge, enrich, and remove members | Member management | |
| Join requests | Approve or decline the people asking to join | Member management | |
| Import & sync | Import a spreadsheet or LinkedIn connections, sync Airtable, HelloAsso or Odoo, and see past imports | Member management, CRM sync | |
| Events | Create events, connect ticketing platforms, manage attendees | Events | |
| Member profiles | Custom fields | The custom fields admins keep about members | Custom fields |
| Tags | Named tags with search-boost weights, and the families that group them | Search tuning | |
| Enrichment | Smart Enrich runs, publication refresh, and run history | Enrichment | |
| Search and AI | Permissions | Which profiles non-admin members can find in search | Search tuning |
| Context | The AI context text and the knowledge base documents | Search tuning | |
| Connections | Integrations | Slack, Discord and Microsoft Teams bots | Integrations |
| API & AI tools | Whether the community's admins can write through their own API keys and AI tools | API keys |
On a computer, the groups are listed in a sidebar on the left and General opens first. On a phone, the dashboard opens on the list of sections instead: a card at the top with the community's visibility, your role and three figures (its profiles, how complete they are on average, and its searches over the last 90 days), and under each section a line on where it stands, such as the kind of figures under Engagement, pending invitations under People, or the average profile completeness under Enrichment. Tap a section to open it; the back arrow, or a swipe to the right, returns to the list. A community you have just made with the creation wizard opens on People either way, with a note that it is ready. When join requests are waiting, their number appears beside Join requests. If you have unsaved changes in General or Tags, the dashboard asks before you leave the section.
Engagement
Engagement counts what the community's members have done over the period you pick (7, 30, 90 or 365 days): their searches and what they found, how many were active, and, depending on the kind of community, either the invitations and meetings of an Open networking community or the team searching, profile coverage and credits of an Internal intelligence one. The kind is chosen automatically, internal when at least 90% of the community's profiles are internal ones, and General lets an admin set it. Only admins see this section. To keep people from being picked out, most counts of one to four people show as <5. A figure that would give such a count away, because it is part of another figure shown beside it or adds up with others to a total, is not shown at all, and neither are the search figures for a period in which one to four people searched. The one exception is an internal community in which at least 90% of the profiles are internal and every member with a claimed profile is an admin: its search and profile figures show in full, and only counts of team members under five still read <5 or are left out.
The research and professional analytics and the member map are not admin sections: every member
can open them from the community's People page (Signals and Map tabs) or at
/community/<id>/analytics.
Billing lives in Settings → Billing (with the organization selected, for a community an
organization pays for), not in the dashboard; what the dashboard does hold is the community's
Delegation rules, in General.
Create & configure a community
The creation wizard, the free-trial gate, general settings, who can join, delegation rules, roles, and the danger zone.
Member management
Add, invite, import, claim, merge, and remove members, and review join requests.
Custom fields
Add, edit, archive, and delete the custom fields admins keep about members.
Enrichment
Smart Enrich depth tiers, cost preview, run history, and publication refresh.
Search tuning
Tags, search permissions, AI context, and the knowledge base.
Events
Create events, import guests from Luma, Eventbrite, or HelloAsso, and open networking.
Analytics
Research and professional dashboards, and the member map.
Integrations
Chat bots and CRM sync.
Organizations
Group communities under an organization with shared admins and billing.
Billing
Free trial, plans, credits, and what is metered today.
API keys
Mint keys, connect tools, and enable API writes.
Owner vs. admin
A community's owner is the person who pays for it: whoever pays personally, or the owner of the organization that pays. When the person who pays changes, ownership moves with it: a previous owner who is a member of the community stays on as an admin, and the new payer becomes the owner if they are a member. An organization's owner does not have to be a member: they own the community through the organization, and lose that when someone else unlinks the community from it. The owner can't be removed from the community. An invitation offers member or admin, never owner, but the person who pays owns the community however they join, through an invitation too.
Almost everything in the dashboard is available to both owners and admins. The differences are:
- Transfer Ownership — owner only (platform admins can also do it), to a claimed member, who then also pays for the community. It is not offered for a community an organization pays for.
- Archive and unarchive the community — owner only. An owner of the owning organization and platform admins can do it too; other admins see a note saying who can.
- Delete the community — owner only, and only once the community is archived. An owner of the owning organization and platform admins can delete it too.
- Delegation rules (in General) and the Admins can write through the API switch (in API & AI tools) — changed only by whoever pays for the community: its owner when they pay personally, or an owner or admin of the paying organization. Platform admins can also manage delegation rules. Other admins see both read-only. See Billing and API keys.
- Adding someone directly — every admin can add a person who has their own JOGL account, as a member or an admin, with Add people in the Invite dialog. Adding any other existing profile (the roster's Add members, Added immediately) is for platform admins only. Community admins can also bring people in without an acceptance step with Create profile, a CSV or CRM import or an event guest import, which create profiles directly; an event guest who signs in to JOGL with the email the event lists is not added, but may be sent your community's invitation instead (the events page says when).
For a community an organization pays for, the organization's owner is the community's owner and the organization's admins are its admins, without needing a role in the community, as long as each holds one of the organization's seats. Linking the community to an organization, or unlinking it, still needs them to be an admin or owner of the community themselves (see Organizations).