Finding and connecting with people

The network has three parts: Members for finding people, Connections for managing existing connections, and Matches for platform suggestions.

Finding people

Network → Members lists every active member, and each person has a profile page showing a fixed set of fields: name, bio, specialty, intent, interests, match tags, country, the organisations they belong to, and — where one exists — your match score and connection status with them.

The field set is identical for every signed-in viewer. No filtering is applied per viewer, so a sparse profile indicates incomplete information rather than restricted visibility. Account settings are not included: no email address, and no notification or billing detail.

The visibility switch is about the public web, not about other members

Settings → Profile → Visibility carries one switch, Show my profile publicly. It governs your logged-out profile page and whether you appear in the public member directory and map. It does not change what other signed-in members see — they get the fields above either way, and you still appear in Network → Members. Signing in is what gets you that view.

To withhold information from other members, leave the field empty; the switch does not achieve this.

Connection requests

Connecting is bilateral: a request is sent, and the recipient accepts or declines.

A connection has four states, on which the Connections screen filters: Pending, Accepted, Declined and Completed.

The Connections list filters by state — All, Pending, Accepted, Completed.Open /a/network/connections in the app

×

State	What you can do
Pending — sent by you	Withdraw, until answered. Available to the sender only
Pending — received by you	Accept or decline
Accepted	Collaborate; either party may later mark it Completed
Completed	Closed, with an outcome recorded. See below

Declining notifies the sender. The action is not silent.

Withdrawal is possible only while a request is pending, and only by the sender. A request that has been accepted or completed cannot be withdrawn.

Requests can be accepted or declined in bulk from the list.

Completing a connection

Accepted is not the end state. Either participant — not just the person who received the request — can mark a connection Completed, and completing it records:

Outcome	One of: collaborated, opportunity, knowledge exchange, or simply connected
Feedback	Up to 500 characters, optional

Completion is frequently omitted, and it is what distinguishes a connection that produced a collaboration from one that produced a conversation. Only completion records that distinction.

Note the asymmetry: acceptance is available to the recipient alone, whereas completion is available to either party.

Where a connection came from

The Connections list includes an Origin column, as a request can arrive by four routes: direct, browse, match, or opportunity. The last indicates a connection made in relation to a specific listing.

That route changes one rule: normally only one connection may exist between two members, but an opportunity connection is scoped to its opportunity. The same two members can therefore connect again in relation to a different listing without removing the first.

Notifications for all of this are controlled under Notifications — Connection alerts.

Suggested connections

Network → Matches suggests members based on shared areas of work. It requires Solo plan.

Each suggestion carries a relevance score. Weak matches are excluded rather than ranked low, so the list is short by design and contains only suggestions above the threshold.

Note

Connection matching and opportunity matching are separate systems sharing a term. This page covers member matching; opportunity matching is documented separately.

ConnectionsNetwork → Connections

MembersNetwork → Members