← Back to Help

Who can join, discovery, and visibility

Understand join permissions, invite links, discovery, and results visibility.

Who can join, discovery, and visibility

This page explains, in plain English:

  • who can preview an event before login
  • who can join it
  • who can see results

1) Read-only preview before login

ParcorPlus supports an anonymous read-only preview for some events.

Preview is available when either of these is true:

  • the event is public and listed
  • the viewer opens a valid invite link

Preview mode is read-only. It can show event basics (title, type, timing, route, sectors), but does not allow actions.

Blocked until login:

  • RSVP / join
  • upload or link activities
  • full results access
  • other participant actions

If preview policy is not met, login is required first.

2) Who can join

Who can join controls RSVP participation.

Typical options:

  • Public: any signed-in user can join (unless global public joining is disabled).
  • Followers / Club members: restricted to followers (personal events) or club members (club events).
  • Invite-only: joining depends on invite access.

Invite links are for controlled sharing.

  • A valid invite link can open read-only preview (even before login).
  • Joining through that link still requires login and depends on event policy.

For club-hosted non-public events:

  • if Allow invite link to admit non-members is off: non-members can view by link but cannot join.
  • if on: non-members with the link can join (subject to capacity).

4) Discovery (listed vs unlisted)

Discovery controls whether an event appears in listings/search.

  • Listed: appears to the intended audience.
  • Unlisted: hidden from normal lists; requires direct link or existing rights.

Use unlisted for private logistics or controlled pilots.

5) Results visibility

Results visibility controls who can view standings. Full leaderboard/results always require login first.

Common patterns:

  • Public results: broad visibility.
  • Followers/club scope: limited to that audience.
  • Participants-only: visible to host/admin + riders marked going.

Interested is not treated as participant for participant-only views.

6) Attendee list visibility

Current behavior is designed to reduce social friction:

  • attendee count can be shown to viewers
  • attendee names/list can be limited to host/admin and going participants

7) Lifecycle gates (important)

Permissions also depend on event status:

  • RSVP joining: open window logic
  • Upload/linking activity: active only

So a user may be allowed by access policy but still blocked by lifecycle state.

If you want low confusion for most events:

  1. Set Who can join first.
  2. Keep discovery/results on defaults unless you have a clear reason.
  3. Enable invite link when you want easy sharing.
  4. For club non-public events, explicitly decide non-member invite policy.
  5. Test once while logged out to confirm what first-time visitors will see.