My Network
Connections, connection requests, suggestions, and who you can reach.
My Network (sidebar entry when your scope is All my communities) is your personal graph across every community: the people you're connected with, requests waiting on you, and suggestions of who to meet next.
Connections
A connection is a mutual link between two members, like on a professional network. Connections can see the contact details you share with Connections only, can be given access to your bookings, and can be invited to collaborate on your projects.
To connect, use Connect on a search result, a people card, or a profile, and optionally add a message. The button shows Requested while the other person decides, and Connected once they accept. If someone has sent you a request, the button reads Respond and takes you to your requests.
Requests
The Requests view lists Received requests (accept or decline) and Sent requests (withdraw). The sidebar shows a badge with the number of requests waiting on you.
Who may send you a request is your choice, in Settings → Notifications → Messaging: Anyone, Members of my communities + Members of my connections' communities, Members of my communities only, or No one.
Views
| View | What it shows |
|---|---|
| People | Everyone in your network, searchable. |
| Map | Your network on a map. |
| Signals | Analytics across your communities. |
| Meet | AI suggestions: people in your network who work closest to what you work on. Mark each as Worth meeting or Not for me. |
Who you can reach
Messaging, connection requests, meeting requests, and bookings follow the same base rule. You can reach someone when their own setting allows it, and either:
- you are in reach of each other — you share a community, or you are connected — or
- your account is verified.
This gate is checked when a conversation is opened, not on every message. An existing DM thread therefore keeps working after you stop sharing a community or the other person tightens their setting: the tightening governs new conversations, not ones already under way. Connection and meeting requests are one-off actions, so for them the check is the whole story.
Accounts created before trust levels existed carry no level and count as verified, so the gate does not touch them. It is not simply a matter of age, though: some accounts the platform creates for you — an event guest imported from Luma or Eventbrite, a profile converted into an account, an account minted through the API — start out unverified, and an account a moderator has flagged for review reads unverified however old it is.
Two event surfaces are exempt from the rule:
- A meeting request inside an event is always allowed between two attendees of that event, even if they share no community and are not connected, and it has no recipient-side preference of its own.
- Bookings opened for an event. When a host switches on "Let people at this event book a meeting with you", anyone attending that event can book them — on top of, and regardless of, the host's usual "Who can book" audience, and without any verification check. Both people must still be attending when the booking is made.
When a reach check fails you see one of:
- "This person isn't accepting messages right now." — their setting excludes you.
- "Verify your account to reach people outside your own communities. Add your LinkedIn, or start the free trial." — your account is new and not yet verified. Automatic verification is still being rolled out; if you see this message today, email support@jogl.io.
- "Your account is under review…" — contact support@jogl.io.