{"id":"69c32eb40c4b26b8585c73de","title":"2026 03 25","path":"how-to/committee/release-notes/2026-03-25","contentMarkdown":"# 25-Mar-2026 — Configurable walk leader contact method and remove login prompts ([#195](https://github.com/nbarrett/ngx-ramblers/issues/195), [#196](https://github.com/nbarrett/ngx-ramblers/issues/196))\n\n## [build 563](https://github.com/nbarrett/ngx-ramblers/actions/runs/23518862294) — [commit a83acfe](https://github.com/nbarrett/ngx-ramblers/commit/a83acfecbe744e4f2adf19517dce2a249a143401)\n\n_____\n\n### Configurable Walk Leader Contact Method\n A new **Walk Leader Contact Method** setting in admin system settings\n controls how visitors contact walk leaders. Three options are available:\n\n- **Ramblers Website** (default) — links to the leader's Ramblers contact page\n- **Contact Us** — opens the site's contact form, routing messages either directly to the walk leader (when a valid email exists) or to a configurable fallback committee role\n- **Mailto** — opt-in raw email links for groups that prefer them (not recommended due to spam email risks)\n\n### New Admin Settings\nUnder **System Settings > Event Configuration**:\n- **Walk Leader Contact Method** — select contact-us, ramblers-website, or mailto\n- **Contact Walk Leader Directly** — when using contact-us, send messages directly to the leader if they have a valid email (see **Walk Leader Contact Email Auto-Population** below)\n- **Fallback Committee Role** — committee role to receive messages when direct contact is unavailable\n\n### Admin UI Reorganisation\nThe system settings group tab is now split into two framed sections:\n\n- **Group / Area Configuration** — Ramblers area, group selection, codes, names, web URL (existing settings)\n- **Event Configuration** — population methods, contact visibility, Ramblers links, walk list view, leader contact method (new settings below)\n\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/d69af818-407b-4cbb-a1d1-e3c8070c3851.jpeg)\n\n\n### Login Prompts Removed\n All login prompts have been removed from walk leader contact links across table view, card view, and expanded leader view. Visitors can now contact walk leaders without logging in. A number of contact options are configurable, the first being the existing Ramblers link that takes you to Walks manager. However, a more focussed and immediate mechanism now available is via the secure reCAPTCHA protected \"contact-us\" form also used on the [contact-us]() page:\n\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/6a6aa70a-3613-4456-ac98-cb6d1092ebb9.jpeg)\n\n\n### Phone Numbers Visible to All\n Walk leader phone numbers are now visible to all visitors when the **Walk Contact Details Public Viewable** setting is enabled and consent has been given by the walk leader in Walks Manager, matching the table view's existing behaviour. Previously these were only shown to logged-in members.\n\n### Context-Aware Tooltips\n Leader contact links now display tooltips describing the action that will occur, e.g. \"Click to send a message to Nick B\" for contact-us,\n \"Click to visit the Ramblers website to contact Nick B\" for ramblers-website, or \"Click to email Nick B\" for mailto.\n\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/8504b895-8478-47fe-b608-435ad7fcf046.jpeg)\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/e151519b-7846-4257-af58-f7a6ab2081b2.jpeg)\n\n## Walk Leader Contact Email Auto-Population\n\nWhen using the **Contact Walk Leader Directly** setting (see above), inbound messages can be routed straight to the walk leader — but only if a valid email address exists on the walk. For groups using Walks Manager population, the synced data contains a Ramblers URL rather than an email address, so this needs to be resolved.\n\nThe **Rematch** button on the Leader tab matches the walk leader against member admin data using member-id matching. When a high-confidence match is found, the Ramblers URL in the Contact Email field is automatically replaced with the leader's actual email address. This enables:\n\n- **Direct contact** — enquiries go straight to the walk leader, not via an intermediary or fallback role\n- **No manual entry** — email addresses are resolved automatically from existing member data\n- **Group control** — each group chooses their preferred contact method: email, phone, or Ramblers URL\n\nHere's how it looks in practice:\n\n### Before Rematch\n\nWalk leader data as populated from the Walks Manager sync — the Contact Email field contains a Ramblers URL redirect rather than an actual email address.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/25a6c802-9b19-4e8c-9c76-8a9502a0b41e.jpeg)\n\n### After Rematch\n\nAfter rematching, the Ramblers URL is replaced with the walk leader's actual email address, enabling direct inbound contact to the walk leader. The green confirmation banner shows the match was successful with high confidence.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/2c2b7a15-3ef7-49d3-ace9-9d81cf9e4fbf.jpeg)\n\n\n### Unified Leader Rendering\n The previously duplicated rendering paths for Walks Manager and local walk population have been merged into a single template per component.\n A new shared `EventLeaderContactLinkComponent` eliminates the repeated contact link pattern across all three views.\n\n#### Files Changed\n- `models/system.model.ts` — WalkLeaderContactMethod enum + Organisation fields\n- `contact-us-modal.component.ts` — committeeMemberOverride support\n- `contact-us-modal.service.ts` — openContactModalForMember/ForRole methods\n- `walk-display.service.ts` — contact method logic, tooltip, lazy modal injection\n- `area-and-group-settings.ts` — admin UI with framed sections and role dropdown\n- `event-leader-contact-link.ts` — new shared contact link component\n- `event-table-view.ts` — simplified leader column using shared component\n- `walk-card-view.ts` — unified leader rendering using shared component\n- `walk-leader.ts` — simplified from ~140 to ~84 lines using shared component\n","contentHtml":"

25-Mar-2026 — Configurable walk leader contact method and remove login prompts (#195, #196)

\n

build 563 — commit a83acfe

\n
\n

Configurable Walk Leader Contact Method

\n

A new Walk Leader Contact Method setting in admin system settings\n controls how visitors contact walk leaders. Three options are available:

\n\n

New Admin Settings

\n

Under System Settings > Event Configuration:

\n\n

Admin UI Reorganisation

\n

The system settings group tab is now split into two framed sections:

\n\n

\"\"

\n

Login Prompts Removed

\n

All login prompts have been removed from walk leader contact links across table view, card view, and expanded leader view. Visitors can now contact walk leaders without logging in. A number of contact options are configurable, the first being the existing Ramblers link that takes you to Walks manager. However, a more focussed and immediate mechanism now available is via the secure reCAPTCHA protected "contact-us" form also used on the contact-us page:

\n

\"\"

\n

Phone Numbers Visible to All

\n

Walk leader phone numbers are now visible to all visitors when the Walk Contact Details Public Viewable setting is enabled and consent has been given by the walk leader in Walks Manager, matching the table view's existing behaviour. Previously these were only shown to logged-in members.

\n

Context-Aware Tooltips

\n

Leader contact links now display tooltips describing the action that will occur, e.g. "Click to send a message to Nick B" for contact-us,\n "Click to visit the Ramblers website to contact Nick B" for ramblers-website, or "Click to email Nick B" for mailto.

\n

\"\"

\n

\"\"

\n

Walk Leader Contact Email Auto-Population

\n

When using the Contact Walk Leader Directly setting (see above), inbound messages can be routed straight to the walk leader — but only if a valid email address exists on the walk. For groups using Walks Manager population, the synced data contains a Ramblers URL rather than an email address, so this needs to be resolved.

\n

The Rematch button on the Leader tab matches the walk leader against member admin data using member-id matching. When a high-confidence match is found, the Ramblers URL in the Contact Email field is automatically replaced with the leader's actual email address. This enables:

\n\n

Here's how it looks in practice:

\n

Before Rematch

\n

Walk leader data as populated from the Walks Manager sync — the Contact Email field contains a Ramblers URL redirect rather than an actual email address.

\n

\"\"

\n

After Rematch

\n

After rematching, the Ramblers URL is replaced with the walk leader's actual email address, enabling direct inbound contact to the walk leader. The green confirmation banner shows the match was successful with high confidence.

\n

\"\"

\n

Unified Leader Rendering

\n

The previously duplicated rendering paths for Walks Manager and local walk population have been merged into a single template per component.\n A new shared EventLeaderContactLinkComponent eliminates the repeated contact link pattern across all three views.

\n

Files Changed

\n\n"}