# 14-May-2026 — lead button, auto-expand & risk-assessment control / config, sub-tab order [closes #266](https://github.com/nbarrett/ngx-ramblers/issues/266)

## [build 642](https://github.com/nbarrett/ngx-ramblers/actions/runs/25832541886) — [commit e3115da](https://github.com/nbarrett/ngx-ramblers/commit/e3115dabbf57d4bedae8259951beed10092f4844)

_____

- Card lead button: any logged-in user (including admin) now sees *lead*
on awaiting-leader cards instead of the legacy hardcoded *view* anchor
or admin-only *edit* button. For admins the button becomes a split
dropdown with *lead* as the default action and *edit* as a secondary
option so an admin can step into an unclaimed walk slot to tweak
details without auto-assigning themselves as walk leader.
toWalkAccessMode refactored to a const-based helper that prioritises
AWAITING_LEADER over admin precedence; walk-display.service.edit()
accepts a bypassLeaderInit flag that drives an ?as=edit query param;
walk-edit full-page honours the param to override walkAccessMode to
"edit" mode on load (no auto-leader-init).

_____



*Same card seen as an admin - the button becomes a split, with lead as the default click and a caret toggle alongside it.*

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/3c82098b-e8f2-4106-8154-f5514cda2125.png)

*Admin opens the caret and gets an edit option, which navigates to the walk editor with ?as=edit so no auto-leader-init runs.*

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/ed7a6462-f34c-4c4b-8f64-57d61ba79de4.png)

*Walk card action button as a regular member sees it - a plain yellow lead button, no admin options.*

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/6ea304dc-8bcd-410f-95d8-0dd17e1352f2.png)

- "Our next walk" + page-nav auto-expand: introduce
walkDetailsComplete() and require it from isNextWalk() and from the
walks card-list first-walk auto-expand. Empty Sunday slots no longer
win the next-walk slot.




![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/2480d06d-3677-49df-aaec-440cf612aed0.png)

<br>

*Walks listing - the first walk auto-expands only when walkDetailsComplete() is true, so empty Sunday slots no longer win the next-walk slot.*

- Risk Assessment tab: gate on walksConfig.requireRiskAssessment in
addition to display.allowEdits(walk). Promote walksConfig from
private to public so the template can read it. Validation path
already gated.




![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/6d161ba7-3c40-491d-adfc-2756d632241e.png)

<br>

*Walks Configuration > General - the requireRiskAssessment checkbox is the source of the new guard.*

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/4cc31fef-1820-4677-8da0-957a3884e0aa.png)

<br>

*Walk editor tab strip with the Risk Assessment chip on the right, shown only when the requireRiskAssessment toggle is on and the user can edit the walk.*

- Walk Details sub-tabs: reorder DetailsTab enum to Venue, Route,
Route & Venue and set the component's tabs array explicitly so the
rendered order is deterministic.

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/9d9013c8-f478-4cb8-bf78-58017fef6133.png)

*Walk Details sub-tabs now render Venue, Route, Route & Venue in that fixed order.*