# Trail Sentinel — full content (English)

> Trail maintenance management software for trail networks, outdoor centers, ski resorts and sport clubs — bike, hiking, ski, ATV and snowmobile trails. GPS task tracking, offline mode. Used in Canada, the United States and Europe.

This file contains the complete English content of trail-sentinel.com, concatenated for LLM ingestion. The same content is available in French at `https://trail-sentinel.com/fr/llms-full.txt`.

Site: https://trail-sentinel.com/en


## Home


### Hero

**Badge**: Quebec · 10+ centers · 3 countries
**Title**: An interactive trail map dedicated to trail maintenance task management.
**Subtitle**: Report issues from the field and prioritize your trail maintenance projects — all in one tool.
**Trust Line**: Used across Canada, the United States and Europe by outdoor centers, multisport centers, bike centers and managers of all types of trails — hiking, mountain biking, cross-country skiing, snowshoeing, bike paths, ATV and snowmobile.
**Cta Primary**: Book a demo
**Cta Secondary**: See features

### Section Nav

**Overview**: Overview
**Tasks**: Tasks
**Structures**: Structures
**Field**: Field
**Community**: Community

### Features Grid

**Title**: Here's what Sentinel does for you
**Subtitle**: From the issue reported in the field to the PDF report for your board of directors — all the features your organization needs, on a single platform.
**Explore Label**: Explore

#### Cards

**Tag**: Core product
**Title**: Spot, document, resolve
**Teaser**: Every maintenance issue becomes a geolocated task with photos, priority and assignment.
**Highlight**: 30 seconds to report an issue from the field.
**Tag**: Infrastructure
**Title**: Bridges, signs, inspections — fully documented
**Teaser**: Inventory your structures, inspect them with your own forms, produce official PDF reports.
**Highlight**: Custom forms + one-click PDF export.
**Tag**: Planning
**Title**: From isolated tasks to projects that move forward
**Teaser**: Group your tasks into a project to keep a clear overview and track progress in real time.
**Highlight**: Real-time progress, zero manual updates.
**Tag**: Team
**Title**: A team that contributes, without breaking things
**Teaser**: Volunteers, seasonal staff, partners — each with access to what concerns them, at the right permission level.
**Highlight**: Granular roles and access zones.
**Tag**: Field
**Title**: Works where you actually work
**Teaser**: No cell signal? The app works anyway. Designed for cold hands, thick gloves and bright sunlight.
**Highlight**: Offline creation — tasks, structures and reports.
**Tag**: Impact
**Title**: Quantify your impact, justify your resources
**Teaser**: Dashboards, exportable reports, complete history — ready for your partners and funders.
**Highlight**: PDF and Excel exports with no double entry.

### Signatures


#### Tasks

**Tag**: At the heart of daily work
**Title**: From the fallen tree to the proof of repair
**Description**: Your team finds a fallen tree in the forest. In 30 seconds, the location is geolocated, the problem type is identified, photos are captured and the task is sent to the team. Each member gets a notification, the technician navigates to the exact spot, documents the repair and closes the task. Everything is tracked, everything is proven.
Geolocated pin or segment, with unlimited photos
4 priority levels so urgency is never lost
Complete history, accessible year after year
**Cta Label**: See how it works

#### Structures

**Tag**: Your inventory, alive
**Title**: Your bridges, your signs, your inspections — your way
**Description**: Every structure on your network becomes a living file. Build your own inspection forms with the questions that matter to you, fill them in on the field, export an official PDF report when you need it for a partner or insurer. Otherwise, everything stays neatly archived in the app.
Fully customizable inspection forms
PDF exports branded with your organization
Multi-year inspection history, comparable
**Cta Label**: See how it works

#### Field

**Tag**: Built for the field
**Title**: Works where you actually work — not just in the office
**Description**: No cell service? Keep creating your tasks, your structures and your inspection reports — photos and media included. Everything saves locally on the phone. As soon as you're back in a covered area, synchronization happens automatically. You lose nothing. You retype nothing.
Create tasks, structures and inspection reports offline
Photos and media captured without signal, kept on the device
Automatic sync on return online
**Cta Label**: See how it works

### Community

**Tag**: Community plan
**Title**: Running a small community organization? Get Sentinel for free.
**Subtitle**: Early-stage centers, volunteer clubs and donation-driven organizations can access the full platform at no cost. Tell us about your organization — we'll review your eligibility together.
**Cta**: Discover the Community plan

### Testimonial

**Translated From**: Translated from French
**Link Label**: Read the full testimonial

### Photo Bands

**Thaw**: Spring thaw · ruts and drainage
**Bridge**: Timber boardwalk · autumn inspection

### Final Cta

**Title**: Your network deserves better than an Excel file
**Subtitle**: Create your account in minutes and see how Sentinel fits your reality — size, team, seasonal constraints. 30-day free trial, no credit card required.
**Cta Primary**: Start trial
**Cta Secondary**: See features

### Newsletter

**Tag**: NEWSLETTER
**Title**: Get our updates
**Subtitle**: New features, trail management guides and case studies — one email a month, no more.
**Name Placeholder**: Your first name
**Email Placeholder**: your@email.com
**Submit**: Sign up
**Submitting**: Sending…
**Success**: Thanks! You're on the list.
**Error Email**: Please enter a valid email.
**Error Generic**: Something went wrong. Please try again later.
**Error Rate Limited**: Too many attempts. Please try again in a few minutes.
**Error Verification**: Please complete the spam verification before signing up.
**Privacy**: We never share your email. Unsubscribe in one click.

## About us

**Title**: About

### Hero

**Title**: Built in the field, for the people who keep trails alive.
**Subtitle**: Behind Sentinel there's a story of volunteering, trails and a genuine desire to do things right. Here's who we are and why we do what we do.

### Mission

**Tag**: Our mission
**Statement**: Helping trail networks and outdoor centers get structured, better organized, and invest their energy — and their money — in the right place.
**P1**: Sentinel wasn't born in a boardroom, but in the field. Before it was a product, it was the work of someone who genuinely cares about trails, who truly wants networks to work, to last and to grow. The goal was never to make money at all costs: it's to help centers develop and get better organized.
**P2**: We built Sentinel as a concrete tool, designed to bring something extra to teams and their members. A well-structured organization wastes less time, operates more calmly and puts every dollar where it truly matters. That's the whole point of Sentinel: giving teams the means to do their work well.

#### Pillars

**Title**: Get structured
**Description**: Centralize information and ways of working so the whole team moves in the same direction.
**Title**: Operate better
**Description**: Bring visibility into what's happening on the trails and smooth out the day-to-day, even offline.
**Title**: Invest where it counts
**Description**: See clearly where time and money go, so you can prioritize what has the most impact.

### Team

**Tag**: The team
**Title**: Behind Sentinel
**Subtitle**: Sentinel is driven by its founder, close to the field and to the teams who use it every day.

### One

**Name**: Francis Lessard
**Title**: Founder and developer of Sentinel
**Content**: Volunteer at Sentiers du Moulin
**Bio**: Francis has been building software for about twenty years. He designs products that make life easier for businesses — less paperwork, more action. On the other side of his life, he volunteers at Sentiers du Moulin.

The idea for Sentinel was born there, on the ground. Back then, nothing really existed to manage trail maintenance: teams juggled between Facebook groups, text messages and scraps of paper, and issues kept slipping through the cracks. The opportunity was obvious — save teams time, give real visibility into what's happening on the trails, and help networks finally get organized.

Sentinel is now in its fourth year. The first ones were spent exploring and validating that the idea actually held up: an app that works for real in the field, even without cellular coverage. After a lot of iterations, Sentinel was officially launched in year two. It has been evolving ever since, shaped by the people who use it every day.

## Pricing

**Title**: Pricing
**Subtitle**: Three plans built for organizations managing trails, infrastructure and field teams.
**Meta Description**: Sentinel pricing: Community, Standard and Pro plans. 30-day free trial on Standard and Pro. Built for early-stage centers, volunteer clubs and established trail networks.

### Hero

**Title**: Plans for every kind of organization
**Subtitle**: Whether you're a small community group or an established network, pick the plan that matches your reality.

### Tiers


#### Community

**Name**: Community
**Tagline**: For small organizations
**Price Monthly**: Custom
**Price Yearly**: Custom
**Suffix Monthly**: 
**Suffix Yearly**: 
**Yearly Note**: 
**Cta**: Apply
Access to every feature
Personal onboarding
Built for young centres and volunteer clubs

#### Field

**Name**: Field
**Tagline**: Tasks, in the field
**Price Monthly**: $35
**Price Yearly**: $385
**Suffix Monthly**: / month
**Suffix Yearly**: / year
**Yearly Note**: 1 month free
**Cta**: Start trial
Geolocated tasks, with photos
A mobile app that works with no signal
For teams who want the field sorted first

#### Standard

**Name**: Standard
**Tagline**: The essentials to get organized
**Price Monthly**: $75
**Price Yearly**: $825
**Suffix Monthly**: / month
**Suffix Yearly**: / year
**Yearly Note**: 1 month free
**Cta**: Start trial
Projects and team planning
Conversations attached to the work
Hours worked, logged

#### Pro

**Name**: Pro
**Tagline**: The whole network
**Price Monthly**: $105
**Price Yearly**: $1,155
**Suffix Monthly**: / month
**Suffix Yearly**: / year
**Yearly Note**: 1 month free
**Cta**: Start trial
**Popular Label**: Recommended
Structures and inspection reports
Season checklists and published conditions
Exports, bulk editing and custom referentials

### Eligibility

**Title**: Community plan — eligibility
**Description**: The Community plan is reserved for small organizations managing trails with limited resources: early-stage centers, organizations looking to structure their operations, volunteer clubs and groups, organizations running on donations. Legal status doesn't determine eligibility — your organization's economic reality does. To qualify, you'll first need to reach out to our team so we can review your eligibility together. Free access is granted for a one-year period and is reassessed annually based on the organization's economic reality.
**Footnote**: Special conditions

### Comparison

**Title**: Compare plans
**Subtitle**: All of Sentinel's features, and what's included in each plan.
**Feature Column**: Feature

#### Features

**Name**: Tasks
**Description**: Report, assign and track the work to do, with photos and a position on the map.
**Name**: Mobile app
**Description**: iOS and Android, usable with no cell signal and synced when you get back.
**Name**: Conversations
**Description**: Talk on a task, a structure or a project instead of over text messages.
**Name**: Projects
**Description**: Group tasks into worksites, track progress and name someone in charge.
**Name**: Time tracking
**Description**: Count hours per member and per task, for your reports and grant applications.
**Name**: Map annotations
**Description**: Trace a zone, a line or points on a task's map.
**Name**: Planning
**Description**: Spread the week's work across your members and groups.
**Name**: Structures
**Description**: Inventory bridges, boardwalks, culverts and signs, and track their condition.
**Name**: Inspection reports
**Description**: Scored inspection forms, with automatic recurrence based on the score.
**Name**: Data export
**Description**: Export tasks to Excel, reports to PDF, a project to a single file.
**Name**: Bulk editing
**Description**: Change the status, owner or due date of dozens of tasks at once.
**Name**: Checklists
**Description**: Recurring inspection templates, deployed per trail for season opening.
**Name**: Trail conditions
**Description**: Publish each trail's condition on your website with one link.
**Name**: Custom task types
**Description**: Create your own work types and their icons.
**Name**: Difficulty levels
**Description**: Define your own rating scale, its colours and its order.

### Faq

**Title**: Questions about pricing?
**Subtitle**: Let's talk about your organization and find the plan that fits.
**Cta**: Contact us

### Interval

**Monthly**: Monthly
**Yearly**: Yearly
**Savings**: 1 month free

## Features

**Title**: Features
**Breadcrumb**: Features
**Meta Description**: Every Trail Sentinel feature for trail maintenance: geolocated tasks, structures and inspections, trail conditions, checklists, trail mapping, projects, team, field work and impact reports.
**Tag**: THE PLATFORM
**Hero Title**: Trail maintenance features
**Hero Description**: Everything you need to run your trail network, from a field report to the annual summary. One map, one mobile app, one team.
**Cta Title**: See the platform on your own trails
**Cta Subtitle**: Your tasks, structures and projects in Trail Sentinel — with your network, not sample data.
**Cta Primary**: Start trial

### Mapping

**Title**: Trail Mapping Software for Trail Networks
**Menu Description**: Your whole network on one map
**Meta Description**: Trail mapping software for trail networks, outdoor centers and ski resorts. Put your whole network on one interactive map, geolocate every task and structure, and keep the map usable offline on iOS and Android.
**Tag**: TRAIL NETWORK MAPPING
**Hero Title**: Your whole trail network on one map
**Hero Description**: Stop rebuilding your network from old plans, screenshots and what your volunteers remember. Sentinel brings every trail, every task and every structure onto a single interactive map — on the web at the office, on the phone in the field, with or without signal.

#### Section1

**Tag**: 01 — The full picture
**Title**: One map, the whole network, always current
**Description**: You open the dashboard and you see your entire network: trails by activity and difficulty, maintenance tasks still open, structures waiting on an inspection. No more cross-referencing three files to figure out where a sector stands. When a crew creates a task in the field, it shows up on the office map.
Trails, tasks and structures on the same base map
Filter by activity, difficulty and status
Updated as soon as a crew records something on site

#### Section2

**Tag**: 02 — Out on the trail
**Title**: Every problem pinned exactly where it is
**Description**: A crew member comes across a tree down across the trail. They pull out their phone, take a photo, pick the problem type: the task is created with its GPS position, on the right trail. Nobody has to describe "about 300 metres past the second junction". The next crew opens the map and walks straight to it.
GPS position recorded automatically on creation
Photos and problem type attached to the point
The task attaches itself to the right trail

#### Section3

**Tag**: Offline
**Title**: The map keeps working where cell coverage stops
**Description**: Most trails sit outside coverage. Sentinel's map stays usable with no signal: you still see your trails, your tasks and your structures, and you keep creating new ones. Everything syncs when you are back in coverage, without anyone having to think about it.
Map, tasks and structures viewable with no signal
Create tasks and reports offline
Automatic sync when the signal comes back
**Highlights Title**: What a network map has to do

#### Highlights

**Title**: The whole network
**Description**: Your trails, your sectors, your structures and your tasks on one base map, instead of scattered across separate files.
**Title**: Web, iOS and Android
**Description**: The same map at the office and in the field. What the phone records, the dashboard shows.
**Title**: Usable off-grid
**Description**: The map does not stop at the edge of cell coverage. You view and you create; the sync catches up.
**Faq Title**: Frequently asked questions
**Cta Title**: See your network as it actually is
**Cta Subtitle**: One interactive map that holds your trails, your tasks and your structures — at the office and in the field, with or without signal.
**Cta Primary**: Start trial

#### Definition

**Title**: What is network mapping in Sentinel?
**Body**: Mapping is the layout of your trails: their geometry, their name, their difficulty and the activities they allow, imported from your GPX files. It is the backbone of everything else — tasks, structures and conditions all attach to a trail.
**Replaces**: Old paper maps, screenshots of maps, and GPX files scattered across several computers.
**Where**: Network built on the web, consulted on the phone in the field, with or without cell coverage.

### Tasks

**Title**: Maintenance Tasks
**Menu Description**: Spot, document, resolve
**Description**: From the issue spotted in the forest to the issue resolved, everything happens in Sentinel.
**Meta Description**: Trail maintenance task management. Geolocated reporting, photos, priorities, assignment, complete task lifecycle tracking.
**Tag**: Core product
**Hero Title**: Spot, document, resolve — without missing a thing
**Hero Description**: Every maintenance issue becomes a geolocated task with photos, priority and assignment. From the report in the forest to the documented repair, you keep track of everything.

#### Section1

**Tag**: 01 — Report an issue
**Title**: Reported in 30 seconds
**Description**: You come across a fallen tree? Open the app — it geolocates you automatically and detects the trail for you. Take a photo, choose the problem type. It's reported, geolocated, dated. The team gets notified. No one will forget.
Meter-precise geolocation, even deep in the forest
Unlimited photos, automatically geotagged
Instant notification to the whole team

#### Section2

**Tag**: 02 — Prioritize and assign
**Title**: Turn a list of problems into an action plan
**Description**: On the web dashboard, view all open tasks on a map or in a kanban by priority. Assign to a team member, group into a project. You go from firefighting mode to management mode.
4 priority levels: critical, high, medium, low
Individual or group assignment
Map view or kanban view by priority
**Kpi Open**: Open
**Kpi In Progress**: In progress
**Kpi Completed**: Completed
**Col New**: New
**Col In Progress**: In progress
**Col Done**: Done

#### Mockup

**Task Number**: New task
**Header Subtitle**: Panorama Trail · Section 4
**Step Label**: Step
**Slide1Title**: Locate the problem
**Slide1Meta**: 45.52° N · 73.58° W · ± 3 m
**Slide1Button**: Confirm
**Slide2Title**: Fallen tree
**Slide2Meta**: Problem type identified
**Slide2Button**: Next
**Slide3Title**: Photos captured
**Slide3Meta**: Automatically geotagged
**Slide3Button**: Save
**Slide4Title**: Task sent
**Slide4Meta**: Team notified · Marc R. assigned

#### Kanban Browser Mockup

**Workspace Name**: Mont-Valin Park
**Lang Code**: EN
**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Nav Dashboard**: Dashboard
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav Trails**: Trails
**Nav Activities**: Activities
**Nav Difficulties**: Trail difficulties
**Nav Task Types**: Task types
**Nav Structure Types**: Structure types
**Activity Label**: Mountain biking
**Header Title**: Tasks
**Header Subtitle**: Manage and track your open tasks
**Create Button**: Create a task
**Filter Assignee**: Assigned to
**Filter Task Type**: Task type
**Filter Advanced**: Advanced filter
**Col New**: NEW
**Col Ready**: READY
**Col In Progress**: IN PROGRESS
**Col Done**: DONE
**Col Waiting**: ON HOLD
**Task Sign**: Sign
**Task Fallen Tree**: Fallen Tree
**Task Hanger**: Hanger
**Task Broken Plank**: Broken Plank
**Today**: Today at
**Time New1**: 1:17 PM
**Time New2**: 11:33 AM
**Time New3**: 10:57 AM
**Time New4**: 10:41 AM
**Time New5**: 10:40 AM
**Time New6**: 10:06 AM
**Time New7**: 9:36 AM
**Time New8**: 8:23 AM
**Time Map New1**: 2:28 PM
**Time Map New2**: 1:02 PM
**Date In Progress1**: Tue. Jul 15, 4:45 PM
**Date In Progress2**: Sat. Jul 12, 2:19 PM
**Done Title**: Completed tasks
**Done Description**: Tasks moved here are marked as completed and hidden from this view.
**Notif Title**: Status updated
**Notif Now**: now
**Panel Title**: View task
**Panel Conversation**: Conversation
**Panel Add Time**: Add Time
**Panel Completed**: Completed
**Panel Task Date**: Tue Nov 4, 5:36 PM
**Panel Priority Critical**: CRITICAL
**Panel Activity Label**: MOUNTAIN BIKING
**Panel Estimated Label**: ESTIMATED TIME
**Panel Estimated Value**: 2 HOURS
**Panel Trail Name**: 38 - MARIE-HÉLÈNE PRÉMONT VÉLOROUTE
**Panel Assignee Label**: ASSIGNED TO
**Panel Assignee Name**: Sophie Lavoie
**Panel Author Label**: AUTHOR
**Panel Author Name**: Marc Dubois
**Panel Media Title**: Media
**Panel Edit**: Edit

#### Section3

**Tag**: 03 — No more lost messages
**Title**: No more reports lost in group chats
**Description**: A fallen tree reported in a Messenger, Facebook or WhatsApp group. Someone replies "we'll look into it." A few weeks later, the message is buried under the group's other conversations. No photo, no precise location, no follow-up. With Sentinel, every report is geolocated, documented and tracked to resolution.
No more information buried under group chatter
No more "where exactly is it?" with no answer
No more forgotten tasks with no proof or follow-up
**Group Name**: Trail Maintenance
**Members**: 12 members
**Msg1Author**: Marc R.
**Msg1Text**: There's a big tree down on the north trail, near the bridge
**Msg1Time**: 9:42 AM
**Msg2Author**: Julie T.
**Msg2Text**: Ok we'll look into it
**Msg2Time**: 10:15 AM
**Msg3Author**: Marc R.
**Msg3Text**: Has this been taken care of?
**Msg3Time**: 3 days later
**Noise1Author**: Paul L.
**Noise1Text**: Group outing Saturday, who's in?
**Noise1Time**: Mon
**Noise2Author**: Sophie B.
**Noise2Text**: Beautiful view this morning at the lookout
**Noise2Time**: Wed
**Noise3Author**: Jean D.
**Noise3Text**: Anyone know tomorrow's opening time?
**Noise3Time**: Fri
**Later Badge**: 14 days later
**Forgotten**: Report forgotten
**No Photo**: No photo
**No Location**: No location
**No Tracking**: No tracking
**Highlights Title**: Why it changes everything

#### Highlights

**Title**: Meter-precise location
**Description**: Every task is precisely geolocated. Find the problem even in a sector you've never been to, without vague descriptions.
**Title**: Photos that tell the whole story
**Description**: Photo at reporting, photo during the intervention, photo after the repair. Complete documentation for your team, partners, and insurers.
**Title**: Clear prioritization
**Description**: Critical, high, medium, low. Your teams instantly see what needs to be done this week versus next fall.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: What types of tasks can I create?
**Answer**: A point marker (a fallen tree, a broken sign) or a segment over a distance (eroded zone, drainage to redo). Both formats cover the vast majority of maintenance issues.
**Question**: Can a task be assigned to multiple people?
**Answer**: Yes. A task can be assigned to an individual or a group, depending on your organization.
**Question**: What happens to a closed task?
**Answer**: It stays in the trail's history, viewable at any time. Useful for proving maintenance was done, or for detecting a recurring problem at the same spot.
**Question**: Does it work without network?
**Answer**: Yes. You can create tasks, take photos and document without any cellular network. Everything syncs automatically as soon as signal returns.
**Cta Title**: Stop losing problems in the forest
**Cta Subtitle**: With Sentinel, a reported problem is a problem that will be documented, prioritized and resolved.
**Cta Primary**: Start trial
**Cta Secondary**: See features

#### Benefits

Report in 30 seconds from the field, even without network
Precise geolocation — find the problem even if you've never been there
Before, during and after photos to document the full cycle
4 priority levels so urgency is never lost
Assign to a member or group, with instant notification
Complete history per trail, accessible anytime

#### How It Works

**Title**: Report in 30 seconds
**Description**: Open the app — it geolocates you and detects the trail automatically. Take a photo, choose the problem type. The task is dated and sent to the team.
**Title**: Prioritize and assign
**Description**: From the web dashboard, sort by priority, assign to a technician, group into a project. You go from firefighting mode to management mode.
**Title**: Document the repair
**Description**: The technician navigates to the exact spot, makes the repair, adds a before/after photo. The task closes, the history stays. Everything is tracked.

#### Use Cases

Reporting fallen trees, damaged bridges, clogged drainage
Tracking interventions with photo evidence for insurers
Coordinating maintenance work days with volunteers
Documenting eroded sections or hazardous zones
Planning repairs by priority and season

#### Definition

**Title**: What is a maintenance task in Sentinel?
**Body**: A maintenance task is an issue found on the network, recorded at the exact spot where it sits: a tree across the trail, a torn-off sign, a slippery boardwalk. It carries its GPS position, its photos, its type, its priority, the person responsible and its progress — from the report in the woods to the documented repair.
**Replaces**: Photos dropped in a group chat, to-do lists on paper, and emails you dig up three weeks later.
**Where**: Created and closed on the phone in the field, tracked on the web at the desk.

### Structures

**Title**: Structures & Inspections
**Menu Description**: Inspect, document, report
**Description**: Every structure on your network becomes a living file — inspected, documented, reported.
**Meta Description**: Trail infrastructure management. Inventory your structures, inspect with custom forms, generate official PDF reports. Bridges, signs, lookouts.
**Tag**: INFRASTRUCTURE & REPORTS
**Hero Title**: Your structures inspected, documented, reported — your way
**Hero Description**: Every bridge, every walkway, every sign — inventoried and inspected. Create your own inspection forms, generate official PDF reports when needed, or simply keep the history in the app. You choose the level of formality based on the context.

#### Kanban Browser Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Nav Dashboard**: Dashboard
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav Trails**: Trails
**Nav Activities**: Activities
**Nav Difficulties**: Trail Difficulties
**Nav Task Types**: Task types
**Nav Structure Types**: Structure types
**Activity Label**: Mountain bike
**Header Title**: Structures
**Header Subtitle**: Manage and inspect your structures
**Create Button**: Create a structure
**Filter Structure Type**: Structure type
**Filter Advanced**: Advanced filter
**Col High Risk**: HIGH RISK
**Col Medium Risk**: MEDIUM RISK
**Col Low Risk**: LOW RISK
**Col No Risk**: NO RISK
**Col Not Evaluated**: NOT EVALUATED
**Type Bridge**: Wooden bridge
**Type Berm**: Berm
**Type Jump**: Jump
**Type Sign**: Sign
**Type Drain**: Drain
**Type House**: Cabin
**Structure Pont Liberte**: Liberty Bridge
**Structure Berm Virage**: Grand Turn Berm
**Structure Drain Nord**: North Sector Drain
**Structure Saut Belvedere**: Belvedere Jump
**Structure Panneau Carrefour**: Crossroads Sign
**Structure Pont Amazone**: Amazone Bridge
**Structure Saut Panorama**: Panorama Jump
**Structure Berm Enduro Sud**: Enduro South Berm
**Structure Panneau Liberte**: Liberty 55 Sign
**Structure Cabane Relais**: Relay Cabin
**Panel Add Report**: Add report
**Panel Conversation**: Conversation
**Panel Info Trail**: LIBERTY 55
**Panel Info Next Reminder**: NEXT REMINDER
**Panel Info Next Reminder Date**: APR 8, 2027
**Panel Reports Title**: Reports
**Panel Reports Year**: 2026
**Panel Reports By**: By
**Panel Report Author**: Marc Rondeau
**Panel Report Date1**: Wed Apr 8, 9:09 PM
**Panel Report Date2**: Fri Mar 20, 7:43 AM
**Panel Report Date3**: Fri Mar 20, 7:35 AM
**Panel Report Date4**: Fri Mar 13, 3:02 PM
**Panel Report Date5**: Fri Mar 13, 3:02 PM
**Panel Report Date6**: Fri Mar 13, 2:49 PM

#### Section1

**Tag**: 01 — Inspect on site
**Title**: Quick inspection or detailed form — your choice
**Description**: You arrive at a bridge for the annual inspection. Pull up the form your organization prepared: specific questions, checkboxes, photos, severity levels. Or, if it's an informal check, add a quick note with a few photos. Either way, everything is geolocated, dated, attached to the structure's file. History builds itself, inspection after inspection.
Custom forms or free-form inspections, depending on context
Photos, severity levels, checkboxes
Everything geolocated and attached to the structure file

#### Section2

**Tag**: 02 — Your forms, your rules
**Title**: Design your own inspection forms
**Description**: Your organization has specific inspection requirements? Build your own questionnaires from the web dashboard: multiple choice, free text, photos, checkboxes, severity levels. One form per structure type — bridges, walkways, signs — or a universal form. Your teams fill it in the field, you receive structured, comparable data year after year.
Unlimited fully customizable questionnaires
One form per structure type or a universal form
Published in one click, deployed to your team's phones
**Form Title**: Bridge Inspection
**Field Deck**: Deck condition
**Field Guardrails**: Guardrails
**Field Severity**: Severity level
**Field Photos**: Photos
**Field Notes**: Inspector notes
**Deploy Label**: Deploy
**Deployed Label**: Deployed to 3 devices
**Phone Header**: Inspection
**Phone Subtitle**: Bridge — North Sector

#### Section3

**Tag**: 03 — From field to official report
**Title**: One field inspection, one report ready to share
**Description**: A field inspection immediately becomes a viewable report at the office. For internal needs, everything stays in the app — photos, form answers, notes, history. For your partners, insurers, board of directors or funding bodies, export an official PDF in one click: professional layout, your organization's logo, branded header, all photos attached.
Professional PDF with your logo and branded header
All photos and form data included automatically
Same work serves internal team and external partners
**List Title**: Inspection Reports
**Report1Name**: Bridge — North Sector
**Report1Date**: Apr 8, 2026
**Report1Status**: OK
**Report2Name**: Lookout — Summit
**Report2Date**: Apr 5, 2026
**Report2Status**: Monitor
**Report3Name**: Sign — Main Trail
**Report3Date**: Apr 2, 2026
**Report3Status**: OK
**Export Button**: Export PDF
**Pdf Title**: Inspection Report
**Pdf Number**: RI-2026-042
**Pdf Structure**: Bridge — North Sector
**Pdf Type**: Wooden bridge · 12 m
**Pdf Badge**: PDF ready
**Highlights Title**: Everything you need for your infrastructure

#### Highlights

**Title**: Structured inventory
**Description**: Bridges, walkways, signs, lookouts, tables, stairs, shelters... You define the types that match your network. Each structure is geolocated, linked to a trail, tracked over time.
**Title**: Custom inspection forms
**Description**: Build your own questionnaires with the questions that matter to you. Mandatory or optional, depending on your context. Same forms for the whole team — data is finally comparable.
**Title**: PDF reports on demand
**Description**: Need an official report for a partner, insurer, or board of directors? One click, one clean PDF. Don't need it? Everything stays in the app. Formality adapts to the situation.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: What does Sentinel consider a "structure"?
**Answer**: Any permanent physical infrastructure on your network: bridges, walkways, stairs, lookouts, signs, tables, benches, shelters. You choose the types that apply to you and can add more.
**Question**: Can I create my own inspection forms with my own questions?
**Answer**: Yes. You build your questionnaires from the web dashboard: free text, multiple choice, checkboxes, photos, severity levels. You can have a different form per structure type, or a universal form.
**Question**: Do I have to fill out a form to document an inspection?
**Answer**: No. You can also do a free-form inspection: a few notes, a few photos, and it's in the file. The form provides structure when useful, the free-form inspection gets the job done when it's not.
**Question**: Are the PDF reports branded with my organization?
**Answer**: Yes. Your logo appears on the PDF produced. It's ready to use for your partners, insurers, grant applications — no rework in Word needed.
**Cta Title**: Stop losing the memory of your structures
**Cta Subtitle**: A living inventory, guided inspections when needed, official reports when you need them. The rest of the time, your team works — you never lose a single piece of data.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: What is a structure and an inspection report?
**Body**: A structure is a fixed asset on your network — bridge, boardwalk, stairs, lookout, sign — inventoried with its position and its history. An inspection report is the questionnaire you defined yourself, filled in on site on a given date: every answer is kept, and you either export an official PDF or simply keep the record in the app.
**Replaces**: The inspection binder, the paper form that has to be retyped back at the office, and the memory of whoever was there last year.
**Where**: Questionnaires defined on the web, inspections filled in on the phone in front of the structure.

### Trail Conditions

**Title**: Trail conditions
**Menu Description**: Show your trail status, live
**Description**: Build your condition boards, organize them by activity, and share them publicly with an embeddable widget.
**Meta Description**: Trail condition management and public display. Boards by activity, folder organization, embeddable widget for your website, automatic updates when your crews work in the field.
**Tag**: TRANSPARENCY & COMMUNICATION
**Hero Title**: Your trail conditions, live and one-click shareable
**Hero Description**: Organize trails into boards by activity, group them by type with folders, and publish conditions live on your website. When your crews work in the field, the app can adjust conditions automatically — your visitors always see the right information.

#### Board Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Place Name**: Sentinel Bike Park
**Nav Dashboard**: Dashboard
**Nav My Planning**: My planning
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Conditions**: Trail conditions
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav More Items**: 5 more items
**Activity Selector Label**: Mountain bike
**Page Title Activity**: Trail conditions
**Page Subtitle Activity**: Choose the activity for which you want to manage trail conditions
**Page Title Boards**: Mountain bike
**Page Subtitle Boards**: Manage condition boards displayed to your trail users
**Activity Mtb**: Mountain bike
**Activity Hike**: Hike
**Activity Gravel**: Gravel bike
**Activity Trail Run**: Trail running
**Activity Fat Bike**: Fat bike
**Activity Electric**: Electric bike
**Activity Atv**: ATV
**Activity Snowmobile**: Snowmobile
**Back To Activities**: Trail conditions
**Search Placeholder**: Search
**Create Board Button**: Create a board
**Name Column**: NAME
**Existing Board Name**: Summer 2026
**Dialog Create Title**: Create a board
**Dialog Create Field**: Board name
**Dialog Create Placeholder**: e.g. Spring 2026 conditions
**Dialog Create Add**: Add
**Dialog Create Cancel**: Cancel
**New Board Name**: Spring 2026 conditions
**Sort Button**: Sort
**Add Button**: Add
**Trail Column**: Trail
**Condition Column**: Condition
**Status Open**: Open
**Status Work**: Work in progress
**Status Closed**: Closed
**Work Details**: Drainage · km 2.4
**Dialog Select Title**: Select trails
**Dialog Select Subtitle**: Choose trails to add to the board
**Dialog Select Add**: Add selection
**Dialog Select Cancel**: Cancel
**Trail1**: L'Ancienne
**Trail2**: L'Inuk
**Trail3**: La Cairn
**Trail4**: La Coulée
**Trail5**: La passe du suisse
**Trail6**: Coupe du monde XC

#### Section1

**Tag**: 01 — One board per activity
**Title**: Multiple boards, an organization that fits your network
**Description**: A single condition board is never enough. Your visitors search for a biking, hiking or skiing trail — each with its own set of paths. Sentinel lets you create as many boards as activities, and group the trails of each one by type using folders: enduro, cross-country, flow trail for mountain biking; beginner, intermediate, expert for skiing; and whatever your network requires.
One board per activity — biking, hiking, skiing, fatbike
Folders and sub-groups to classify trails by type or level
Drag & drop to reorder, move a trail from one folder to another
**Back Link**: Trail conditions
**Board Name**: Summer 2026
**Activity Subtitle**: Mountain bike
**Search Placeholder**: Search a trail
**Sort Button**: Sort
**Add Button**: Add
**Trail Column**: Trail
**Condition Column**: Condition
**Status Open**: Open
**Status Construction**: Under construction
**Trail1**: 1837 (La bête)
**Trail2**: 1837 to WCDH
**Trail3**: La Germaine
**Trail4**: La Ruisseau-Rouge
**Trail5**: La Scalandrier
**Trail6**: 2.0 Montant
**Trail7**: La Basse Amazone
**Trail8**: La Virenrond
**Trail9**: La Tak-Tak
**Folder Name**: kxvrnd
**Folder Count**: 2 trails

#### Section2

**Tag**: 02 — Automatic synchronization
**Title**: Your field tasks update conditions — no double data entry
**Description**: A crew member arrives on a trail for drainage work. They mark their task as "In progress" on the mobile app. Sentinel immediately offers to update the trail to "Work in progress" on the public board. One tap, and your visitors see fresh information with the precise location of the work. No need to remember updating two places — the app handles it.
The app suggests the update when a task starts on a trail
Work location displayed publicly on the trail map
Automatic return to "Open" when the task is completed
**Header Title**: EDIT TASK
**Save Button**: SAVE
**Activity Badge**: MOUNTAIN BIKE
**Priority Label**: PRIORITY
**Priority Value**: LOW
**Date Label**: CREATED ON
**Date Value**: MAY 7 AT 12:28
**Status Label**: STATUS
**Status New**: New
**Status In Progress**: In progress
**Author Label**: AUTHOR
**Author Name**: Francis Lessard
**Name Label**: Name
**Name Value**: Fallen tree
**Assigned To Label**: Assigned to
**Assigned To Value**: User
**Dialog Title**: Mark trail as under work?
**Dialog Body**: "Black Beast" will be flagged "Work in progress" on the public board.
**Dialog Confirm**: Yes, update
**Dialog Cancel**: No
**Public Title**: Trail conditions
**Public Subtitle**: OUTDOOR CENTER
**Public Trail Name**: Black Beast
**Status Open**: Open
**Status Work**: Work in progress
**Work Details**: Drainage in progress · km 2.4

#### Section3

**Tag**: 03 — Embeddable public widget
**Title**: Display your conditions on your own website, in two lines of code
**Description**: Trail conditions are critical information for your visitors — and a major communication asset. Sentinel generates a widget you paste on your website: two HTML tags, and conditions display live, updated automatically, in your brand colors. No API to set up, no manual updates, no transcription errors.
2-line code to paste — works with WordPress, Wix, Squarespace, custom code
Customizable: colors, header, trail map, language
100% synced with your Sentinel board — only one place to maintain
**Browser Url**: outdoor-center.com
**Site Name**: Mont-Plein-Air Center
**Site Tagline**: Explore. Ride. Discover.
**Site Nav1**: Trails
**Site Nav2**: Pricing
**Site Nav3**: Map
**Site Nav4**: Contact
**Section Title**: Real-time trail status
**Section Subtitle**: Check conditions before you head out — information is updated automatically by our crews.
**Widget Title**: Trail conditions
**Widget Subtitle**: Updated automatically
**Folder Enduro**: Enduro
**Folder Xc**: Cross-country
**Status Open**: Open
**Status Work**: Work
**Status Closed**: Closed
**Trail1**: Black Beast
**Trail2**: Fast Descent
**Trail3**: Blue Loop
**Trail4**: The Long Way
**Last Update**: Updated 5 min ago
**Powered By**: Powered by Sentinel
**Code Title**: Install on your site
**Tag**: Live example
**Title**: See the widget in action
**Subtitle**: Here's a real trail-conditions board published as a widget, embedded in a website page. It updates on its own — exactly what your visitors will see.
**Iframe Title**: Sentinel trail conditions widget
**Highlights Title**: Everything you need to communicate the state of your network

#### Highlights

**Title**: Flexible boards, by activity
**Description**: Create as many boards as activities, organize each board by folders (type, level, sector). The structure fits your network, not an imposed model.
**Title**: Synced with your field
**Description**: When your crews start a task on a trail, the app offers to update the condition. The trail switches to work mode automatically, with the exact location of the worksite.
**Title**: Embeddable public widget
**Description**: Two lines of code and conditions show up on your site. Live updates, customizable, bilingual. Only one place to manage.
**Faq Title**: Frequently asked questions
**Cta Title**: Give your visitors the information they need
**Cta Subtitle**: Clear condition boards, synced with your field and published live on your website. One more piece of always-fresh info, zero extra effort for your team.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: What is a trail condition?
**Body**: A trail condition is the publishable state of a trail at a given moment: open, closed, passable with care. Trails are grouped into boards by activity, and a board publishes as-is on your website. When a crew works in the field, the app can adjust the condition automatically.
**Replaces**: The web page updated by hand, the morning post on social media, and the phone calls asking whether the trail is open.
**Where**: Kept up to date on the web and on the phone, read by the public on your own site.

### Checklists

**Title**: Trail Maintenance Checklists
**Menu Description**: The same list, on every trail
**Description**: One list of checks, applied to your whole network — and ticked in the field, even without coverage.
**Meta Description**: Run the same series of checks across every trail: season opening, periodic inspection, closing. Reusable templates, whole-network progress on a single screen, offline ticking on mobile.
**Tag**: CHECKLISTS
**Hero Title**: The same checks, on every one of your trails
**Hero Description**: Season opening, periodic inspection, closing: one list, applied to the whole network at once. You see what is done, what is left and on which trail — on a single screen, instead of a file nobody opens out in the field.

#### Matrix Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Place Name**: Mont-Brûlé
**Nav Dashboard**: Dashboard
**Nav Planning**: My planning
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Checklists**: Checklists
**Nav Conversations**: Conversations
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Activity Label**: Mountain bike
**Lang Code**: EN
**Back Link**: Checklists
**Campaign Name**: Summer opening 2026
**Started On**: Started on May 4, 2026
**Repeat Label**: Yearly · next on May 4, 2027
**Search Placeholder**: Search a trail
**Stat Progress**: Progress
**Stat Items**: Items
**Stat Trails**: Trails completed
**Stat Duration**: Duration
**Duration Value**: 18 d
**Responsible Label**: Owner
**Responsible Name**: Marie Tremblay
**Assignee Label**: Assigned
**Assignee Name**: Jonathan Lavoie
**Trail Column**: Trail
**Discussion Column**: Discussion
**Discuss Empty**: Discuss
**Item1**: Visual inspection
**Item2**: Fallen trees
**Item3**: Brush clearing
**Item4**: Drainage and culverts
**Item5**: Signage
**Item6**: Structures and bridges
**Item7**: Litter picked up
**Item8**: Closing photo
**Trail1**: La Germaine
**Trail2**: Ruisseau-Rouge
**Trail3**: 1837 (La bête)
**Trail4**: La Basse Amazone
**Trail5**: Le Belvédère
**Trail6**: La Scalandrier
**Trail7**: 2.0 Montant
**Trail8**: La Virenrond

#### Section1

**Tag**: 01 — Write it once
**Title**: Write the list once. It applies to every trail you pick.
**Description**: A reusable template: your items, your icons, your order. On launch, Sentinel creates one checklist per selected trail, with the items copied into it. Next season you launch the same template — nothing to rewrite. And if you have no template yet, you type the items straight into the wizard.
Several named templates side by side: opening, brush clearing, grooming, closing
An owner and an assignee per checklist — everyone knows who leads and who does
The template stays optional: items can be typed at creation time
**Editor Back**: Templates
**Editor Title**: Template
**Editor Name Label**: Name
**Editor Name Value**: Season opening
**Editor Items Label**: Items (6)
**Editor Add Placeholder**: Add an item…
**Editor Add Button**: Add
**Item1**: Visual inspection
**Item2**: Fallen trees
**Item3**: Brush clearing
**Item4**: Drainage and culverts
**Item5**: Signage
**Item6**: Closing photo
**Dialog Title**: New checklist
**Step1**: Name
**Step2**: Content
**Step3**: Repeat
**Step4**: Trails
**Trails Hint**: Select the trails to cover
**Trail1**: La Germaine
**Trail2**: Ruisseau-Rouge
**Trail3**: 1837 (La bête)
**Trail4**: La Basse Amazone
**Trail5**: Le Belvédère
**Trail6**: La Scalandrier
**Dialog Back**: Back
**Dialog Create**: Create checklist
**Selected Count**: %n trails selected

#### Section2

**Tag**: 02 — Tick it in the field
**Title**: Ticked deep in the woods, synced on the way back
**Description**: On iOS and Android, whoever is on site opens the checklist, picks their trail and ticks. Without cell coverage the tick shows up immediately and goes into the sync queue: it is replayed as soon as the network is back. Nobody has to jot anything on paper to re-enter it that evening.
Checklists, trails and items readable offline
A tick made without coverage stays visible right away, then syncs on its own
Progress updates live for whoever stayed at the office
**List Title**: CHECKLISTS
**Section In Progress**: In progress
**Section Completed**: Completed
**Campaign1Name**: Summer opening 2026
**Campaign1Meta**: 8 trails · Started May 4
**Campaign2Name**: Culvert round
**Campaign2Meta**: 12 trails · Started May 19
**Campaign3Name**: Fall closing 2025
**Campaign3Meta**: 8 trails · Completed Nov. 3
**Detail Title**: SUMMER OPENING 2026
**Stat Trails**: Trails
**Stat Items**: Items
**Stat Progress**: Progress
**Repeat Label**: Yearly · May 4, 2027
**Search Placeholder**: Search a trail
**Trail1**: La Germaine
**Trail2**: Ruisseau-Rouge
**Trail3**: 1837 (La bête)
**Trail4**: La Basse Amazone
**Trail Detail Title**: LA GERMAINE
**Item1**: Visual inspection
**Item2**: Fallen trees
**Item3**: Brush clearing
**Item4**: Drainage and culverts
**Item5**: Signage
**Item6**: Structures and bridges
**Item7**: Litter picked up
**Item8**: Closing photo

#### Section3

**Tag**: 03 — Repeat and follow up
**Title**: What comes back every week should not be rebuilt by hand
**Description**: Give the checklist a frequency — weekly, monthly or yearly — and the next one is created on the scheduled date, same items, same trails. And on each trail, a dedicated discussion: the photo of the blocked culvert stays attached to the culvert, instead of vanishing into a group thread.
Weekly, monthly or yearly repeat, ending on a date or after a number of occurrences
One discussion per trail, with photos and an unread message counter
Start date, duration, percentage: a dated record of what was actually done
**Dialog Title**: Repeat
**Frequency Label**: Repeat
**Frequency Value**: Weekly
**Every Label**: Every
**Every Value**: 1
**Every Unit**: week(s)
**Days Label**: Days of the week
**Day1**: S
**Day2**: M
**Day3**: T
**Day4**: W
**Day5**: T
**Day6**: F
**Day7**: S
**End Label**: Ends
**End Value**: On October 31, 2026
**Complete Previous Label**: Complete the previous one on launch
**Cancel**: Cancel
**Save**: Save
**Panel Title**: La Germaine
**Panel Subtitle**: Trail discussion
**Message1Author**: Jonathan Lavoie
**Message1Time**: 8:14
**Message1Text**: The culvert at km 2 is blocked, I can't tick drainage today.
**Message2Author**: Marie Tremblay
**Message2Time**: 9:02
**Message2Text**: Photo taken this morning — it needs a shovel and two people.
**Message3Author**: Éric Bourgeois
**Message3Time**: 11:47
**Message3Text**: I'm going tomorrow with the ATV and the trailer, I'll clear it.
**Input Placeholder**: Write a message…
**Highlights Title**: Why crews use it

#### Highlights

**Title**: One template, the whole network
**Description**: Write the list once and apply it to as many trails as you want. Next season, launch the same template without rewriting a thing.
**Title**: The network's state on one screen
**Description**: Trails as rows, checks as columns. What is left to do shows up in three seconds, without opening ten records one after the other.
**Title**: A dated record
**Description**: Who did what, when, on which trail. Enough to answer a board, a municipality or an insurer without piecing the history back together from memory.
**Faq Title**: Frequently asked questions
**Cta Title**: Your next season opening, without the shared file
**Cta Subtitle**: Build a checklist, launch it across forty trails and tick it in the field — with your own trails, during your 30-day trial.
**Cta Primary**: Start trial
**Cta Secondary**: See the other features

#### Definition

**Title**: What is a maintenance checklist?
**Body**: A checklist is a list of verifications applied at once to several trails: season opening, periodic inspection, closing. Every trail gets its own copy of the items, and a single screen shows what is done, what is left, and on which trail.
**Replaces**: The season-opening spreadsheet nobody opens in the field and nobody fills in on the way back.
**Where**: Templates and tracking on the web, items checked off on the phone, even with no signal.

### Projects

**Title**: Projects
**Menu Description**: Plan, track, deliver
**Description**: Group your tasks into projects, plan your season, track progress without spreadsheets.
**Meta Description**: Trail maintenance project management. Group tasks by worksite, season or grant. Real-time progress tracking, instant reports.
**Tag**: PLANNING
**Hero Title**: From isolated tasks to projects that move forward
**Hero Description**: Group your tasks by worksite, by season, by grant. Track progress in real time, see what's done, what's left, what's blocked.

#### Kanban Browser Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Nav Dashboard**: Dashboard
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Planning**: Planning
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav Groups**: Groups
**Nav Trails**: Trails
**Nav Activities**: Activities
**Nav Difficulties**: Trail difficulties
**Nav Task Types**: Task types
**Nav Structure Types**: Structure types
**Activity Label**: Mountain biking
**Header Title**: Projects
**Header Subtitle**: Manage and track your projects
**Create Button**: Create a project
**Filter Assignee**: Assigned to
**Col New**: NEW
**Col Ready**: READY
**Col In Progress**: IN PROGRESS
**Col Done**: DONE
**Col Waiting**: WAITING
**Selected Project Name**: Rehabilitation
**Tasks Completed**: Tasks completed
**Hours Worked**: Hours worked
**List Group New**: NEW
**List Group Ready**: READY
**List Group In Progress**: IN PROGRESS
**Tasks Count**: tasks
**Stats Kpi Progress**: Progress
**Stats Kpi Estimated**: Estimated time
**Stats Kpi Worked**: Time worked
**Stats Kpi Unassigned**: Unassigned tasks
**Stats By Status Title**: Tasks by status
**Stats By Status Subtitle**: Distribution of tasks by current status
**Stats By Priority Title**: Tasks by priority
**Stats By Priority Subtitle**: Distribution of tasks by priority level
**Priority Critical**: Critical
**Priority High**: High
**Priority Medium**: Medium
**Priority Low**: Low

#### Section1

**Tag**: 01 — CONTEXT AT HAND
**Title**: Your team knows why they're there
**Description**: A volunteer opens Sentinel and sees the tasks for the "North sector rehabilitation" project. They understand the context, see the related tasks, know what's priority. No need to explain every time — the information is in the app.
All project tasks, visible at a glance
Worksite context, right in the app
Clear priorities, without daily briefings

#### Section2

**Tag**: 02 — STEER YOUR WORKSITES
**Title**: Every project, a progress dashboard
**Description**: Create a project, add the relevant tasks, set a deadline, assign a team. The dashboard shows you how many tasks are done, in progress, blocked. You spot delays before they become problems.
Create a project in seconds, add the relevant tasks
Set deadlines and assign the responsible teams
Spot delays and blockers before they become problems
**Header Title**: Projects
**Header Subtitle**: 3 active projects
**Create Button**: New project
**Project1Name**: Rehabilitation — North sector
**Project1Deadline**: Jun 30, 2026
**Project2Name**: Summer 2026
**Project2Deadline**: Sep 15, 2026
**Project3Name**: MAPAQ grant
**Project3Deadline**: Completed
**Col Name**: Project
**Col Progress**: Progress
**Col Tasks**: Tasks
**Col Deadline**: Deadline
**Kpi Active**: Active
**Kpi Open Tasks**: Open tasks
**Kpi Completed**: Completed

#### Section3

**Tag**: 03 — THE PROJECT UPDATES ITSELF
**Title**: Every completed task moves the project forward
**Description**: When your team closes a task in the field, the project progress updates automatically at the office. No spreadsheet to maintain, no "can you send me the weekly updates." The project lives with its team.
Progress recalculated automatically with every completed task
Zero spreadsheets, zero weekly update emails
The project reflects field reality in real time
**Mobile Label**: In the field
**Desktop Label**: At the office
**Task Label**: Pruning completed
**Project Name**: North sector
**Progress Label**: Progress

#### Section4

**Tag**: 04 — FROM FILTER TO PROJECT
**Title**: Turn a list of tasks into a structured project
**Description**: Your volunteers reported 40 fallen trees this season? From the tasks view, filter by type, area or priority, then convert the result into a project. The tasks keep their context — photos, location, priority — and are now grouped under a single assignable project.
Any filtered list can become a project — no re-entry needed
Each task keeps its context: photos, history, priority
Perfect for cross-cutting work: clearing, drainage, seasonal marking
**Tasks Title**: Tasks
**Filter Label**: Type
**Filter Value**: Fallen tree
**Selected Label**: selected
**Create Button**: Create project
**Task1**: Fallen tree km 2.4
**Task2**: Fallen tree Blue Loop
**Task3**: Fallen tree North Sector
**Task4**: Fallen tree Panorama Descent
**Task5**: Fallen tree East Link
**Trail1**: Panorama Trail
**Trail2**: Blue Loop
**Trail3**: North Sector
**Trail4**: Panorama Descent
**Trail5**: East Link
**Project Name**: Spring clearing 2026
**Project Tasks Label**: Tasks
**Project Deadline Label**: Deadline
**Project Deadline**: May 31, 2026
**Project Progress Label**: Progress
**Highlights Title**: What changes with projects

#### Highlights

**Title**: Flexible grouping
**Description**: By worksite, by season, by grant, by sector. You define what a "project" means for you.
**Title**: Instant report
**Description**: At any time, pull a progress report: tasks done, photos, time invested. Perfect for your status reports and funding applications.
**Title**: History preserved
**Description**: A closed project remains accessible. Useful to demonstrate your accomplishments to partners or to draw inspiration for the next similar project.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: How many projects can we have in parallel?
**Answer**: No limit. You can have one project per worksite, one per season, one per grant — all at the same time.
**Question**: Can a task belong to multiple projects?
**Answer**: No. Each task belongs to one project at a time, to keep progress clear. You can move it from one project to another if needed.
**Question**: Can we manage a budget per project?
**Answer**: For now, Sentinel focuses on progress (tasks done versus total tasks) and time invested. Dollar-based budget tracking is not yet integrated — we're working on the next version.
**Cta Title**: Switch from reactive to planned
**Cta Subtitle**: A well-maintained network is a managed network — by projects, by seasons, by teams.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: What is a project in Sentinel?
**Body**: A project groups tasks that belong together: a work site, a season, a grant. It carries its lead, its dates and its progress — computed from the real state of the tasks it contains, not from a percentage typed by hand.
**Replaces**: The work-site tracking spreadsheet, kept alongside the real work and out of date by the second week.
**Where**: Created and tracked on the web, consulted on the phone by the crews.

### Team

**Title**: Team & permissions
**Menu Description**: The right person, the right access
**Description**: Volunteers, seasonal staff, partners, contractors — everyone gets access to what concerns them, with the right permission level.
**Meta Description**: Team management and permissions for trail networks. Invite members, assign Admin, Editor, Viewer or custom roles. Activity-based access control.
**Tag**: TEAM
**Hero Title**: A team that contributes, without breaking things
**Hero Description**: Volunteers, seasonal staff, partners, contractors — everyone gets access to what concerns them, with the right permission level. You delegate with confidence.

#### Members Browser Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Place Name**: Sentinel Bike Park
**Nav Dashboard**: Dashboard
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Planning**: Planning
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav Groups**: Groups
**Nav Trails**: Trails
**Nav Activities**: Activities
**Nav Difficulties**: Trail difficulties
**Nav Task Types**: Task types
**Nav Structure Types**: Structure types
**Activity Label**: Hiking
**Header Title**: Members
**Header Subtitle**: Enter the email of the member you want to invite to your account.
**Invite Button**: Invite
**Search Placeholder**: Search
**Filter Activity**: All activities
**Col Member**: Name
**Col Role**: Role
**Col Activity**: Activities
**Col Last Seen**: Last activity
**Status Pending**: Invitation pending
**Role Admin**: Admin
**Role Editor**: Editor
**Role Viewer**: Viewer
**Invite Dialog Title**: Invite a member
**Invite Dialog Subtitle**: Enter the email of the member you want to invite to your account.
**Invite Dialog Email Label**: Email
**Invite Dialog Activity Restriction**: Activity restriction
**Invite Dialog Activity Restriction Description**: This member has access to all activities. Enable this option to restrict their access to certain activities only.
**Invite Dialog Role Label**: Role
**Invite Dialog Role Admin Description**: Can manage account settings and subscription settings, and invite other members.
**Invite Dialog Role Viewer Description**: Can only view tasks and projects.
**Invite Dialog Role Editor Description**: Can create, edit and assign tasks and projects.
**Invite Dialog Cancel**: Cancel
**Invite Dialog Send**: Send invitation
**Invite Typed Email**: maxime.dubois@sentinel-bike.ca

#### Section1

**Tag**: 01 — EACH TO THEIR ROLE
**Title**: Your volunteers contribute, your experts decide
**Description**: A volunteer can report a problem and take photos. An editor can assign tasks and close cases. An admin can edit the network and manage members. Everyone sees what they can do, and nothing more. No confusion, no accidental errors.
Three default roles (Admin, Editor, Viewer) plus custom roles
Granular permissions per data type (tasks, trails, structures, members)
Activity restrictions to limit members to specific sports

#### Section2

**Tag**: 02 — MANAGE ACCESS
**Title**: Invite, assign, adjust — in a few clicks
**Description**: From the dashboard, invite a new member by email, assign them a role, restrict them to specific activities. Revoke access at the end of a contract or season. You stay in control, without having to ask an IT admin.
Email invitation, member operational in under 60 seconds
Role changes and access revocation are instant — no ticket needed
Restrict access by activity (bike, hiking, cross-country skiing, ATV)
**Header Title**: Members
**Header Subtitle**: 4 active members · 1 pending invitation
**Invite Button**: Invite
**Col Member**: Member
**Col Role**: Role
**Col Activity**: Activities
**Member1Name**: Marie Tremblay
**Member1Email**: marie@sentinel-bike.ca
**Member2Name**: Julien Côté
**Member2Email**: julien@sentinel-bike.ca
**Member3Name**: Sophie Bergeron
**Member3Email**: sophie@sentinel-bike.ca
**Member4Name**: Alexandre Roy
**Member4Email**: alex.roy@gmail.com
**Role Admin**: Admin
**Role Editor**: Editor
**Role Viewer**: Viewer
**Role Volunteer**: Volunteer
**Activity All**: All
**Activity Mtb**: Mountain bike
**Activity Hike**: Hike, snowshoeing
**Kpi Active**: Active
**Kpi Pending**: Pending

#### Section3

**Tag**: 03 — ONE TEAM, TWO FIELDS
**Title**: Office and trail, same team
**Description**: The admin at the office promotes Alexandre from Volunteer to Editor. A few seconds later, out on the trail, Alexandre gets his new tools: he can now close tasks and document his interventions. No logout, no manual refresh — permissions follow the person.
Role changes propagated in real-time across all devices
Permissions follow the person, even in offline mode
A member can belong to multiple networks with a single account
**Highlights Title**: What changes with roles

#### Highlights

**Title**: Granular roles
**Description**: Admin, Editor, Viewer or 100% custom roles. Define who can read or edit each type of data.
**Title**: Activity restriction
**Description**: Limit a member to mountain bike, cross-country ski, hiking or ATV trails only. Perfect for contractors and specialized partners.
**Title**: Instant changes
**Description**: Revoke an access, change a role, transfer responsibilities — everything propagates in real-time on the trail and at the office.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: How many members can we invite?
**Answer**: As many as you want. There's no limit on the number of members in Sentinel — invite your entire team, your volunteers, your partners and your contractors with no extra per-user fees.
**Question**: Can a member belong to multiple organizations?
**Answer**: Yes. A technician can work for two different clubs with the same Sentinel account. They switch between networks directly from the app, without having to log in again.
**Question**: How do we manage seasonal volunteers?
**Answer**: Invite them with a limited role for the season. At the end, you simply disable their access. Their contribution stays in the network history — photos, reports, time invested.
**Question**: What about external partners (municipality, contractor)?
**Answer**: Give them a Viewer role on the activities that concern them. They see what they need to see, nothing more. Perfect for transparency without risk of error.
**Cta Title**: A team that moves forward, a manager who breathes
**Cta Subtitle**: Delegating means trusting the right tools. Sentinel gives you the right tools.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: How do members, groups and roles work?
**Body**: A member is a person attached to your place. Their role decides what they can see and do: browse, create a task, inspect a structure, administer. Groups gather several members so work can be assigned to a crew at once, without naming one person in particular.
**Replaces**: The shared account whose password everyone knows, and the volunteer list kept separately in another file.
**Where**: Invitations, roles and groups managed on the web; the member works on the phone.

### Discussions

**Title**: Discussions
**Menu Description**: Centralize conversations where the work happens
**Description**: No more messages lost in Messenger, Slack or Discord. Every discussion is attached to a task, a structure or a project — with photos, audio and mentions.
**Meta Description**: Sentinel discussions module: chat attached to every task, structure or project. Share photos, voice messages, mention your team. Smart notifications so nothing is missed.
**Tag**: DISCUSSIONS
**Hero Title**: Every conversation, where the work happens
**Hero Description**: Your discussions are no longer scattered across Messenger, Slack or Discord. Every exchange is tied to the task, structure or project it belongs to — and you find everything back, even six months later.

#### Browser Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Place Name**: Sentinel Bike Park
**Nav Dashboard**: Dashboard
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Planning**: Planning
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav Groups**: Groups
**Nav Trails**: Trails
**Nav Activities**: Activities
**Nav Difficulties**: Trail difficulties
**Nav Task Types**: Task types
**Nav Structure Types**: Structure types
**Activity Label**: Mountain bike
**List Title**: Conversations
**Filters Label**: Filters
**Conv1Title**: Fallen tree
**Conv1Preview**: 44: werewr
**Conv1Time**: 9 days ago
**Conv2Title**: Planning 2026
**Conv2Preview**: demo: asdasas
**Conv2Time**: 15 days ago
**Conv3Title**: Water
**Conv3Preview**: demo: zdfdssf
**Conv3Time**: 16 days ago
**Conv4Title**: Fallen tree 32223
**Conv4Preview**: demo: sdfsdds
**Conv4Time**: 19 days ago
**Conv5Title**: Broken plank
**Conv5Preview**: Francis Lessard: j
**Conv5Time**: 20 days ago
**Conv6Title**: Fallen tree
**Conv6Preview**: Francis Lessard: asdsad
**Conv6Time**: 21 days ago
**Conv7Title**: Handicap
**Conv7Preview**: Francis Lessard: sdasdas
**Conv7Time**: 21 days ago
**Conv8Title**: Ada
**Conv8Preview**: demo 1: ok
**Conv8Time**: 22 days ago
**Conv9Title**: Fallen tree
**Conv9Preview**: Francis Lessard: zx
**Conv9Time**: 22 days ago
**Conv10Title**: Handicap
**Conv10Preview**: demo: Hjghjghj
**Conv10Time**: 23 days ago
**Conv11Title**: Erosion
**Conv11Preview**: Francis Lessard: xs
**Conv11Time**: 23 days ago
**Conv12Title**: Erosion asdpf asdfy8 á9s8df8aysd=f0…
**Conv12Preview**: Francis Lessard: asdfasfsd
**Conv12Time**: 23 days ago
**Conv13Title**: Erosion
**Conv13Preview**: demo: Hbhh
**Conv13Time**: a month ago
**Chat Title**: Broken plank
**View Task Button**: View task
**Author Self Initial**: Y
**Author Other Initial**: F
**Msg0Body**: Hey! There's a broken plank on the North sector bridge.
**Msg1Body**: On my way in 15 min
**Msg2Body**: Thanks! A photo would be perfect.
**Msg3Caption**: Here you go!
**Msg4Body**: Perfect, thanks 👍 closing the task
**Msg5Body**: can you come validate on site?
**Input Placeholder**: Write a message…
**Mention Menu Title**: Members
**Mention P1Name**: Sophie Bergeron
**Mention P1Handle**: Sophie B.
**Mention P1Role**: North sector lead
**Mention P2Name**: Julien Côté
**Mention P2Handle**: Julien C.
**Mention P2Role**: Patroller
**Mention P3Name**: Marie Tremblay
**Mention P3Handle**: Marie T.
**Mention P3Role**: Volunteer
**Phone Date**: Monday, April 21
**Phone Notif App**: SENTINEL
**Phone Notif Now**: now
**Phone Notif Title**: Francis L. mentioned you
**Phone Notif Context**: Broken plank · Sector 4

#### Section1

**Tag**: 01 — ATTACHED TO CONTEXT
**Title**: One discussion per task, structure or project
**Description**: No more chat groups where everything blends together. Every discussion is linked to a specific object in Sentinel — a fallen tree task, a bridge inspection, a rehab project. When someone joins your team six months later, the whole history is there, in the right place.
Discussion created automatically for every task, structure or project
One click from the record to join the conversation
Full history kept even after the task is closed
**Card Title**: Fallen tree
**Card Subtitle**: High priority · Panorama Trail
**Discussion Badge**: 12 messages
**Discussion Label**: Discussion
**Unread Label**: 2 new
**Inspection Title**: Inspection — North Bridge
**Inspection Subtitle**: Structure · 6 messages
**Project Title**: East Sector Rehab
**Project Subtitle**: Project · 18 messages

#### Section2

**Tag**: 02 — TEXT, PHOTOS, AUDIO
**Title**: All the context, in a single thread
**Description**: A voice message to describe a complex issue. Three photos of a damaged bridge. A mention to alert the sector lead. Everything stays in one place, attached to the task. No more screenshots, no more copy-paste between apps.
Unlimited photos, compressed automatically
Voice messages for frozen hands or long descriptions
Emoji reactions and replies to keep threads readable
**Photos Label**: Photos added
**Photo1Label**: Bridge — upstream side
**Photo2Label**: Damaged fixing
**Photo3Label**: Blocked drainage
**Audio Label**: Voice message
**Audio Duration**: 0:47
**Audio Speaker**: Julien C.
**Mention Label**: Mention
**Mention Body**: @Sophie B. can you come validate on site?

#### Section3

**Tag**: 03 — NOTIFIED, NEVER OVERWHELMED
**Title**: The right messages, to the right people
**Description**: Each member gets a notification when they're mentioned, when a message arrives in a discussion they follow, or when a task that concerns them changes. The rest is noise — and we filter the noise for you. You never miss what matters.
@name mentions to draw a specific person's attention
Subscribe per discussion to follow what matters to you
Unread indicators on desktop and on the field
**App Label**: SENTINEL
**Time Now**: now
**Time1min**: 1 min ago
**Time3min**: 3 min ago
**Lock Date**: Monday, April 19
**Notif1Title**: Marie T. mentioned you
**Notif1Body**: @Julien can you come validate the inspection?
**Notif1Context**: North Bridge · Inspection
**Notif2Title**: New message
**Notif2Body**: Francis sent 3 photos
**Notif2Context**: Broken plank · Sector 4
**Notif3Title**: Active discussion
**Notif3Body**: Sophie and 2 others are talking
**Notif3Context**: East Sector Rehab
**Highlights Title**: What changes with discussions

#### Highlights

**Title**: One source of truth
**Description**: No more scattered messages across Messenger, Slack or Discord. Everything is tied to the task, structure or project it belongs to.
**Title**: Photos, audio, mentions
**Description**: The right format for the right info. A picture is worth a thousand words, a voice message saves you from typing with gloves on.
**Title**: Targeted notifications
**Description**: Each member gets what concerns them, nothing more. Mentions are prioritized, the rest stays browsable.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: Do messages disappear when a task is closed?
**Answer**: No. The discussion stays attached to the task, even closed. You can still browse it from history — photos, audio and text included. Perfect for audits or lessons learned.
**Question**: Can volunteers and external partners take part in discussions?
**Answer**: Yes, if their role allows it. You stay in control: a volunteer can take part in the discussions of tasks assigned to them, but not in projects they're not attached to.
**Question**: Why use this instead of a Slack or Messenger group?
**Answer**: Because an external chat isn't tied to anything. Six months later, finding a specific message about a fallen tree takes an hour. In Sentinel, you open the task and the whole conversation is there, with photos and context.
**Cta Title**: Stop searching, start finding
**Cta Subtitle**: Your field conversations deserve better than a lost Messenger thread. Centralize everything in the right place.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: What is a discussion in Sentinel?
**Body**: A discussion is a message thread attached to what it is about: a task, a structure, a project. The exchange stays with the object, along with its photos and its history, and is still there six months later without any digging.
**Replaces**: Messaging threads where the problem is buried under the day's conversations, then forgotten.
**Where**: Web and mobile, with a notification for what concerns you.

### Field Work

**Title**: Field work
**Menu Description**: Built for the field, not the office
**Description**: Built to work where you work: in the forest, off-grid, hands full.
**Meta Description**: Field mobile app (iOS and Android) for trail maintenance crews. Offline creation of tasks, structures and inspection reports. Works without signal, syncs on return.
**Tag**: FIELD
**Hero Title**: It works where you work
**Hero Description**: No signal? The app runs. Cold hands? The interface stays usable. Thick gloves? Tap targets are large. Sentinel is built for the field, not for a meeting room.

#### Hero Phone

**Park Name**: Mont-Valin Park
**Category Fallen Tree**: Tree
**Category Erosion**: Erosion
**Category Water**: Water
**Category Mud**: Mud
**Category Broken Plank**: Plank
**Projects Title**: Projects
**Tasks Title**: Tasks
**New Badge**: New
**Task Count Suffix**: Tasks
**Project1Name**: Summer trail refresh 2026
**Project1Count**: 4
**Project1Progress**: 62
**Project2Name**: Boardwalk inspection
**Project2Count**: 2
**Project2Progress**: 18
**Task Type**: Water damage
**Task Date**: April 18 at 7:12 AM

#### Hero Phone Detail

**Header Title**: View task
**Edit Button**: Edit
**Completed Badge**: Done
**Activity Chip**: Mountain bike
**Priority Label**: Priority
**Priority Value**: Critical
**Status Label**: Status
**Status Value**: New
**Created At Label**: Created at
**Created At Value**: Apr 18 at 7:12 AM
**Add Time Label**: Add time
**Conversation Label**: Conversation
**Author Label**: Author
**Author Name**: Marc Tremblay
**Author Initials**: MT
**Task Title**: Water damage
**Medias Title**: Media

#### Hero Sync

**Card Title**: Water damage
**Card Meta**: Mont-Valin · Apr 18

#### Section1

**Tag**: 01 — OFFLINE, NO COMPROMISE
**Title**: Cellular coverage is a luxury — not a requirement
**Description**: You report a task in a no-signal zone. The app saves everything locally: photos, GPS, notes. The moment you're back in coverage, everything syncs automatically. You don't lose anything, you don't redo anything.
Create tasks, structures and inspection reports offline — with photos and media
Local storage on the phone, even without a connection for days
Automatic sync the moment the signal returns, no manual action

#### Section2

**Tag**: 02 — TIME INVESTED, VISIBLE
**Title**: Every hour in the field, documented
**Description**: Your team logs time spent on each task directly in the app. At the office, you see the time invested by project, by person, by task type. Perfect for reports to funders and for planning future seasons.
Time linked to the task, the project, the person — automatically
Time reports ready for funders and seasonal planning
**Header Title**: Time by task
**Header Subtitle**: 3 people active · this week
**Period Label**: This week
**Col Task**: Task
**Col Person**: Person
**Col Project**: Project
**Col Duration**: Time
**Task1Name**: Repair bridge km 3.2
**Task1Person**: Maxime D.
**Task1Project**: North sector
**Task2Name**: Clean drainage
**Task2Person**: Julie T.
**Task2Project**: Blue Trail
**Task3Name**: Rebuild boardwalk
**Task3Person**: Alexandre R.
**Task3Project**: South sector
**Task4Name**: Seasonal marking
**Task4Person**: Sophie B.
**Task4Project**: Panorama Loop
**Active Label**: In progress
**Total Label**: Team total

#### Section3

**Tag**: 03 — FROM FIELD TO REPORT
**Title**: Data flows up, work keeps moving
**Description**: The technician works, documents, closes tasks. Meanwhile, the data flows back to the office as soon as network is available. The manager sees the day's progress without interrupting anyone. You don't pay for hours of data entry after the fact — it's already in the system.
No double entry — what's done in the field arrives at the office as is
Progress visible in real time, without a call or status email
Background sync, without interrupting the work in progress
**Mobile Label**: In the field
**Desktop Label**: At the office
**Task Label**: Task completed
**Project Name**: North sector
**Progress Label**: Progress

#### Section4

**Tag**: 04 — FROM HOURS TO REPORTS, ONE CLICK AWAY
**Title**: Every hour linked, every total ready
**Description**: Each time entry is automatically linked to a task, a task type, a trail, a volunteer. How many hours clearing fallen trees this year? How much time on the Panorama Trail? How much on that trail specifically for marking? Sentinel rolls it all up for you — no spreadsheet to compile, no volunteer to chase.
Reports by trail, by task type, by volunteer — in just a few clicks
Automatic seasonal rollups: hours by category, by crew, by zone
Activity proof ready for grants, annual reports, and volunteer hour valuation
**Period Label**: 2026 Season
**By Type Title**: Hours by task type
**Type1Label**: Fallen tree
**Type1Value**: 147 h
**Type2Label**: Drainage
**Type2Value**: 84 h
**Type3Label**: Marking
**Type3Value**: 56 h
**Type4Label**: Inspection
**Type4Value**: 32 h
**By Trail Title**: Hours by trail
**Trail1Label**: Panorama Trail
**Trail1Value**: 210 h
**Trail2Label**: Blue Loop
**Trail2Value**: 85 h
**Trail3Label**: North Sector
**Trail3Value**: 64 h
**Highlights Title**: Built for people who work outside

#### Highlights

**Title**: Offline creation
**Description**: Creating tasks, structures and inspection reports — with photos and media — works without a signal. Sync happens the moment the connection returns.
**Title**: Interface built for the field
**Description**: Large buttons, generous tap targets, sun-readable screens. Designed to be used with gloves, in the rain, on the move.
**Title**: Simple time tracking
**Description**: One button to start, one button to stop. Time is linked to the task, not to a timesheet to fill out Friday night.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: How long can the app stay offline?
**Answer**: Days, even weeks. As long as you don't reinstall the app, the data stays on your phone and syncs on the next connection.
**Question**: Does the app drain the battery?
**Answer**: No. The app is optimized to use GPS only when needed — when creating a task or viewing a specific point, never continuously in the background. Battery consumption stays very low, even during a full day in the field.
**Question**: Does it work on Android and iPhone?
**Answer**: Yes, both. Same features, same performance. Download from the App Store and the Google Play Store.

#### Store Section

**Tag**: DOWNLOAD
**Title**: Available on iOS and Android
**Description**: The same app, the same features on both platforms. Install it on your team's phones today — no subscription needed to try it. Works on modern smartphones, even in deep-forest conditions.
**Compatibility**: iOS 14+ · Android 10+ · Free to download
**Alt Screenshot1**: Sentinel mobile app for trail maintenance — field screen on iOS and Android
**Alt Screenshot2**: Sentinel trail maintenance mobile app — offline field work screen on iOS and Android
**Cta Title**: A field tool, not a repurposed office tool
**Cta Subtitle**: Sentinel is built by people who've already spent a full day in the forest with a phone. Try it.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: What is field work in Sentinel?
**Body**: Field work is what the app does when nobody is at the office: report, annotate a map or a photo, inspect and check off from the phone, with or without a signal. Anything entered offline is kept on the device and syncs on its own once the signal is back.
**Replaces**: The notepad in your pocket, the photos retyped in the evening, and the voice notes nobody plays back.
**Where**: On the phone in the field; visible on the web at the office as soon as it syncs.

### Insights

**Title**: Reports & impact
**Menu Description**: Quantify your impact, justify your budget
**Description**: Your work, in numbers. Your evidence, exportable. Your impact, demonstrable.
**Meta Description**: Dashboards, reports and exports for trail networks. Turn every closed task into evidence for your board, your grants, and your partners.
**Tag**: IMPACT
**Hero Title**: Quantify your impact, justify your budget
**Hero Description**: Dashboards, exportable reports, complete history. Sentinel turns your team's work into clear data, ready for your board, your grants, your partners.

#### Overview Mockup

**Sidebar Place**: PLACE
**Sidebar General**: GENERAL
**Sidebar Admin**: ADMINISTRATION
**Place Name**: Sentinel Bike Park
**Nav Dashboard**: Dashboard
**Nav Tasks**: Tasks
**Nav Structures**: Structures
**Nav Projects**: Projects
**Nav Conversations**: Conversations
**Nav Planning**: Planning
**Nav Billing**: Billing
**Nav Members**: Members
**Nav Roles**: Roles
**Nav Groups**: Groups
**Nav Trails**: Trails
**Nav Activities**: Activities
**Nav Difficulties**: Trail difficulties
**Nav Task Types**: Task types
**Nav Structure Types**: Structure types
**Activity Label**: Mountain bike
**Greeting**: Hello Francis!
**Subtitle**: Here's an overview of your operations
**Date Range**: 12 Apr 2026 – 18 Apr 2026
**Kpi Critical**: Critical tasks
**Kpi Open**: Open tasks
**Kpi Completed**: Completed tasks
**Kpi Structures At Risk**: Structures at risk
**Kpi Overdue**: Overdue reports
**Donut Status Title**: Tasks by Status
**Donut Status Caption**: Task distribution by current status
**Donut Priority Title**: Tasks by Priority
**Donut Priority Caption**: Task distribution by priority level
**Donut Risk Title**: Structures by Risk Level
**Donut Risk Caption**: Structure distribution by risk level
**Donut Projects Title**: Projects by Status
**Donut Projects Caption**: Project distribution by status
**Hours Title**: Weekly Hours Trend
**Hours Caption**: Weekly worked hours evolution
**Hours Last Weeks**: Last 8 weeks
**Hours Month1**: Mar 16
**Hours Month2**: Mar 30
**Tasks By Type Title**: Tasks by Type
**Tasks By Type Caption**: Number of tasks by intervention type
**Type Fallen Tree**: Fallen Tree
**Type Erosion**: Erosion
**Type Broken Plank**: Broken Plank
**Type Water**: Water
**Type Other**: Other
**Type Mud**: Mud
**Type Drain**: Drain
**Type Ruts**: Ruts
**Type Handicap**: Handicap
**Type Others**: Others
**Hours By Member Title**: Hours by Member
**Hours By Member Caption**: Total hours logged per member
**Member1Name**: Francis Lessard
**Member2Name**: Marie Tremblay
**Member3Name**: Julien Côté
**Member4Name**: Sophie Bergeron
**Member5Name**: Alexandre Roy
**Member6Name**: Karine Dubois
**Member7Name**: Maxime Dubois

#### Section1

**Tag**: 01 — EVERY GESTURE COUNTS
**Title**: Every closed task feeds your numbers
**Description**: No separate report to fill out. Every task closed by your team — with photos, time, location — becomes data in your dashboard automatically. The annual report writes itself, while your team works.
Zero double entry — field data feeds reports directly
Photos, GPS and time captured automatically on every task
The annual report builds itself through the season, not at the last minute

#### Section2

**Tag**: 02 — DASHBOARDS
**Title**: Your season at a glance
**Description**: How many open tasks this week? How many kilometers maintained this month? How many volunteer hours this spring? Sentinel dashboards answer all these questions in real time, without anyone compiling manually.
Configurable widgets for the indicators that matter to you
Real-time updates with every task closed in the field
Season, month or week view — filter by trail, activity or team
**Header Title**: Dashboard
**Header Subtitle**: 2026 season · real-time data
**Export Button**: Export
**Kpi Tasks Label**: Tasks closed
**Kpi Km Label**: Km maintained
**Kpi Hours Label**: Hours invested
**Kpi Structures Label**: Structures inspected
**Chart Title**: Activity by month
**Chart Caption**: Tasks closed
**Month1**: Apr
**Month2**: May
**Month3**: Jun
**Month4**: Jul
**Month5**: Aug
**Month6**: Sep
**Activity Title**: Recent activity
**Activity1Name**: Bridge km 3.2 — repair
**Activity1Meta**: Closed · 4h 15
**Activity2Name**: Drainage Blue Trail
**Activity2Meta**: Closed · 2h 40
**Activity3Name**: Structure #42 inspection
**Activity3Meta**: Completed · photos + signature
**Live Label**: Live

#### Section3

**Tag**: 03 — FACTS, NOT IMPRESSIONS
**Title**: When the board asks, you answer
**Description**: "What did the team do this summer?" — before Sentinel, the answer was anecdotal. With Sentinel, you pull a report in two clicks: 147 tasks closed, 32 km of trails maintained, 840 hours invested, 12 structures inspected. Numbers, photos, evidence.
PDF reports ready for boards and funders
Timestamped, geolocated photos archived with every task
Two-click export — no manual compilation at season's end
**Report Title**: Season summary
**Report Number**: 2026 season · Prepared for the board
**Structure Name**: North sector
**Structure Type**: 147 tasks closed · 32 km maintained
**Summary Title**: Summary
**Item1**: Tasks closed (147)
**Item2**: Hours invested (840)
**Item3**: Structures inspected (12)
**Item4**: To monitor (3)
**Signature Name**: Francis L.
**Signature Role**: Operations Director
**Pdf Badge**: PDF ready
**Highlights Title**: Everything you need to prove your work

#### Highlights

**Title**: Exports ready for your partners
**Description**: PDF for your board, Excel for your accountant, photos for your funder. Exports adapt to every audience.
**Title**: Complete history
**Description**: Every task, every intervention, every photo — kept for as long as you keep your account. Perfect for demonstrating continuity of service over multiple years.
**Title**: Configurable dashboards
**Description**: Highlight the indicators that match your reality: tasks by activity, time by volunteer, kilometers per season, structures by status.
**Faq Title**: Frequently asked questions

#### Faq

**Question**: What export formats are available?
**Answer**: PDF (formatted reports), Excel (raw data), CSV (for external analysis). Photos can also be exported as an archive for your presentations.
**Question**: Can I customize the reports?
**Answer**: Yes. You choose the period, the trails, the task types, the team members. The report adapts to what you want to demonstrate.
**Question**: How long is data retained?
**Answer**: As long as your account is active, everything is kept. If you cancel, we keep your data for 90 days to allow a reactivation or a complete export.
**Cta Title**: Stop justifying by guesswork
**Cta Subtitle**: With Sentinel, every report rests on real data. Your credibility — and your grants — will thank you.
**Cta Primary**: Start trial
**Cta Secondary**: See other features

#### Definition

**Title**: What do the reports and the dashboard contain?
**Body**: The dashboard quantifies the state of the network: tasks closed and remaining, structures inspected, time spent, activity per member. The same data exports for a board of directors, a grant report or a partner.
**Replaces**: The end-of-season summary rebuilt from memory, out of photos and old emails.
**Where**: On the web, fed by what the crews enter in the field.
**Definition Tag**: Definition
**Definition Replaces Label**: Replaces
**Definition Where Label**: Where it happens
**Docs Tag**: Documentation
**Docs Title**: How it's done, step by step
**Docs Subtitle**: The documentation articles covering this feature, written for the person who uses it.
**Docs All**: All documentation
**Docs Card Link**: {count, plural, one {Documentation · # article} other {Documentation · # articles}}

## Customers

**Meta Title**: Customer stories — trail networks
**Meta Description**: The trail organizations that run their maintenance on Sentinel, in Canada, the United States and Europe — and what they say about it.
**Title**: Customers

### Hero

**Title**: Who runs their trail maintenance on Sentinel
**Subtitle**: {count} trail networks, outdoor centers, resorts and clubs across Canada, the United States and Europe plan, document and account for their field work in Sentinel. Here is what that looks like, in their words.
**Cta**: Read the testimonials

### Testimonials

**Tag**: In their words
**Title**: What trail organizations say
**Intro**: Testimonials are published as received, with the name of the person and of the organization. Nothing is rewritten.
**Translated From**: Translated from French
**Visit Label**: Visit the website of
**Share Label**: You use Sentinel and want to share your experience?
**Share Cta**: Write to us

### Roster

**Tag**: Organizations
**Title**: Trail organizations using Sentinel
**Intro**: Each one manages a real network — mountain bike singletrack, hiking trails, cross-country ski, fatbike, bike parks. Every link goes to their own website.
**Count**: {count, plural, one {# organization} other {# organizations}}

#### Countries

**CA**: Canada
**US**: United States
**FR**: France

### Outcomes

**Tag**: What changes
**Title**: Three things a trail organization gains
**Intro**: Each one is taken from the testimonials above, not from a feature list.

#### Items

**Excerpt**: see exactly what they need to do on a daily basis
**Title**: The crew knows what to do before it leaves the shop
**Description**: Every report becomes a geolocated task with a photo, a type and a priority. In the morning the crew opens the map, sees what is assigned to it and works down the list — no phone calls, no wasted trips.
**Link Label**: Tasks
**Excerpt**: it eases communication between volunteers and staff surrounding trail projects
**Title**: Volunteers and staff work from the same picture
**Description**: Roles decide who sees what and who can change what, so a seasonal volunteer and a full-time coordinator can share one workspace. Discussions stay attached to the task or the project they belong to, instead of scattering across text threads.
**Link Label**: Team and roles
**Excerpt**: more transparent with our community partners about the time, and money, we invest
**Title**: The hours and the dollars can be accounted for
**Description**: Time is logged on the task it was spent on, and projects carry their own budget. When a municipality, a landowner or a grant program asks what the season cost, the answer is exportable instead of reconstructed from memory.
**Link Label**: Reports and insights

### Faq

**Tag**: Questions
**Title**: About who uses Sentinel

### Cta

**Title**: See what your own network looks like in Sentinel
**Subtitle**: Your trial, built around your trails, your structures and your team.
**Button**: Start trial

### Proof

**Pricing Label**: {count} trail organizations across Canada, the United States and Europe already run on Sentinel.
**Comparison Label**: {count} organizations describe how they work now, in their own words.
**Cta**: See who uses Sentinel

## Community plan

**Title**: Community plan
**Meta Title**: Free Trail Management Software for Nonprofits
**Meta Description**: Full, free access to Sentinel for volunteer clubs, early-stage centers and donation-funded organizations that manage trails. Eligibility reviewed each year.

### Hero

**Title**: Free access to Sentinel for community organizations.
**Subtitle**: The Community plan gives full access to Sentinel, at no cost, to small centers running trails with limited resources — volunteer clubs, early-stage organizations, groups operating on donations. We review eligibility together, and access is renewed each year based on your reality.
**Cta**: Apply now

### Eligibility

**Tag**: Who qualifies
**Title**: It's not your legal status that determines eligibility.
**Intro**: The Community plan is reserved for small organizations running trails with limited resources. It's not your legal status (nonprofit, co-op, association, etc.) that opens access — it's the economic reality of your organization and the role trails play in your mission.

#### Cards

**Title**: Early-stage centers
**Description**: Recently formed organizations building their first trail network or structuring their first operating seasons.
**Title**: Volunteer clubs and groups
**Description**: Collectives without full-time staff, where members maintain trails on their own time.
**Title**: Donation-funded organizations
**Description**: Organizations whose funding comes primarily from donations, fundraisers or membership fees — rather than significant recurring revenue.
**Title**: Organizations finding their footing
**Description**: Groups in transition, formalizing their operations, governance or volunteer management.

#### Note

**Title**: Why reality rather than status?
**Body**: A registered nonprofit can have twenty employees and multi-million-dollar annual revenue. On the other side, a co-op or informal association can run with three volunteers and a handful of donations. Looking at economic reality rather than legal status is the only fair way to treat organizations of every size.

### Included

**Tag**: What's included
**Title**: Full access, no trade-offs.
**Intro**: The Community plan is not a stripped-down version of Sentinel. You get the same tools as established networks — because an organization's size shouldn't limit the quality of its trails.
**See All Plans**: Compare with all plans

#### Items

**Title**: All features
**Description**: Tasks, projects, structure mapping, inspection reports, time tracking, bulk editing and data exports.
**Title**: Full mobile app
**Description**: iOS and Android, with offline mode so you can work on the ground even without a signal.
**Title**: Unlimited users
**Description**: Add as many volunteers, coordinators or admins as needed — no per-user fee.
**Title**: Unlimited trails and tasks
**Description**: Map your entire network and document all your operations with no cap.
**Title**: Onboarding support
**Description**: A kickoff session to set up your organization, import your data and train your team.
**Title**: Continuous updates
**Description**: You get the same improvements and new features as every other customer, in real time.

### Process

**Tag**: How it works
**Title**: Four simple steps to get access.

#### Steps

**Title**: You reach out
**Description**: Fill in the form with a few words about your organization, your trails and your needs. No twenty-page application, no documents to submit up front.
**Title**: We review together
**Description**: A quick email exchange — or a call if needed — to understand your reality. Most requests are handled within one business day.
**Title**: Free access for 12 months
**Description**: Once approved, you get full access to Sentinel for a full year, including onboarding and support.
**Title**: Annual check-in
**Description**: After 12 months we reach out again to understand where you stand. If your reality hasn't changed, access is renewed. If your organization has grown — new recurring funding, paid staff — we discuss a gradual transition to a regular plan.

### Faq

**Tag**: Frequently asked
**Title**: What people ask us.

#### Items

**Question**: What happens at the annual check-in?
**Answer**: We reach out to understand how your organization has evolved. If your reality hasn't changed, access is renewed for another 12-month period. If you've secured significant recurring funding or grown a paid team, we discuss a gradual transition to a regular plan together, with reasonable notice.
**Question**: Are there limits on users, trails or tasks?
**Answer**: No. The Community plan gives access to the same features and the same capabilities as the Pro plan — no user quotas, no trail limits and no cap on tasks.
**Question**: Why doesn't nonprofit status alone determine eligibility?
**Answer**: Because reality on the ground is more nuanced than legal categories. A registered nonprofit can have twenty employees and multi-million-dollar revenue; a co-op or association can run with three volunteers and a handful of donations. Looking at economic reality rather than legal status is the only fair way to treat organizations of every size.
**Question**: Is there a risk of losing access suddenly?
**Answer**: No. Access is always granted in 12-month blocks, and any transition to a regular plan is discussed together with enough notice to plan. The goal isn't to surprise you — it's to support your growth.
**Question**: Can a volunteer team use Sentinel without technical training?
**Answer**: Yes. Sentinel is designed to be used on the ground, with or without an internet connection. Onboarding covers setting up your organization and training your team. Most volunteers are self-sufficient after a single session.
**Question**: Can we try Sentinel before applying?
**Answer**: You can start a free 30-day trial with no commitment, or ask our team to set it up with you through the 30-day trial page. Neither is required to apply to the Community plan — if you're already convinced, go straight to the form.

### Cta Section

**Tag**: Apply
**Title**: Tell us about your organization.
**Subtitle**: A real person reads every request and typically replies within one business day, in French or English.

### Form

**Panel Badge**: What to expect
**Panel Title**: A real person reviews every application — no ticket queue, no bot reply.

#### Panel Items

**Title**: Reply within one business day
**Description**: Most requests get a detailed answer the same or next working day.
**Title**: Reviewed by the product team
**Description**: You'll hear from the people who actually build and run Sentinel.
**Title**: Available in French and English
**Description**: Write us in whichever language you prefer — we reply in kind.
**Name**: Full name
**Email**: Email
**Organization**: Organization you represent
**Message**: Tell us about your needs
**Newsletter Label**: Subscribe me to the Sentinel newsletter
**Newsletter Help**: One email per month, unsubscribe in one click.
**Send**: Send request
**Sending**: Sending…
**Success Title**: Request sent
**Success Message**: Thanks for reaching out. We'll review your eligibility and get back to you shortly.
**Error Rate Limited**: Too many attempts. Please try again in a few minutes.
**Error Verification**: Please complete the spam verification before sending.
**Error Generic**: Something went wrong. Please try again later.

## 30-day trial

**Title**: 30-day trial
**Meta Description**: Start a 30-day free trial of Sentinel. Tell us about your organization and our team will set up your trial account. Full access, no credit card required.

### Hero

**Title**: Start your 30-day free trial of Sentinel.
**Subtitle**: Tell us about your organization and our team will configure your trial account. Full access, no credit card required.

### How It Works

**Title**: How the 30-day trial works

#### Items

Tell us about your organization
Our team sets up your trial account
Full access to Sentinel for 30 days, free
We follow up to help you get started
**Note**: Our team personally configures each trial to match your organization's needs — you'll hear back within one business day.

### Form

**Name**: Full name
**Email**: Email
**Organization**: Organization you represent
**Message**: Tell us about your project
**Newsletter Label**: Subscribe me to the Sentinel newsletter
**Newsletter Help**: One email per month, unsubscribe in one click.
**Send**: Request trial
**Sending**: Sending…
**Success Title**: Request sent
**Success Message**: Thanks for reaching out. Our team will contact you shortly to set up your trial.
**Error Rate Limited**: Too many attempts. Please try again in a few minutes.
**Error Verification**: Please complete the spam verification before sending.
**Error Generic**: Something went wrong. Please try again later.

## Customers

### Canada

- Sentiers du Moulin
- Mont-Sainte-Anne
- Empire 47
- Parc des montagnes noires
- Contact Nature
- Parc du Mont-Saint-Mathieu
- Association Plein Air Shediac Outdoors Association

### United States

- Copper Harbor Trails Club
- SORBA
- Stowe Trails Partnership
- Slate Valley Trails
- Polaris

### France

- Val d'Isère

#### Kenzie Brunner, Stowe Trails Partnership — Stowe, Vermont

40 mi · 64 km of trail maintained.

"Sentinel has been integral to maintaining over 40 miles of trail for our organization. Not only does it allow our trail crew to see exactly what they need to do on a daily basis, but it eases communication between volunteers and staff surrounding trail projects. Tracking projects, infrastructure, and more has allowed us to be more transparent with our community partners about the time, and money, we invest in our trail networks to ensure our town continues to be a destination for riding."

#### Marilou Tremblay, Contact Nature — Saguenay, Quebec

92 fishing pools on a salmon river.

"As an organization dedicated to preserving, restoring and showcasing natural environments, Sentinel has become a valuable ally for our teams! Whether it is managing our hiking, snowshoeing and cross-country ski trails, our ice fishing villages or our 92 fishing pools on a salmon river, the app lets us coordinate the work, monitor our infrastructure, run our quality controls and assign tasks far more simply and efficiently. We especially appreciate being able to share access not only with our employees, but also with our volunteers and with certain active users who work directly alongside our teams in the field. Sentinel lets us structure our operations better, centralize information and, above all, make collaboration in the field easier. We recommend it without hesitation!"

#### Nick Ryan, Trails Coordinator, Copper Harbor Trails Club — Copper Harbor, Michigan

60 mi · 97 km of singletrack maintained.

"This is our first year using Sentinel, and it has absolutely smashed our expectations. As a Trails Coordinator, finding ways to improve staff and volunteer efficiency while better conveying the work we complete to landowners and grant administrators was at the top of my list of off-season tasks this past winter. Sentinel has been integral in making these struggles a non-burden, allowing me to focus on the work that has a greater impact on the user experience. Along with the base functions that were already a major step up from our existing platform, the team at Sentinel has been excellent at accommodating our needs and adding functions that have supported our work. In instances where we have had technical issues, they have been excellent in finding quick solutions to our problems. In summary, the platform and the team are excellent, and I am excited to use it in the future to continue creating better trail experiences for staff, volunteers, landowners, and users alike!"

## Documentation

### Your first sign-in: linking your account to a trail site

URL: https://trail-sentinel.com/en/docs/first-sign-in
Applies to: web, mobile

You've just installed Sentinel, you sign in, and the app tells you one last step is missing. That's normal: an account and a **trail site** are two different things, and you have the first without having the second yet.

This page explains what happens at that moment, and the two ways out of it.

**Where:** the first screen of the mobile app after signing in, and the home page of the web app as long as no site is linked to your account.

#### Signing in, without a password

Sentinel has no password. You enter your email, you tap **Continue**, and a **verification code** is emailed to you. You type it in, you tap **Validate**, and you're in.

If the code doesn't arrive, **Resend code** generates a new one — and it's worth checking the junk folder, by far the most common cause.

The same email covers signing in and signing up: there aren't two forms to choose between.

**If the page opens in the wrong language**, the **FR / EN** selector sits in the top-right corner of every screen of this flow, on the web app. You don't need to be signed in to use it, and the choice sticks on that browser.

#### An account is not a trail site

This is the only concept you need for what follows.

**Your account is you.** Your email, your name, your preferences, your notifications. It follows you from one site to another.

**A trail site is the organization.** Its trails, its tasks, its structures, its members, its roles, its subscription. Every bit of content in Sentinel belongs to a site — which is why an account without one has nothing to show.

You can belong to several sites: a bike club and a municipality, for instance. You switch between them without signing out.

#### The "One last step" screen

On mobile, an account with no site opens straight to this screen. There's no map behind it, and that's deliberate: nothing loads and nothing tracks your position as long as there is no data to show.

_The screen an account sees before it has a site._
1. **Create my site** opens the setup wizard in your browser.
2. **Get me invited** shares your account address — the one shown right below it.
3. **I am done, check again** re-reads your account without restarting the app.

At the bottom, two quiet links stay available: **Settings**, for your profile and notifications, and **Log out**, in case you used the wrong email.

#### The same screen, in the web app

If you sign in from a computer, you don't land on the dashboard but on **Welcome to Sentinel**, which lays out the same two paths one under the other.

_The home page of an account that doesn't have a workspace yet, in the web app._
1. **Create my workspace** is the highlighted one: it's the usual path on a computer.
2. **Join an existing account** isn't a button — it's a reminder of what has to happen.
3. The address the invitation has to be sent to, so no one gets it wrong.

**The second block isn't clickable, and that's fine.** Joining an organization isn't up to you: the block simply reminds you that an administrator has to invite you, and that the invitation will show up here on its own.

**When an invitation is waiting, the page changes entirely.** It shows the logo and the name of the organization inviting you, who sent the invitation, the activities practised there, and the **role** you were given — so you know what you are stepping into before you accept. Two actions are left, **Accept** and **Decline**; creating a workspace of your own becomes a plain link at the bottom.

**If two organizations invite you at the same time**, the page lists them one under the other, each with its logo, who is inviting and the role planned for you. Sentinel doesn't choose for you.

**Nothing to refresh.** As long as you stay on this page, it listens: if you just asked an administrator for your invitation, it shows up on its own the moment they send it. That applies to this page only — nothing shifts under your hands while you are going through the workspace setup.

#### Creating your site from a computer

This is the path for whoever is setting Sentinel up for their organization. Do it **on a computer**, not on the phone: it involves dropping track files, which is far more comfortable with a keyboard.

Open `app.trail-sentinel.com/onboarding`. You'll be asked to sign in if you haven't already, then the wizard walks you through five steps.

**About you.** Three quick questions: the kind of organization you run, your role, and how you heard about Sentinel.

**Your network.** The activities practised where you are — mountain biking, hiking, cross-country skiing, snowmobiling… — which one opens by default, and roughly how big the network is. You can add more later, as covered on the [activities](/en/docs/manage-activities) page.

**Your workspace.** The organization's name, its logo if you have one handy, and the address. The address field suggests matches as soon as you type, and the address has to be **picked from the list** — with the mouse or the arrow keys; city, province, country and postal code then fill themselves in. The address is what centres your map on your territory, and that's why it goes through the list: it has to be an address that really exists. If yours doesn't come up — common for a forest road or a rural address — pick the closest existing one; you can always change it later. This is the step that creates the site — and you are its **administrator**.

**Your plan.** The first 30 days give access to everything, free and **with no credit card**. You choose afterwards. If you're a non-profit or a volunteer club, a banner offers the **Community** plan: full access, free, on request.

**Your trails.** Drop your track files — `.gpx`, `.kml`, `.kmz`, or a Shapefile `.zip`. Sentinel creates **one trail per track found** in the main activity, showing them on a map as they come in. This step can be skipped: nothing stops you from importing later from [trails](/en/docs/manage-trails).

At the end, the wizard announces that your workspace is ready, counts the trails imported, and opens your dashboard.

#### Getting invited

This is the path for whoever is joining an organization that's already set up. You can't add yourself: **an administrator has to invite you**, and they do it from [members](/en/docs/invite-and-manage-members).

**Only one thing matters: the address.** The invitation goes to one specific email, and it's only recognized by the account carrying that exact email. That's what the **Get me invited** button is for: it opens your phone's share sheet with a ready-made message containing your address, to send by text or email to whoever manages access.

**You have nothing to accept.** When an invitation arrives and you have no site yet, it **applies itself**: Sentinel accepts it and opens the site. You don't even need to be in the app at the right moment.

**Unless there are several.** Two organizations inviting you at once? Sentinel won't choose for you: a **Pending invitation** card appears, with the name of the person inviting and the name of the site, and you **Accept** or **Decline**.

What you see next depends on the role you were given — see [roles](/en/docs/understand-roles). Two people on the same site don't necessarily get the same sections.

#### Checking without restarting the app

The screen listens continuously: the moment the invitation goes out, it should switch on its own. But when you've just hung up with the person who invited you, waiting isn't satisfying.

**I am done, check again** re-reads your account on demand. If there's still nothing, the screen says so — "Still nothing on that side." — instead of leaving a spinner running with no answer. It isn't an error: the invitation simply hasn't been sent yet, or it went to a different address.

#### Permissions, on the first launch

Once your site is attached, the mobile app doesn't open on the map yet. It shows **Welcome to Sentinel** first, then walks you through a few screens that explain, one by one, what it needs from your phone.

There are four steps, and each says what the permission is for before asking for it:

| Step | What you lose without it |
|---|---|
| **Location** | Seeing yourself on the map, creating a task at your position, scanning what's around you |
| **Camera** | Photographing a problem on site — you can still attach a photo you already took |
| **Microphone** | Voice memos and dictation — typing still works |
| **Notifications** | Alerts for assigned tasks, messages, and pending synchronization |

**The button always leads to your phone's own request.** It's your phone that asks you to allow or deny, not Sentinel — the Sentinel screen is only there to explain why the question is coming. On Android, a **Deny** button is offered before the system request.

**Nothing is mandatory, but location changes everything.** Without it you can read and edit; you lose everything that depends on your position. The detail is in the [geolocation settings](/en/docs/geolocation-settings).

**A step you've already settled doesn't come back.** Sentinel only explains the permissions still missing. And as long as one is missing that your phone will still answer for, the screen returns on the next launch — deliberately: a team that discovers three months later that its GPS was never allowed has lost three months of positions.

**After a refusal, the screen stops coming back.** Your phone won't let the question be asked again; it has to go through its settings. Sentinel points you there instead of nagging you for nothing.

#### Three things worth knowing

**Whoever creates the site is its administrator.** They're the one who invites everyone else and manages the subscription. So create the site with the account of the person who will actually look after it, not with a throwaway address.

**Nothing is lost if you take the wrong path.** An account created "for nothing" bothers no one: it waits for an invitation. There's no phantom site to delete as long as you haven't finished the wizard.

**The mobile app doesn't need reinstalling.** Once the site is linked, the map opens and the data comes down to the phone on its own — the subject of the page on [working offline](/en/docs/work-offline).

### Deleting your account: what goes, what stays

URL: https://trail-sentinel.com/en/docs/delete-your-account
Applies to: web, mobile

A Sentinel account is deleted **from the mobile app or from the Web app**, two steps away in either case. Deletion is **permanent**: it cannot be undone, and nothing that is erased can be recovered.

This page describes the exact flow, the important difference between what disappears and what stays in the trail site, and the special case of an owner.

**Where:** on mobile, the gear at the top of the home screen → your name under **Profile** → **Delete account**. On the Web, your **picture** at the top right → **Edit profile** → **Delete account**.

#### The flow on mobile, step by step

**Open the settings.** The gear, at the top of the home screen, to the right of your trail site's name.

**Tap your name**, the first row under the **Profile** heading. That is your account screen: your picture, your name, your email.

**Tap "Delete account"**, the last row of that screen.

_Your account screen, on mobile._
1. **Delete account** closes the list: it is the last row, below your fields.

**Read the screen.** It lists what will be deleted and what will be kept. If you own a trail site, an orange banner at the top of the screen tells you what will happen to it — see below.

**Choose the new owner**, if the screen asks you to. The site's administrators are listed right under the banner; tap the one who should inherit the site.

**Enter your email address.** The one on your account, exactly. Capitalization does not matter; the address does. As long as it does not match, the button stays inactive and a message says so.

**Tap "Delete permanently"**, then confirm in the dialog that appears. The app returns you to the sign-in screen: it is done.

The screen that opens gathers everything you need to know before confirming.

_The deletion screen, for a site owner._
1. The orange banner only shows if you own a trail site.
2. The list of administrators: tap the one who should inherit the site.
3. Your email address, to type exactly.
4. The button stays inactive until both of the above are done.

There is **nobody to contact** and no waiting period. You do not need to email customer support.

#### The flow on the Web

The same flow exists in the Web app in another shape: a dialog instead of a screen.

**Click your picture**, at the top right, then **Edit profile**. Your account panel opens on the right.

**Click "Delete account"**, at the bottom of the panel, below your Name and Email fields.

_Your account panel, on the Web._
1. The **danger zone** gathers what cannot be undone, and states what the action erases.
2. The button that opens the deletion dialog.

The dialog that opens holds exactly what the mobile screen holds: the owner panel if it applies, the list of administrators to hand the site to, what will be deleted, what will be kept, then the confirmation field. **Delete permanently** stays inactive until your email address is typed — and until an administrator is chosen, if you are asked to.

_The deletion dialog, on the Web._
1. The same orange banner as on mobile, if you are an owner.
2. The checked administrator is the one who will receive the site.
3. Your email address, then **Delete permanently** becomes active.

One difference worth knowing: the Web app **has no offline mode**, so there is nothing to sync first. On mobile, do check your sync queue — see below.

#### What gets deleted

- **Your profile**: name, email address, phone number, picture.
- **Your access** to every trail site you are a member of. You leave each one.
- **Your notifications**, your notification settings, your preferences and your pending invitations.
- **Your sessions**: every sign-in is revoked, on every device.
- **Your activity history** — the record of your actions in the site's log.
- **All Sentinel data stored on the device** you delete the account from: on the phone, trails, structures, tasks, conversations, checklists and photos still waiting to upload; in the browser, whatever the Web app keeps in reserve.

That last point deserves care **on mobile**: changes that have not synced yet are lost. If your sync queue is not empty, the app warns you before you confirm. Get back online and let the sync finish before deleting, if that work matters.

#### What stays

**The tasks, inspection reports, messages and time entries you created stay in the trail site** — without your name. The author becomes an anonymous deleted account.

This is not an oversight. That work describes the state of a trail network: a bridge inspected, erosion reported, a repair done. It belongs to the organization running the network, not to the person who entered it. A volunteer who closes their account in October should not erase the season's inspection history.

#### If you own a trail site

The owner is the person who created the site. Deletion is never blocked for them — but it has a consequence, and the screen tells you before you confirm. Three cases, depending on who is left behind.

**If administrators remain, you pick which one becomes the owner.** They are listed under the banner with their name and email address; you tap one, and only then does the delete button become active. The site keeps working normally and your subscription stays active — it simply changes hands.

That choice is deliberately not automated: deciding who inherits a trail network, its subscription and its billing is not a decision the app should make for you.

**If members remain but no administrator does**, there is nobody to pick. Ownership then passes to the longest-standing member. If that is not what you want, **appoint an administrator before** coming back here — see [roles](/en/docs/understand-roles) and [managing members](/en/docs/invite-and-manage-members).

**If you are the only member**, the trail site is closed and its subscription is cancelled. Nobody can reach it any more. If you want to keep it, **invite and promote an administrator before** deleting your account.

#### Afterwards

Your email address **becomes available again**. You can create a new Sentinel account with the same address whenever you like — it will be a brand-new account, unconnected to the old one, with no access to the trail sites you had.

There is **no way back**: creating a new account restores nothing. To get into a trail site again, you have to be invited again.

#### A pause instead of a deletion

If all you want is to stop the noise — the end of a season, a leave, a role changing hands — deleting is out of proportion. Two lighter moves do the job:

- **Turn off your notification channels** in [the notification settings](/en/docs/notification-settings). A single switch silences email or phone alerts, and you turn it back on when you return.
- **Just sign out**: **Settings → Sign out** on mobile, your picture → **Sign out** on the Web. Your account and your access stay intact.

An administrator can also remove you from a trail site without touching your account: you lose access to that site and keep everything else.

### Report a problem from the map

URL: https://trail-sentinel.com/en/docs/report-a-problem-from-the-map
Applies to: mobile

When you come across a fallen tree, a broken plank or an eroded section, there is nothing to write down on paper. The app creates the task exactly where you are standing, and it keeps it even if you have no coverage.

**Where:** mobile app, the **Field** view — the home screen.

#### The Field view

The Field view is the home screen of the mobile app. It shows your trails, the tasks already reported, the structures on record, and your own position.

_The Field view, home screen of the mobile app._
1. The active place and current view. Tap the pill to switch place or view.
2. The task-type filter. Tap an icon to show only that type on the map.
3. A task already reported. The icon shows its type — erosion, in this case.
4. The create button. This is your starting point for everything you add.

Type filters stack: tap several icons to show several types at once. An icon ringed in green is active. Tap it again to turn it off.

#### Create the task

Tap the **+** button, bottom right. The map fades out and a fan of choices opens above the button.

_The create button, fan open._
1. Up to five choices: to-do, task, project, structure, report.
2. The **+** button. Tap it again to close.

You won't necessarily get all five: **each entry only appears if your role may create that kind of item.** A volunteer who can only report will see **To-do** and **Task** alone.

To report a problem, it's **Task**.

**Pick the position.** By default the app uses your GPS position. You can move it on the map if the problem sits a few metres away from you.

**Attach it to the right trail.** If your position is close to a trail, the app suggests it automatically. Check that suggestion — it is what makes the task show up in the right trail's reports.

**Document it.** Add the type, a priority, a photo and a description. A photo often beats a paragraph: whoever picks the task up will know what to bring.

#### Without coverage

If you have no signal, nothing changes in the flow: the task is created, visible right away, and queued. It leaves for the server as soon as the connection is back.

You can see what is still waiting to be sent in the sync screen, from your account settings.

### Annotating on the map: showing the extent, not just the spot

URL: https://trail-sentinel.com/en/docs/annotate-on-the-map
Applies to: web, mobile

A task marker says "there's a problem **here**". It doesn't say whether that's three metres or three hundred.

**Map annotations** answer that. On a task's map you can draw the flooded area, trace the reroute to open, drop a point on the stump to pull and attach two photos to it. Whoever picks up the task sees the size of the job before leaving — and loads the right gear.

**Where:** on a task's form — the **Annotate on the map** button on the web, the **Annotate** chip on mobile.

#### Where to find it

Annotations live **on a task**, both when creating and when editing, on web and on mobile.

_The button, on the form's map preview._
1. The button sits over the map preview, top left.

On the **web**, the **Annotate on map** button sits on the map preview of the task form. On **mobile**, it's the **Annotate** chip at the top right of the task's map header — with a counter as soon as there are annotations.

Two limits to know:

- The task must **have a position**. A to-do, which has none, has no annotations.
- Annotations belong to **tasks**. Structures and inspection reports don't have them.

#### Three tools

Whatever the device, it's the same three shapes.

| Tool | What it is | What it gives you |
|---|---|---|
| **Zone** | A closed polygon, 3 corners minimum | The extent of the affected sector, readable at a glance |
| **Line** | An open path, 2 points minimum | A route, with an adjustable width |
| **Point** | A marker dropped at a precise spot | A photo holder: the only shape that takes images |

**Measurements show on the web, not on the phone.** In the web annotation dialog, the layer list gives a zone's **area** in m² and a line's **length** in metres, under the annotation's name. That isn't decoration: a 1,240 m² zone is a figure that goes into a grant application. On mobile those figures aren't displayed — the only measurement the phone shows is the GPS recording counter, while you walk a line. Draw in the field, read the measurements at the desk.

**The point is the most useful of the three.** It's the only one that carries photos, and that's what turns a task into a file: the photo of the stump is attached to the stump, not lost in a pile of uncaptioned images.

#### The dialog, on the web

_The annotation dialog._
1. The tools: select, zone, line, point.
2. The layer list, with the eye to hide and the bin to delete.
3. The properties of the selected annotation.

Pick a tool, then click the map to draw. **Double-click to finish** a zone or a line. Go back to the select tool to rework a shape: its corners become draggable, and the midpoints let you insert new ones.

The right column is the **layer list**. It holds your annotations, but also **the task's own point or segment** — which you can hide with one eye while you draw over it. Hiding erases nothing: it's a working convenience.

Below the list are the **properties** of the selected annotation:

- its **name** — with no name it's "Zone 1", "Line 2"; with a name it actually says something;
- its **colour**;
- for a line, its **width**, from 1 to 12 pixels;
- for a point, its **photos**.

Nothing is stored until you click **Confirm** — and then **save the task**. That's what trips people up most: confirming the dialog only brings the annotations back into the form.

#### In the field

_Annotating on mobile._
1. Close on the left, confirm on the right.
2. The hint tells you what to do with the current tool.
3. The four tools, including the photo survey.

Mobile takes the whole screen: the map goes full screen and the controls live in a dark bar at the bottom. You tap the map to place corners, and **Finish** closes the shape.

Three things mobile can do that the web can't:

**Follow GPS.** On a line, instead of drawing it with your finger, tap **Follow GPS** and **walk the path**. The button only shows while you haven't placed a point yet: you pick one method or the other at the start. The phone records your track and smooths it — points that are too imprecise, too close together or too fast are dropped. That's the right way to survey a real reroute, the one that actually gets around the obstacle.

**Use my current position.** On a point, this button drops it where you stand. You're in front of the stump: one tap and it's mapped.

**The photo survey**, the fourth tool — the rest of this page.

To rework an annotation, tap it: its corners appear, a handle at the centre moves the whole shape, and the midpoints insert new corners. The bottom bar then turns into an editor: name, six colours, a swatch for a free colour, width for a line, photos for a point.

On the way out the app asks you to **keep your changes**. Same story: keeping brings them back into the form, you still have to **save the task** to apply them.

##### The photo survey

_The photo survey._
1. The current GPS accuracy — green under 10 m.
2. Merging photos taken in the same place.

The photo survey turns the logic around: instead of dropping a point and then adding a photo to it, **you take the photo, and the point places itself where you shot it**.

It's the walk-the-trail tool. You head down the trail, photograph what's wrong, and come back with a series of geolocated points — without having touched a map once.

Two details that matter:

**The accuracy chip** at the top right shows the GPS margin of error: green under 10 m, orange up to 25 m, red beyond. Under dense canopy, wait for it to settle before shooting — otherwise your points will be off.

**Merging.** Turned on, two photos taken less than eight metres apart land on **the same point**. That's what you want to photograph one problem from three angles. Turn it off if you're documenting distinct things that happen to be close together.

#### What everyone else sees

Once the task is saved, the annotations show on its map in both apps. They also follow the task **beyond** Sentinel:

- on a **public share link**, the public map shows the annotations;
- the **GPX**, **KML** and **GeoJSON** exports carry them, ready to open in mapping software.

That's what makes the effort pay: the drawing done once serves the person doing the work, then the report, then the funder.

#### Three pieces of advice

**Name what you draw.** "Zone 1" tells nobody anything. "Flooded section at thaw" still makes sense six months later.

**One colour per kind of problem.** Red for what blocks, orange for what needs watching, green for the shape of the fix. The code doesn't need to be written down: it becomes obvious after three tasks.

**Walk your lines rather than drawing them.** A reroute traced with a finger over satellite imagery often runs through a bank. The same survey done on GPS is accurate to the metre.

### Annotating a photo: circle it, point at it, explain it

URL: https://trail-sentinel.com/en/docs/annotate-a-photo
Applies to: mobile

A wide shot of the undergrowth shows nothing. The same frame with a red circle around the break and an arrow pointing at it becomes an instruction.

That's all this tool does: **draw freehand on a photo**, on the phone, before attaching it.

**Where:** mobile app, on any photo you've already added — tap it to open the editor.

#### Where it works

Everywhere you add a photo from the mobile app:

- a **task**, when creating and when editing — to-dos included;
- a **structure** and an **inspection report**;
- a **discussion message**, as long as it hasn't been sent yet.

The gesture is the same everywhere: tap a photo already added in the media list. The editor opens over it, full screen and black.

This is a **mobile-only** feature. On the web you add photos, you don't annotate them.

#### The editor

_The annotation editor._
1. Undo and redo, next to the title.
2. Five colours, plus a swatch to pick your own.
3. Three stroke widths.

There's only one gesture: **your finger draws**. No ready-made shapes, no text, no automatic arrows — a pen, and that's it. That's deliberate: on a phone, with gloves on, a pen is faster than a tool menu.

The settings are down to the essentials:

- **five colours** — red, yellow, blue, white, black — plus a swatch that opens a full picker if none of them fits;
- **three stroke widths**;
- **undo** and **redo**, stroke by stroke.

Red and yellow are the two that carry on a forest photo. White and black are for very dark or very bright shots — a white stroke on wet bark reads better than a red one.

The tick at the top right stays **disabled until you've drawn something**: nothing to save, nothing to do.

#### Replace or copy

_The choice on save._
1. The choice only appears when the photo is already attached to an existing record.

When you confirm, the app **flattens** your drawing and the photo into a single new JPEG. The strokes are now part of the image: they can't be edited again.

Depending on where you came from, two behaviours:

| Where you are | What happens |
|---|---|
| A record you are **editing** | You're asked: **replace the original** or **create a copy** |
| A record **being created**, or a discussion message | The annotated photo **replaces** the original, no question asked |

**Create a copy** is the right choice when the photo is evidence. You keep the raw state of the site — useful if someone disputes it, or for an insurance file — and the annotated version sits beside it as the instruction.

An annotation can't be undone after the fact. If you replaced and you regret it, you have to take the photo again.

#### Three pieces of advice

**Annotate before sending, not after.** In a discussion, the tool is only available on photos still in the composer. Once the message is out, the photo is fixed.

**A circle beats a paragraph.** "The broken plank is the third one from the left" has to be read twice. A red circle doesn't.

**Keep the original when the photo documents an incident.** For a condition record, a damage claim or an insurance file, the annotated copy adds to the evidence — it shouldn't replace it.

### Working off the network: how Sentinel handles no signal

URL: https://trail-sentinel.com/en/docs/work-offline
Applies to: mobile

A valley-bottom trail, a mountain sector, a boardwalk under dense canopy: the network isn't where the work is. That's Sentinel's starting constraint, and the app is built around it.

The rule is one sentence: **nothing you do in the field waits for the network.** You create, you edit, you photograph, you log your time. Everything is written to the phone immediately, and leaves later on its own.

This page explains the whole mechanism — what's stored, what goes out, in what order, and what happens when two people changed the same thing.

**Where:** nothing to turn on — working offline is always on. The **Sync** screen, in your account settings, shows what hasn't been sent yet.

#### What you carry with you

Before you even lose signal, the app has already filled your pocket.

Every time you **open the app** and every time you bring it back to the foreground, Sentinel quietly reloads a local copy of the active place:

- every **task** in the current activity and their projects;
- the detail page of the tasks in **your planning** and of each project's tasks;
- the **structures** and their pages;
- the **checklists** for the current season;
- the **trails**, types, folders and the place's reference data — those arrive through a separate, versioned channel, described in [installed data](/en/docs/installed-data).

So it isn't "whatever you looked at recently": it's the whole place, preloaded. You can leave with the phone in airplane mode and open any task on the network.

Two limits, set so your device doesn't fill up:

- at most **200 detail pages** from your planning and **30 projects** in detail;
- the oldest pages are **pruned** over time.

Beyond that the list stays readable, but the detail page of a task you never opened may be missing.

**Discussions** follow a different rule: only the threads you've already opened are cached. A discussion you never looked at isn't readable off the network.

#### What you see when it cuts out

_The confirmation after creating something off the network._
1. The message says the task is saved and will go out later.
2. The chip appears for a few seconds when the network is gone.

Two signals, and nothing more:

**The "Offline mode" chip** appears at the bottom of the screen when the app notices the network is gone, then fades after a few seconds. It comes back if you reopen the app, still offline. It blocks nothing.

**A confirmation message** appears when you save something without a connection: *"Your task has been created and will be synchronized when your internet connection is restored."* There's a variant for each gesture — task updated, structure created, report created, time logged.

That's deliberately quiet. Having no network is the normal state in the field, not a failure.

#### What you can do without a connection

Almost everything that produces work:

| You can | Detail |
|---|---|
| **Create a task** | Point, segment or to-do, with photos, materials, annotations |
| **Edit a task** | Any field, including status and assignee |
| **Delete a task** | The deletion goes into the queue like everything else |
| **Log time** | The entry is saved with its task |
| **Tick a sub-task** | And a checklist item |
| **Create, edit, delete a structure** | And create an **inspection report** |
| **Write in a discussion** | The message goes out when the network returns |
| **Take photos** | They follow their own queue — see below |

What is **not** possible off the network: anything that needs an answer from the server right then — signing in, switching place, opening a page that was never cached, or administration data.

Every gesture becomes a **pending item**, written to the phone. That list is what we call the sync queue.

#### How the queue empties

_The Synchronization screen._
1. The button retries everything pending or failed.
2. A pending item: its type's icon, and the time of the gesture.
3. An item needing attention is orange and opens with one tap.

The **Synchronization** screen, in the account settings, is the source of truth: it lists what hasn't gone out yet.

##### When it goes out

The queue restarts on its own on four triggers:

- **the network comes back**;
- **you reopen the app**;
- **you add** a new item;
- **the system wakes the app in the background** — the phone picks the moment, but the queue can empty without you opening anything.

The **Sync all** button forces an immediate pass. It's greyed out when there's nothing to send, or when there's no network.

##### In what order

**Oldest first.** The queue's order is the order of your gestures, which guarantees a task created at 9 am exists before its 11 am edit goes out.

An item that can't be read or is permanently rejected is set aside rather than blocking the queue: **one problem never holds up the rest**.

##### When it fails

A failed send isn't lost, it's retried — with a delay that **doubles each time**: about one second, then two, four, eight… up to a five-minute ceiling. After **ten attempts**, the item is marked failed and waits for your decision.

That spacing is deliberate. At the edge of coverage, where the network comes and goes, retrying non-stop would drain the battery without sending anything.

Two reminders warn you if it drags:

- after several consecutive failures, a **box appears in the app** with a *Fix* button that goes straight to the Synchronization screen;
- **reminder notifications** are scheduled at 2 h, 4 h, 8 h and 16 h while items remain pending — never between 10 pm and 8 am.

#### An item's states

| What you see | What it means |
|---|---|
| The type's icon, in grey | **Pending** — it will go out on the next pass |
| A blue sync icon | **Sending** |
| An orange icon with two bars | **Conflict** — someone else touched the same thing |
| An orange icon with an exclamation mark | **Failed** — the send didn't work |

The last two are tappable: that's where you decide.

#### Conflicts

This is the part that matters. You were off the network; meanwhile, the person at the office may have touched the same task. Sentinel tells four situations apart.

##### A similar task already exists nearby

When a task or structure created offline finally goes out, Sentinel first checks whether **one of the same type already exists right beside it**. That's the classic case: two volunteers report the same fallen tree on the same Saturday.

The item goes into conflict and shows you the candidates. It's up to you to say **Create anyway**, if it isn't the same problem, or to delete your item if it's a duplicate.

That check only happens on send — it needs the server. Which is why it sometimes shows up hours after the creation.

##### Someone edited the task while you were away

_Resolving an edit conflict._
1. Only genuinely contested fields are listed.
2. Your value is kept by default.

This is the most interesting case, because Sentinel settles **most of it by itself**.

The app doesn't send the whole task back: it sends **the fields you changed**, and for each one it knows what the value was when you changed it. At send time, three cases per field:

- the server **already has the same value** as you → nothing to do, move on;
- nobody touched that field → **your change is applied**, silently;
- someone changed it, differently from you → **conflict on that specific field**.

In practice: if you changed the status and your colleague changed the description, **there is no conflict at all**. Both edits land. You're only interrupted for what is genuinely contested.

When a contested field remains, the screen shows **My value** and **Server value** side by side, field by field. Yours is kept by default; you flip whichever you want, then **Apply**. Or **Discard changes**, and the server's version stands.

##### The task was deleted

If the task disappeared from the server in the meantime, your edits can no longer apply. The screen tells you, shows what you had changed, and your only option is to discard. That's the one case where offline work is genuinely lost — and it's because its target no longer exists.

##### You had asked for a deletion

If you deleted a task offline and someone has edited it since, you're asked to confirm: **Delete anyway** or **Cancel deletion**.

#### Photos

Photos have **their own queue**, separate from the rest. That's on purpose: a photo weighs a hundred times a status change, and a slow upload must not hold up your other gestures.

Three things to know:

**They wait for their task.** A photo taken on a task created offline can't go out before the task actually exists on the server. The queue handles it: as soon as the task is created, the photos waiting on it are attached automatically.

**Three at a time, no more.** So a weak connection doesn't get saturated.

**A watchdog looks for stalls.** An upload that drags on is detected and restarted. If it persists, the app offers: *"Media upload stuck — Retry?"*

On Android, an upload in progress keeps going even if you leave the app.

#### The one trap

**Don't log out with pending items.**

The queue lives on the device, tied to your session. Logging out wipes the local data — and with it everything that hasn't gone out. The app warns you first, with an explicit message, but the warning is easy to swipe past.

The safe rule: **before logging out or uninstalling, open the Synchronization screen and check that it says "Everything is synchronized".**

The same reasoning applies to a lost or reset phone: what hasn't gone out exists nowhere else.

#### What about the web?

The web app **does not work offline**, and that's on purpose: you use it at a desk, on a connection.

It does share the same protection against concurrent edits. If two people change the same task at the same time, the server detects the mismatch and the same logic applies: what nobody else touched goes through, the rest is flagged.

#### Four pieces of advice

**Open the app before you leave, while on the network.** Thirty seconds of Wi-Fi in the parking lot and you leave with the whole place in your pocket.

**Don't count on pages you never opened.** The preload covers the essentials, but it's bounded. If you know you'll be working on a specific project, open it once before leaving.

**Check the Synchronization screen when you get back.** Thirty seconds, once per outing. It's the only maintenance the offline mode asks of you.

**Deal with conflicts the same day.** A two-week-old conflict is one nobody remembers — and the right answer becomes impossible to give.

### Reading a task on mobile: the map and the list

URL: https://trail-sentinel.com/en/docs/tasks-on-mobile
Applies to: mobile

Out in the field you read more than you type. The same task exists in two forms on the phone — a **marker** on the map, a **card** in the list — and the two don't tell you the same thing.

This page describes every visual element: what it encodes, and above all what it doesn't.

**Where:** mobile app, the **Field** view. The pill at the top right switches between the map and the list.

#### Two views, one filter

_Markers on the map._
1. A task's marker: a white teardrop, a grey disc, the type's icon.
2. A structure: a circle, never a teardrop.
3. The pill that switches between map and list.

The floating pill at the top right has two halves: the **globe** for the map, the **list** for the list. The white cursor slides onto whichever is active.

**Your choice sticks.** Next time you open the app you land on the view you left — it's a per-place preference, not a global setting.

Both views share the same filters. One difference matters though: **the map hides finished tasks** until you explicitly filter by status. It shows the four unfinished statuses, because a map cluttered with work already done is useless in the field. The list shows whatever the filter asks for.

#### The marker on the map

A task marker is always made of three things:

- **a white teardrop** — the shape that points at the ground;
- **a pale grey disc** inside it;
- **the task type's icon**, in dark blue, at the centre.

Here's the thing to remember: **the marker only encodes the type.** Not the priority, not the status, not who it's assigned to. A critical task and a minor one of the same type look exactly alike. For severity, open the task or switch to the list.

A **segment task** — one covering a stretch of trail rather than a point — carries the *Segment* icon instead of a type icon.

Three behaviours worth knowing:

- **Nothing is clustered.** Many apps merge nearby markers into a counter; Sentinel doesn't. Twenty tasks in one spot are twenty stacked markers. Zoom in to separate them.
- **Nothing is hidden either.** Two overlapping markers are both still drawn — one covers the other, but neither disappears.
- **The touch area is bigger than the drawing.** You don't have to aim precisely; the phone buzzes when the task is caught.

**A structure is not a task.** On the same map, a structure is drawn as a **filled circle ringed in white**. The shape alone tells them apart: teardrop = something to do, circle = a structure to watch.

The **trail's track** is painted in its difficulty colour, and the pill at the top left recalls its name with its rating symbol. See [difficulties](/en/docs/manage-trail-difficulties).

#### Tap a trail to isolate it

_On the left, one trail filtered. On the right, several._
1. The chosen trail thickens and takes on a halo in its own colour.
2. The others recede, names faded — but nothing disappears.
3. The "Filtered on" pill names the trail you kept.
4. As soon as there are several: a quieter capsule, the ratings in play and the count.

That track is also a button. **Tap a trail on the map** and the map keeps only that trail's tasks — it's exactly the "Trail" filter, set without opening the panel. The phone buzzes briefly when the track is caught. Aim for the line: unlike markers, a trail's touch area is narrow.

Three things change at once:

- **The chosen trail stands out**: its track thickens and takes on a halo in its own colour.
- **The others recede, without vanishing.** They stay drawn in the background, very pale, their names faded. You keep the shape of the network in view without losing the one you picked.
- **A "Filtered on" pill** appears at the top left, below "You are in", naming the trail. That's what answers you when you're zoomed in and the chosen track no longer fits on screen.

Tap the same trail again to go back to the full view. You can also stack several: each tap adds a trail.

**The corner of the screen never fills up with pills.** As soon as more than one trail is filtered, the display changes character: instead of a second white pill, a **quieter dark capsule** slides in below the first. It names no one — it shows the **symbols of the difficulties present in your filter**, then the count: "10 trails filtered". You see at a glance which ratings are in play, and the capsule stays the same size whether you filter two trails or fifteen.

The difference in treatment is deliberate: the name of the trail you're walking is foreground information, the presence of a filter is not. The two shouldn't look alike.

**And when the trail you filter is the very one you're walking**, the "You are in" pill steps aside: all that's left is "Filtered on / \<the trail\>". It's the same name either way, and your position is already drawn on that track — writing it twice would teach you nothing.

**It's the same filter as the panel's.** What you set with your finger on the map shows up under "Trail" in the filters, and the reverse holds too: filtering by five trails from the panel brings those five tracks forward on the map. See [filter tasks in depth](/en/docs/use-advanced-filters).

#### The recenter button: three modes

Bottom left of the map, a round button. It doesn't just "go back to my position": **it has three states**, and you move between them by tapping. There's no menu — each tap advances one step, and the third brings you back to the first.

_The button's three states._
1. Overview: the button is dark.
2. Centred: it turns blue.
3. Follow: it pulses.

**1. Overview** — the starting state. The map is framed on **your whole place**: every trail fits on screen. The button is dark. It's the "how does the network look" view.

**2. Centred** — one tap. The map flies to your position and zooms to sector level. The button turns **blue**. It's a **one-shot** recentre: if you then walk, the map doesn't follow. You're free to move it around.

**3. Follow** — two taps. The map zooms closer and **stays locked to you**: it re-frames every time your position moves. The button pulses — two white rings spreading out in a loop. This is the mode that changes the most, and it's the next section.

A third tap returns to the overview.

#### Follow mode: a scan of what's around you

Follow mode doesn't just follow you. **It changes what the map shows.**

_Follow mode, running._
1. The 55-metre disc around you.
2. Only tasks inside the disc are drawn.
3. The button, in follow mode.

A **translucent blue disc with a 55-metre radius** appears around your position, and the map only shows **what's inside it**: the tasks and structures within that radius, nothing else. Everything further out disappears for the duration of the scan.

Three things to know, and the second one surprises people:

- **The scan ignores your filters.** It shows **every unfinished task** in range — all four active statuses — whatever type, trail or assignee you had filtered on. That's deliberate: when you're looking for what there is to do where you're standing, you don't want to miss a task because a filter was still on.
- **Finished tasks stay hidden**, as everywhere else on the map.
- **It works with no coverage**, from what the phone already has cached — see [working offline](/en/docs/work-offline).

**What it's actually for.** You arrive in a sector and can't remember what was reported there. Two taps, and you have the answer to within fifty-five metres, without filtering or searching. It's the move that replaces "hang on, let me check the list".

**When to leave it.** Follow re-frames the map constantly: you can't look elsewhere, it pulls you back. As soon as you want to explore around, one tap gives you control again.

#### The list screen

_The list view._
1. The same header as the map: the place, and the task-type filters.
2. A project: folder icon, task count, progress bar.
3. A task folder: gold icon, its name, and the arrow that opens its contents.
4. The status group, on a hairline.

**The header doesn't change between views.** The place pill and the row of type filters sit above the map and the list alike — it's the same band, literally the same component. Filter a type on the map and it's filtered in the list too, and the other way round.

**At the top: projects.** If any projects match the filter they come before the tasks, under a **Projects** heading. Each is a plain row — not a card: a **folder icon**, the name, the task count and a small progress bar. A project on hold is marked *On hold* and its icon fades.

**Then: folders.** If your place has [task folders](/en/docs/manage-tasks), they appear under a **Folders** heading, between the projects and the tasks. One row per folder: its name, a gold folder icon, and an arrow. Tap it and you open **the folder's contents** — the same tasks, narrowed to that folder.

Those contents come in **three forms**, exactly like a project's: a tab bar at the bottom of the screen switches between the **map**, the **list** and the **kanban**. The map frames itself on the folder's tasks; the kanban is the one you know from [my planning](/en/docs/plan-member-work), one column per status and drag-and-drop to move work along. The app remembers the mode **folder by folder**: view "May 12 work party" on the map and "Before opening day" as a kanban, and each reopens in its own mode. The kanban goes further and also remembers **the column** you were on.

Three things to know about these folders:

- They show up **even with no network**: folders are part of the data installed on the phone, like the trails — see [installed data](/en/docs/installed-data).
- A folder does **not** remove its tasks from the list: the same task stays visible further down, in its status group. A folder is a shortcut to a subset, not a drawer that hides things.
- A folder's contents follow the same rules as the Field list — no to-do task without a position, no task already filed in a project — but they **ignore the filters** in the top bar: you see the whole folder. All three modes show exactly the same tasks, presented differently.

Don't mix up the two notions: projects and folders carry the same folder icon, but **a folder's is gold** where a project's is grey. And a project shows a task count and a progress bar, whereas a folder shows only its name.

**Then: tasks**, under a **Tasks** heading, cut into status groups. Each group is announced by a pill centred on a hairline — which also carries a folder icon, because the same component serves both. The pill's text is the **status**, not a folder name.

#### A task's card

A task isn't a text row: it gets a **card with its own map thumbnail** — the actual spot, drawn, rather than a trail name to decode.

_A task in the list, close up._
1. The thumbnail: the position, the trail's track, the type's marker.
2. The priority tag, bottom right.
3. The assignee's avatar, top right.

Top to bottom:

| Element | What it tells you |
|---|---|
| **The title** | The task's name |
| **The date** | When it was created — "Today at 8:12 AM", "Yesterday at…", then the full date |
| **The sync badge** | Only appears while the task hasn't reached the server yet — see [working offline](/en/docs/work-offline) |
| **The map thumbnail** | The real position, the trail's track in its difficulty colour, and the type's marker |
| **The trail pill** | Bottom left, overhanging: the difficulty symbol and the name |
| **The priority tag** | Bottom right, overhanging, coloured by priority |
| **The avatar** | Top right: the person or group assigned. **Absent when nobody is assigned** |
| **The annotation counter** | Top left, when there are map annotations — see [annotating on the map](/en/docs/annotate-on-the-map) |
| **The description** | Two lines at most, then cut |

Those four badges deliberately overhang the thumbnail's corners: they have to stay readable without eating the map.

**What the list card adds over the marker**: priority, assignee, sync state and description. That's why the list is the right view for deciding what to do first, and the map the right view for deciding which way to walk.

#### How the list is ordered

You don't choose the sort: it's fixed, and it follows field logic.

**Projects first, then tasks.** If projects match the filter they come first under a **Projects** heading, then tasks under a **Tasks** heading.

**Tasks are grouped by status**, in this order: New, Ready, In Progress, On Hold, Done. Each group is announced by a pill centred on a hairline.

**Inside a group, priority rules**: Critical, High, Medium, Low. At equal priority, the **most recent first**.

In other words, the first card in the list is always the most recently reported, most serious task among those nobody has picked up. That's deliberate — it's the morning question.

An empty group doesn't appear — you won't see an "On Hold" heading if nothing is on hold.

#### Three tips

**Don't look for severity on the map.** It isn't there. If you need to sort by priority, switch to the list — one tap, top right.

**One marker can hide several.** In a dense area, zoom in before concluding there's only one task.

**A card with no avatar is a task with no owner.** It's the fastest thing to read in the whole list, and often the most useful before a work day.

### Installed data: what the phone keeps in reserve

URL: https://trail-sentinel.com/en/docs/installed-data
Applies to: mobile

For a trail to show up at the bottom of a valley with no signal, its track has to be **already on the phone**. Same for task types, difficulty ratings, folders.

That's what **installed data** is for: seven reference sets Sentinel downloads and keeps locally. You normally have nothing to do here — this screen exists for the times you want to check, or to force.

**Where:** mobile app, the **⚙** button at the top of the Field view → **Installed Data**.

#### What gets installed

_The Installed Data screen._
1. An up-to-date set: the installed version, in grey.
2. An update available: the text turns gold, and so does the button.
3. A download in progress, with its progress bar.

Seven sets, always the same:

| Set | What it holds |
|---|---|
| **Trail** | The full track of every trail — the biggest one, and the most useful offline |
| **Structures** | The inventory of built works and their positions |
| **Structure types** | The types and their inspection questionnaire, with the numbering rules |
| **Task Types** | Your custom types and the built-in ones, with their icons |
| **Trail Difficulties** | The levels, their symbol and their colour |
| **Structure Folders** | The filing folders for structures |
| **Task Folders** | The filing folders for tasks |

These are **reference sets**, not your work. Your tasks, photos and reports aren't here — they travel another way, described in [working offline](/en/docs/work-offline).

#### Reading a row

Each row carries a state, and the text under the name tells you which:

- **"Version: 1.4.0"** in grey — the set is installed and current. Nothing to do.
- **"New version available: 2.1.0"** in gold — the server has a newer one. The download button turns **gold** too: it's the screen's only visual signal, and it means "there's something to take".
- **"Data not installed"** in grey — this set has never come down to this phone.

During a download the button becomes a spinner and a **progress bar** appears under the text. The files are compressed: a two-hundred-trail network comes down in seconds on a decent connection.

#### You normally have nothing to do

This is the important part, and it's why many people never open this screen.

**Sentinel updates these sets on its own.** When a change is made from the web — by a colleague or by you, on your computer — a phone with the app open picks it up within seconds, untouched. With the app closed, a background task takes over: it regularly compares the phone's versions against the server's and installs whatever changed. Either way, there is nothing to do.

So this screen is good for **two things only**:

**Checking.** You're heading into a sector with no coverage and want to be sure the trails are current. One glance: if everything is grey, you're set.

**Forcing.** A colleague just created a trail and you're leaving in ten minutes. Tap the button on the **Trail** row: the version comes down right away, without waiting for the next automatic pass.

Pull the list down to refresh it if you want to re-check against the server.

#### When it doesn't work

**"Unable to download data."** You have no coverage, or the server didn't answer. The set stays as it was — nothing is broken, the old version keeps working. Try again with signal.

**"Update in progress, try again later."** The server is rebuilding that set and the file isn't ready yet. It passes: wait a minute and tap again.

**A set that stays "not installed".** Most often this place simply has none of that thing — no structure folders, for instance. There's nothing to download, and it isn't a problem.

#### Three things to know

**Data is per place.** If you work for two organizations, each place has its own sets, installed separately. Switching places doesn't reload everything.

**A stale set loses you nothing.** You're simply missing what was added since: a trail created yesterday won't appear on your map until the **Trail** set moves up a version.

**Before a long outing, install everything.** It's thirty seconds of connection in the parking lot, and it decides what you'll see on the map for the next six hours.

### Geolocation settings: accuracy against battery

URL: https://trail-sentinel.com/en/docs/geolocation-settings
Applies to: mobile

In the field everything starts from your position: the task you create, the trail it attaches to, the scan of what's around you. This screen is the only place where you can **check that the GPS is working** and **trade accuracy against battery life**.

**Where:** mobile app, the **⚙** button at the top of the Field view → **Geolocalisation settings**.

#### The screen

_The geolocation settings._
1. Tracking status, with the time and position of the last reading.
2. The accuracy level, and the battery warning.

Two blocks, nothing else.

**At the top, tracking status.** If you've never allowed location, a single button — **Active location tracking** — asks for permission. On Android an explanation screen comes first.

In practice you were already asked when the app started, on the welcome screen described in [the first launch](/en/docs/first-sign-in). This screen is the fallback: where you come back if you refused, or to check that tracking really is running.

Once allowed, the button gives way to three lines:

| Line | What it tells you |
|---|---|
| **Tracking position running** | Tracking is live. If it reads **Tracking position stopped**, the GPS isn't reporting any more |
| **Last update** | When the last position came in |
| **Last position** | Your coordinates, to four decimals — about eleven metres |

If something is blocking, an orange message appears under those lines.

**This is your first diagnostic move.** When a task lands in the wrong place, or the proximity scan finds nothing, open this screen: either the last update is twenty minutes old, or the position is plainly wrong — and you know the problem is the GPS, not Sentinel.

#### GPS accuracy

Five levels, from thriftiest to most precise: **Lowest**, **Low**, **Balanced**, **High**, **Highest**. The default is **High**.

The setting is saved **per place**: if you work for two organizations, each keeps its own.

##### What it really changes

This is the part the screen doesn't explain, and the only one that matters.

When you create a task, Sentinel looks for the nearest trail. It doesn't search a fixed radius: **it starts from the accuracy the GPS reports**. The starting radius is twice that accuracy, with a floor of twenty metres and a ceiling of one hundred.

- A position accurate to **5 metres** opens a **20-metre** search — the floor.
- A position accurate to **30 metres** opens a **60-metre** search.

If nothing is found the radius widens in three steps, up to two hundred metres. Put differently: **poor accuracy doesn't stop you finding a trail — it makes you find too many.** Where three trails cross, a sixty-metre radius catches all three, and Sentinel has to ask you which one. With good accuracy there's only one, and the question never comes up.

That's exactly what the screen's own text means by "a more precise detection of the trails near you".

##### The cost

It's written in bold on the screen, and it's real: **more accuracy, more battery.** The GPS polls satellites more often and for longer.

A trade-off that holds up:

- **High** — the default, and the right choice almost always. Precise enough to attach the right trail, without draining the phone.
- **Highest** — for a day of precise survey work, under dense canopy, or when you're mapping. Bring a power bank.
- **Balanced** or below — for a long day where you read more than you create. Your tasks will be attached more loosely.

**Don't go below Balanced if you're creating tasks.** A position accurate to a hundred metres triggers a two-hundred-metre search, and the suggested trail will often be the wrong one.

#### Three things to know

**Tracking only moves when you do.** The position is only re-recorded past **three metres** of movement. A "last update" from ten minutes ago while you're sitting down is therefore not a sign of failure.

**Reported accuracy isn't real accuracy.** Under dense canopy or at the bottom of a valley, your phone may claim five metres and be thirty out. That's another reason checking the suggested position stays worthwhile — see [reporting a problem from the map](/en/docs/report-a-problem-from-the-map).

**Refusing location doesn't block the app.** You can still read and edit; you lose creation at your position, automatic trail attachment and the proximity scan. A reminder then appears at the bottom of the map, with a **Turn on location** button: it shows the same explanation as the first launch, then asks for the permission again.

**After a refusal, the app can no longer ask you again.** That's a phone rule, not a Sentinel choice: once location is denied, only a trip through the system settings can turn it back on. That's what the reminder at the bottom of the map is for.

### The Tasks section: map, kanban, folders

URL: https://trail-sentinel.com/en/docs/manage-tasks
Applies to: web

The **Tasks** section is the workshop of the web app: it's where you look at what there is to do, organise it, and hand it out.

It comes down to two view modes, a heavily equipped list, and a toolbar shared by both.

**Where:** left navigation bar, under **General** → **Tasks**.

#### The two view modes

_The Tasks section in kanban view._
1. The Tasks section, in the left navigation bar.
2. The filters: assignee, task type, and advanced filters.
3. The create button, to add a task without going through the field.

The toolbar's switcher flips between two views:

**The map**, paired with a list on the left. That's the geography view: where the problems are, which ones cluster, how much driving that means.

**The kanban**, without the map. That's the progress view: one column per status, one card per task, and drag-and-drop to move things along. Hover a column header and a **+** appears: it creates a task that starts out **with that column's status** — and in the selected folder, if there is one. Its menu also offers to start [from a photo](/en/docs/create-a-task-from-a-photo). If your place has **folders**, they take up a column to the left of the board and let you show one folder at a time — see [folders](#folders).

Both **share the same filters**: whatever you filter on the kanban stays filtered when you switch to the map. The **Assigned to** filter lists your [groups](/en/docs/use-groups) alongside your members: filtering on "North crew" shows everything handed to that group.

Each view has **its own search field**: above the list in map view, above the board in kanban view. The kanban one searches the task name, its type, its trail, its folder, its project, its assignee — member or group — and its description — which is what the grey hint text in the field spells out. It combines with everything else: to search inside one folder, select that folder first.

#### The toolbar

It sits on the right of the header and is **identical in both views**.

_The section header, with the ⋯ menu open._
1. The view switcher: map or kanban.
2. The two quick filters, then the advanced filter and the ✕.
3. The ⋯ menu and its three entries.

Left to right:

| Control | What it does |
|---|---|
| The view switcher | Map or kanban |
| **Show all tasks** | Switches to the four unfinished statuses — the "show me what's left" shortcut |
| **Assigned to** and **Task type** | Two quick filters, the most used ones |
| **Advanced filter** | Opens the full panel — see [filters](/en/docs/use-advanced-filters) |
| The **✕** | Only appears when a filter is active, and resets everything |
| The **⋯** menu | Create a project from the filter, export to Excel, batch edit |

**On a narrow screen.** The bar never overflows: when room runs short, it puts its controls away **one at a time**, starting with the rightmost one. The control that disappears moves into a sliders button that opens the same list, and the active-filter count stays visible on it. As long as there is room for the others, they stay as buttons. Widen the window and they come back in reverse order.

The **Create project** entry in the ⋯ menu stays greyed out until a filter is active: it turns a filter's result into a project, so it needs a filter.

The other two entries — **Export Excel** and **Edit several tasks** — each open a dialog, and that's what the next two sections are about. If you can't see them, it's a matter of rights: each has its own.

#### Export to Excel

**⋯** menu → **Export Excel**. You get an `.xlsx` file of your tasks, to open in Excel, Google Sheets or Numbers.

_The export dialog, once the tasks are filtered._
1. The dialog's filter bar, independent from the section's.
2. The button showing how many tasks will be exported.

The dialog has **its own filter bar**, independent from the section's. That's deliberate: you can export a batch of tasks without undoing the filter you were working with. It starts empty every time you open it.

Until a filter is set, the dialog shows **Select your tasks** and the button stays inactive. That's the principle: **filter first, export second.** As soon as a filter is set, the matching tasks appear as a preview and the button lights up with their count — **Export 12 tasks**. You see exactly what will end up in the file before you click.

The export is **built by the server**, not by your browser: after the click, Sentinel prepares the file in the background and hands it over when it's ready. Expect a few seconds for a normal export. A very large one can take up to a minute and a half — leave the dialog open while it works.

The entry only appears if your role has the **Export** right.

#### Edit several tasks at once

**⋯** menu → **Edit several tasks**. This dialog applies one change to a whole batch: moving thirty tasks to *Ready*, assigning an entire trail to a group, attaching a batch to a project.

_The 'Edit several tasks' dialog._
1. The dialog's filter bar, which determines the batch.
2. Each property's switch: only the ones turned on will be changed.
3. The switch that notifies the members concerned.

The dialog follows the same two-step logic as the export, with **its own filter bar**. One difference: the edit form **only appears once tasks are found**. As long as the filter returns nothing, the dialog stays narrow and shows only the invitation to filter — you can't prepare a change that would apply to no one.

Once the batch is set, the right-hand column offers four properties, **each behind a switch**:

| Property | What you can do |
|---|---|
| **Status** | Move the whole batch into a kanban column |
| **Priority** | Make the priority uniform |
| **Assignee** | Hand the batch to a person or a group — or **leave the field empty to unassign** |
| **Project** | Attach the batch to a project — or **leave it empty to remove it from one** |

The switch is the important part: **only the properties you turn on are touched.** Everything else on each task is left alone. So you can change the status of thirty tasks without touching who's responsible for them, or change several properties at once by turning them on together.

**Telling the team.** A last switch, **Send a notification**, is off by default. Turned on, it sends a push notification and an email to the members **subscribed to the attributes you're changing** — the people who asked to be told when a task changes owner, for instance. Save it for changes that call for action; a big end-of-season tidy-up doesn't need to wake up thirty phones. See [notification settings](/en/docs/notification-settings).

**The confirmation.** The final button sums up the task count, then a confirmation lists the exact changes before applying them. Read it: **a batch edit cannot be undone.** There's no undo — you can only run another edit in the opposite direction, and that won't restore the individual values you lost if they weren't all identical to begin with.

The work then runs server-side; on a very large batch it can take a few minutes. The changes reach the team's phones as they land.

This entry requires the **Batch edit** right in read and write, which is separate from the export right.

#### The list and its groupings

The list appears **to the left of the map**, in map view only. Its own buttons are in the small grey bar above the search field.

_The List panel._
1. Group by status or by type, and the nesting by trail.
2. The button that creates a folder.
3. The map button, active on that group.

It isn't a plain enumeration: it **groups**, and that's what makes it readable on a busy network.

Two settings combine:

- a **main grouping**: by **status** or by **type**;
- a **Group by trail** toggle, which **nests** the first one under trails.

That gives four readings. "By status" answers "where does the work stand"; "by type, grouped by trail" answers "what's there to do on La Coulée, and of what kind".

Every group header carries its **count**. Tasks with no trail are gathered under **No trail** rather than hidden.

The search field filters the list as you type. It searches **task names** and **folder names**: searching a folder brings up everything inside it.

#### Folders

Folders are your own filing. Unlike the trail or the status, which describe the task, a folder describes **your intent**: "May 12 work day", "Before opening", "Waiting on the permit".

##### From the list, in map view

**Create.** The folder button, the third one in the list's bar — marker ② on the illustration above. A name, and it's done.

**On a brand-new place**, that button isn't there yet: as long as no task exists, the list is replaced by a welcome block explaining what a task is. That block offers both moves — **Create a task** and **Create folder** — so you can set up your folders first and fill them later. As soon as a first folder exists, the normal list takes over and shows it, still empty.

**File tasks into one.** Drag a task onto the folder's header. To move several at once, **Shift + click** selects them, then a single drag moves them all.

**Rename or delete.** The ⋯ menu on the folder's header.

##### From the column, in kanban view

Your folders form a **column to the left of the board**.

_The kanban view with its folder column._
1. The folder column: **All tasks** on top, then one row per folder.
2. The **+** that creates a folder, and the **⋯** menu that appears when you hover a row.
3. The board's search field.
4. The folder name, at the bottom of the card.

**Create, rename, delete.** The **+** at the top of the column creates a folder. Hover a folder and a **⋯** menu appears, with *Rename* and *Delete*.

**File tasks into one.** Drag a card onto a folder in the column and it changes folder. **Shift + click** selects several cards — they turn gold and get a check mark — and a single drag moves them all. To **take a task out** of its folder, drop it on **All tasks** at the top of the column; a task that has no folder to begin with is not accepted there. A confirmation message shows up every time, because nothing visibly moves on the board when you are looking at all tasks.

**Showing one folder only.** Click a folder and the board shows only its tasks. **All tasks** brings everything back. One folder at a time.

This is a **view choice, not a filter**: the [*Advanced filter*](/en/docs/use-advanced-filters) button does not light up, the ✕ does not appear, and your filters stay exactly as you left them. What this view does do is **remember you**: the mode you picked and the folder you opened are kept **for that place**, even if you close the browser. You come back where you left off. Each place keeps its own.

**Seeing where a task is filed.** While you are looking at **All tasks**, every card carries its folder name at the bottom — marker ④. As soon as you step into a folder, the label disappears: it would no longer tell you anything new.

**A task created while a folder is open goes into that folder.** The form's **Folder** field arrives pre-filled. Nothing stops you from changing it or clearing it before saving.

If the place has no folders at all, the column does not appear: the board takes the full width — and the first folder is then created from the list.

One important point: **deleting a folder does not delete the tasks inside it.** They simply lose their folder and stay in the list as before. A folder is a label, not a container.

#### Showing a group on the map

This is the least visible button and one of the most useful. Hover a group's header and, **on the right, its count is replaced by a small map icon**.

Click it and **the map shows only that group's tasks**. The button then stays lit in gold to remind you a projection is on — that's marker ③ on the illustration above, on the "May 12 work day" folder.

Three things to know:

- **It isn't a filter.** Your filters don't move, the list doesn't move — only the map narrows. It's a spotlight, not a sieve.
- **Selections add up.** Light two folders and the map shows both. Click again to switch one off.
- The **✕** that clears filters also switches these projections off.

The typical use: the day before a work day, you light up that day's folder and look at the map to decide where to start.

#### Creating a task from the map

The fastest way to create a task on the web isn't the button: it's a **right-click on the map**, at the exact spot of the problem.

_The right-click menu._
1. The trail it recognised, with its difficulty colour.
2. The entry that opens the form, already positioned.

A menu opens at the click point with a single entry — **Create a task here** — and the form opens with the **position already filled in**.

**Sentinel snaps your click to the nearest trail.** If a trail is within reach, two things happen: the position is **pulled onto the line** instead of being left beside it, and the **trail is pre-filled** in the form. The menu confirms it by showing the trail's name, with the colour dot of its difficulty.

How far that snap reaches **depends on the zoom**: about ten metres when you're zoomed in, up to a hundred and fifty when you're far out. That's deliberate — from far away you don't aim to the metre. If no trail is within reach, the point is taken as-is and the task stays off-trail.

Three things to know:

- Right-click only responds in the **Tasks** and **Structures** sections. On the dashboard home it does nothing.
- In **Structures**, the same gesture offers **Create a structure here**.
- You need the matching create right, otherwise no menu appears.

The menu closes if you move the map, press **Esc**, or click elsewhere.

#### Moving a task forward

This all happens in **kanban view** — the first illustration on this page.

**Change the status.** Drag a card from one column to another. The change is immediate for the whole team, including phones already open on the map.

**Open the details.** Click a card to open the side panel: photos, trail, priority, assignee, time logged and discussion.

**Assign it.** Pick a person or a group. The assignee finds the task in their planning, on web and on mobile.

#### Filtering without losing the thread

Filters are applied server-side: the counter at the top of each column always reflects what you filtered, not just what happens to be loaded on screen.

A common pattern: filter by trail before a work day, then bulk-assign the remaining tasks to the group that will be on site.

### Create a task from a photo

URL: https://trail-sentinel.com/en/docs/create-a-task-from-a-photo
Applies to: web

Someone sends you a photo of a problem on a trail without telling you exactly where it is. If the photo was taken with location services on, Sentinel can find the spot on its own and suggest the right trail.

It is the same task creation as usual — you simply start from the photo instead of the map.

**Where:** left navigation bar, under **General** → **Tasks**, then the chevron on the **Create a task** button.

#### Opening the flow

In the **Tasks** section, the create button has two actions. Clicking it directly starts the normal flow; the chevron opens a menu.

_The create button and its dropdown menu._
1. Clicking the button directly starts the normal flow, the one that begins with the map.
2. The chevron opens the menu. Choose "Task from an image".

The creation panel opens on the right, on the **Upload image** step.

#### Uploading the photo

_The upload step, before a photo is chosen._
1. Drag and drop the photo onto the area, or click to browse your files.
2. The back arrow and the cross close the panel or step back, without losing anything.

Common camera and phone formats are accepted, including **HEIC** from iPhones. One photo at a time: this is the one used to locate the task. You can add more later, in the form.

#### What Sentinel reads from the photo

As soon as the photo loads, Sentinel analyses it and shows the result.

_The analysis result: location found and trails detected._
1. The uploaded photo. Click it to enlarge; the cross on the right removes it.
2. The analysis result: the GPS location read from the photo, its coordinates, and how many trails were found around it.
3. "Continue" moves to the next step.

Sentinel looks for trails within **100 metres** of the photo's location, with a **20-metre** tolerance either side of the path. Three cases:

**One trail found.** Sentinel keeps that trail and the position projected onto its path. The map placement step is skipped: you go straight to the form.

**Several trails found.** The next step shows a map with a photo marker where the picture was taken and one marker per candidate trail. You pick the right one. If none fits, the **Place on map** button hands control back so you can point yourself.

**No trail, or no location in the photo.** You place the marker yourself on the map. If the photo did have a location, the map is already centred on it and a photo marker gives you a reference point.

**Why a photo sometimes has no location:** location services were off on the device, or the photo went through a messaging app that strips metadata while compressing it. In that case, ask for the original file — by email or file sharing rather than by message.

#### Choose the type, then fill in

The next step is the **task type**: fallen tree, erosion, broken plank, and any types you have added yourself. "Segment" is not offered here — a photo gives a point, not a length of trail. For a segment task, use the normal flow.

Then comes the usual form: name, description, priority, status, assignee, project, estimated time, materials. **The photo is already attached** — no need to upload it a second time. It goes to the server once the task is created.

#### Good to know

- You can step back at any time with the arrow at the top: the photo stays in memory, and a **Continue** button lets you pick up where you left off.
- Removing the photo with the cross also clears the location and the detected trails. You start again from an empty drop area.
- The coordinates shown are the photo's, not the task's. The task's final position is the one on the trail you kept, or the point you placed.

### Filter tasks in depth

URL: https://trail-sentinel.com/en/docs/use-advanced-filters
Applies to: web, mobile

The quick filters in the toolbar answer simple questions: who, what type. **Advanced filters** are for when the question combines several — "critical tasks still open on La Coulée, created this month".

The filter applies everywhere at once: the list, the kanban and the map all show the same subset. The counter at the top of each column reflects the filter, not just what happens to be loaded on screen.

**Where:** the **Advanced filter** button in the **Tasks** toolbar. On mobile, the filter icon on the **Field** view.

#### On the web

The **Advanced filter** button in the toolbar opens a panel on the right.

_The filter panel, with three criteria active._
1. Each section collapses. The badge shows how many criteria are active inside it.
2. The counter at the top totals every active criterion, across all sections.
3. Closed sections are not inactive — open them to see what they hold.
4. Nothing moves until you click "Apply filters".

This is what surprises people most: **your choices are not applied as you go**. You tick what you want, then you apply. If you close the panel with unapplied choices, Sentinel asks rather than losing them.

The three buttons at the bottom do different things:

| Button | Effect |
|---|---|
| **Reset** | Clears every criterion in the panel |
| **Cancel** | Closes without changing the filters currently in effect |
| **Apply filters** | Applies your selection. Disabled until something changes |

##### The nine dimensions

**Status** and **Priority** show as pills: one tap turns a value on, another turns it off. Values stack — "Ready" plus "In Progress" gives you both.

**Type** is a grid of your place's task types, including the ones you created yourself.

**Date** first asks *which* date: creation or completion. You then pick a range, with shortcuts (today, yesterday, this week…).

**Trail**, **Creator**, **Assigned to** and **Project** are searchable lists. When a list is long, type the first few letters instead of scrolling.

**Folder** takes **one value at a time**, unlike the others. It is the same filter as the kanban's folder column: what you tick here shows up there, and the other way round. The section only appears if your place has folders.

##### Clearing everything

As soon as one filter is active, an **×** button appears in the toolbar, between "Advanced filter" and the "…" menu. It resets everything — including the "Assigned to" and "Task type" quick filters, which do not live in the panel.

#### On mobile

The funnel icon at the top right of the Field view opens the same set of filters, full screen.

_The mobile filter screen._
1. Date works differently from the other criteria: a switch turns it on, then you pick an operator and a date.
2. The green badge counts the active criteria in that section.
3. An active criterion is recognisable by its darker border and grey fill.
4. The apply button only appears when there is something to apply.

**Creation Date** is the only section driven by a switch. Once it is on, the first field picks the operator — before or after — and the second the reference date. Tapping the date rolls out a wheel picker below the field.

For everything else, same logic as on the web: you compose first, then you apply. The sections are the same, plus a **Structure** section specific to mobile.

The filter stays on when you leave the screen. If the map looks empty when you come back, check the funnel — it is almost always a forgotten filter.

#### Two habits worth having

**Prepping a work day.** Filter by trail and by "Ready" status, then assign the result to the group that will be on site. The kanban and the map then show exactly the day's list.

**Turning a filter into a project.** Once a filter is applied on the web, the toolbar's "…" menu offers to create a project from those tasks. It is faster than picking them one by one.

### Projects: grouping tasks that belong together

URL: https://trail-sentinel.com/en/docs/use-projects
Applies to: web, mobile

A task answers "what to do". A **project** answers "where do we stand".

It's a container: you put tasks that belong together into it — the season opening, a sector rebuild, a grant to account for — and Sentinel computes the progress, the time spent and the workload split from whatever is inside.

A project isn't a category: a task belongs to **exactly one project at a time**, or to none.

**Where:** left navigation bar, under **General** → **Projects**.

#### The list

_The project list._
1. Projects are grouped by status, in their life-cycle order.
2. The gauge shows progress — the completed task count and the percentage.
3. The options button carries a dot when a filter is active.

Projects are **grouped by status**, always in the same order: New, Ready, In progress, On hold, Done. Within a group they're sorted by name.

Two things to know about what you're seeing:

**Done projects are hidden by default.** That's the setting behind the options button next to the search. Turn it on to bring them back — the gold dot reminds you a filter is in place.

**The list only shows the current activity.** As everywhere else in Sentinel, switching activity changes the list.

Search matches on the name and runs on the server: it waits until you've stopped typing, and it searches across every project, including done ones if the option is on.

#### The status computes itself

This is the most important point in the section, and the one that surprises most: **you don't choose a project's status**. It's recomputed every time one of its tasks moves.

| The project becomes | When |
|---|---|
| **New** | No task is ready, in progress or done |
| **Ready** | At least one task is ready or done, none in progress |
| **In progress** | At least one task is in progress |
| **Done** | **Every** task is done |

There's no "95 % is close enough": moving to Done requires the last task to be done. A project at 24 tasks out of 25 stays In progress.

**The one exception is "On hold".** It's the only status you set by hand, and it **freezes** the calculation: while a project is on hold, its tasks can move without its status changing. That's what you want for a suspended job — waiting on a permit, a budget, the thaw.

One detail to know: **the "Set this project on hold" switch lives in the mobile app**, in the project's edit page. On the web, the page preserves the state without letting you change it.

To take a project off hold, turn the switch off: the status recomputes immediately from the tasks.

#### Following a project

A project opens on three views, switched from the header.

_A project's header._
1. The circle shows progress, and beside it time spent over time estimated.
2. The three views: kanban, map, statistics.
3. The menu holds edit, Excel export and delete.

**The kanban** is the default view: the project's tasks in their status columns, dragged from one to the next. It's also where you **add existing tasks** to the project, by dragging them in from the side panel.

**The map** shows those same tasks at their real positions. It's the view that answers "is my job grouped, or spread over ten kilometres?" — which is to say "how much driving will this cost".

**The statistics** are the accountability view.

The assignee filter in the header applies to all three views at once.

##### Time

The `42h / 60h` in the header is **time spent over time estimated**. Both come from the tasks: the estimate is the sum of the estimates, the spent is the sum of the time entries. You don't estimate a project, you estimate its tasks.

A project with no estimate at all doesn't show that ratio.

#### The statistics

_A project's Statistics view._
1. The four headline numbers, including unassigned tasks.
2. How the tasks break down by status.

Five charts, all computed on the project's tasks:

- **by status** — where the work stands;
- **by priority** — is what's left urgent or incidental;
- **by type** — the nature of the work, useful for a grant application;
- **workload by assignee** — who carries what, by status;
- **hours per user** — the time actually logged per person.

The **Unassigned tasks** figure in the header is the one to look at first when a job starts: that's the work nobody has picked up yet.

##### The Excel export

The ⋯ menu offers **Export project**: an Excel file of every task in the project. That's the format funders and end-of-season reports expect.

The entry is greyed out while the project has no tasks.

#### In the field

Mobile isn't for building a project, it's for following it and working on it.

_A project on mobile._
1. Two gauges: tasks completed, then hours worked against hours estimated.
2. The bottom bar switches between the three views.

The page shows the project's name, the two gauges, then its tasks. The bottom bar gives you the **same three views as on the web** — map, list and kanban — and the app **remembers the view project by project**: the one you track as a kanban reopens as a kanban, the one you read on the map reopens on the map. The kanban also remembers **the column** you were on.

You can create and edit a project from mobile — and it's the only place you can put one on hold.

A project's page is **readable offline** if you've opened it before: it's read back from the cache when the network is missing.

#### Who can do what

Projects fall under the **Projects** right in the activity manager.

- With **read**: see the list, open a project, browse its three views and export.
- With **read and write**: create, rename, assign a lead, add or remove tasks, delete.

So read access is enough to produce a report — deliberately: someone who has to account for a grant doesn't need to be able to touch the job. See [roles](/en/docs/understand-roles).

#### Three pieces of advice

**A project must have an end.** "2026 season opening" finishes; "Routine maintenance" never does, and its progress means nothing. For continuous work, [filters](/en/docs/use-advanced-filters) do the job better.

**Name a lead.** It's the column everyone reads in the list, and the only one that says who to ask.

**Put it on hold rather than letting it drift.** A blocked job that stays "In progress" pollutes the list; on hold, it leaves the noise without disappearing.

### The dashboard: reading the network's state in thirty seconds

URL: https://trail-sentinel.com/en/docs/read-the-dashboard
Applies to: web

The dashboard is the web app's first page. It isn't for working: it's for **knowing where things stand** before deciding what to do with your week.

It has three layers — five indicators at the top, a series of charts in the middle, a per-trail table at the bottom — and one date range that drives all of it.

**Where:** left navigation bar, under **General** → **Dashboard**. It's the page that opens when you log in.

#### The principle: one snapshot a day

This is the point to understand before anything else, because it explains every surprise.

The dashboard **doesn't read your data live**. Every night Sentinel compiles a **snapshot of the day that just ended** — a frozen picture — and it's that series of snapshots the dashboard displays.

Two consequences:

- **Today is never shown.** The range stops at **yesterday** at the latest. A task completed this morning shows up tomorrow.
- **The numbers don't move while you work.** This isn't a real-time dashboard, and that's on purpose: you compare whole days, not moments.

To see the true state right now, open the **Tasks** and **Structures** sections. The dashboard is for seeing a **trend**.

#### The date range

_The header and the five indicators._
1. The date range drives everything below it.
2. The line follows the value day by day across the range.
3. The badge compares with the previous period of the same length.

By default the range covers the **last seven days, ending yesterday**. It's neither the calendar week nor the current month: it's a rolling window.

You can change it freely, up to a year. **The future and today are blocked** in the calendar, for the reason above.

Changing the range changes **everything**: the five indicators, every chart, and the trail table.

#### The five indicators

They sit side by side at the top. Each carries three things: a number, a small line, and a change badge.

| Indicator | What it is |
|---|---|
| **Critical tasks** | Tasks with **Critical** priority that aren't done |
| **Open tasks** | Every task that isn't done |
| **Completed tasks** | Tasks completed **during the range** |
| **Structures at risk** | Structures at **high or moderate** risk |
| **Overdue reports** | Inspections whose due date has passed |

There's a difference in kind worth seeing: **four of these are a state, one is a count.**

- Critical tasks, open tasks, structures at risk and overdue reports are **the state on the last day of the range**. Making the range longer doesn't inflate them: they're balances, not sums.
- **Completed tasks** is the only one that **adds up over the range**. Double the duration and the number grows.

That's the reading that matters: the first four say "here's what's still on the table", the fifth says "here's what we got through".

##### The line and the badge

The **small line** behind the number traces its value day by day across the chosen range. It gives no scale: it gives a shape. A steadily rising line on "Open tasks" is a signal, even when today's number looks acceptable.

The **coloured badge** compares with **the previous period of the same length**: seven days against the seven before, a month against the month before. It shows the raw difference, not a percentage.

Its colour follows the **meaning** of the news, not the sign of the number:

- for four indicators out of five, **going up is bad** — more critical tasks, open tasks, structures at risk or overdue reports is red;
- for **Completed tasks** it's the opposite: up is green.

When the difference is zero, the badge disappears.

#### The charts

Below the indicators, ten charts across four rows. They all rest on the same range.

_The first two rows of charts._
1. Four doughnuts: how what's still open breaks down.
2. The hours trend, which does not follow the range you picked.
3. The horizontal bars, ranked largest to smallest.

**Four doughnuts** break down what's open:

- **Open tasks by status** — how many are waiting, how many are running;
- **Open tasks by priority** — how serious what's left is;
- **Structures by risk level**, including those **not evaluated**;
- **Projects by status**.

**Three workload charts**:

- **Hours worked trend**, by week. Careful: this one has its own window — the **last eight weeks**, regardless of the range you picked;
- **Open tasks by type** — which kind of work dominates, useful for a funding application;
- **Hours per member**.

**Two rankings** — the members who **created** the most tasks, and those who **completed** the most. The first measures vigilance, the second execution; they're almost never the same people, and that's fine.

Finally, **the progress of active projects**.

A chart with no data shows "No data available" rather than disappearing: the grid always keeps the same shape.

#### The trail table

_Trail health._
1. Open tasks, by status.
2. Structures, by risk level.

This is the most useful widget on the page, and the most ignored.

Each row is a trail; on the left its **open tasks** split by status, on the right its **structures** split by risk. The rating symbol recalls the trail's difficulty.

This table answers the question no other screen asks: **where is the work concentrated?** A trail with seven tasks waiting and two high-risk structures isn't an open trail, whatever its published condition says. It's the right starting point for setting up a project or planning a work day.

A value of zero shows as pale grey rather than a badge: your eye only sees what isn't zero.

#### What filters the page

Two things, and only two:

**The current activity.** As everywhere in Sentinel, the dashboard shows one activity at a time. Switching activity recomposes the whole page.

**The date range.** There is **no other filter**: no filter by trail, by assignee or by project. For that, go through the Tasks or Structures sections and their [filters](/en/docs/use-advanced-filters).

#### Who has access

The dashboard falls under the **Dashboard** right in the activity manager, at the **read** level. Without it the entry doesn't appear in the menu and the app opens elsewhere.

It's a right to grant broadly: a dashboard allows no changes, and a crew that sees its numbers steers better than a crew that merely endures them.

#### Three pieces of advice

**Look at the shape before the number.** A number on its own says nothing. "Open tasks: 68" means nothing; "68 and the line has been rising for ten days" means it's time for a work day.

**Lengthen the range to judge, shorten it to act.** A month shows a trend, seven days show what just happened. They read differently.

**Start at the bottom of the page.** The indicators say there's a problem; the trail table says **where**. It's the only one of the two you can act on come Monday.

### Checklists: repeating the same checks across the network

URL: https://trail-sentinel.com/en/docs/use-checklists
Applies to: web, mobile

Some checks always come back: at season opening you go over signage, culverts, drainage and hazard trees again — **on every trail**. A task is the wrong tool for that: it describes a one-off problem, not a routine repeated identically across twenty trails.

That is exactly what checklists do. You define the list of points to check once, you run it on the trails concerned, and everyone ticks as they go.

**Where:** left navigation bar, under **General** → **Checklists**.

#### Three words of vocabulary

**An item** is a point to check: "Culverts", "Waymarking", "Hazard trees". It carries an icon, which acts as a visual anchor in the matrix.

**A campaign** is a run: "Season opening 2026". It applies the same list of items to a set of trails. Each trail gets its own copy — ticking "Culverts" on La Coulée ticks nothing anywhere else.

**A template** is a list of items saved to be run again. It is **optional**: you can perfectly well create a campaign by typing the items directly. A template becomes useful in the second season, when you want to run exactly the same list again.

#### Following a campaign on the web

A campaign view is a matrix: **one trail per row, one item per column**.

_A campaign under way: five trails, eight items._
1. One row per trail, with its difficulty dot.
2. One column per item. Hover an icon to read its name.
3. Each cell is an independent tick: this trail, this item.
4. The right-hand column stays visible while scrolling: it holds the trail's discussion.

This layout answers the question that matters at a glance: **where do we stand?** A full row is a finished trail. An empty column is a point nobody has tackled anywhere yet — often a sign that the equipment or the skill is missing.

The header totals trails, items and progress. The **⋯** menu holds the rest: edit the campaign, set its repetition, duplicate it, mark it complete or delete it.

##### Launching a campaign

The **New checklist** button opens a four-step wizard:

1. **Name** — plus, if you want, a lead and an assignee.
2. **Content** — either an existing template, or items you type in. If no template exists, the wizard starts straight in free entry.
3. **Repetition** — leave it empty for a one-off campaign, or set a frequency so it relaunches on its own.
4. **Trails** — the ones concerned. This choice is what creates the matrix rows.

##### The per-trail discussion

Each row carries its own conversation. That is where you write "the culvert at km 2 needs replacing, not just clearing" — attached to the right trail, not lost in a general thread. These exchanges also show up in the Discussions section.

#### Ticking in the field

##### Finding checklists on mobile

Checklists are not a separate tab: they are a **view of the map screen**. Tap the place pill at the top left — the one showing the place name and, right below it, the current view.

_The view switcher, opened from the place pill._
1. Tap the "Checklists" card.
2. The current view is outlined in green.

The line under the place name always tells you where you are. If you are looking for the map and can't see it, chances are you stayed in another view.

**If the "Checklists" card doesn't appear at all**, it is not a bug: your role has no read access to checklists. See the next section.

##### Ticking items

You then drill down three levels: **campaigns**, then the **trails** of a campaign, then the **items** of a trail. The **place band stays on top** at every level, with the back arrow right below it: you always know where you are.

_A trail's items, in the field._
1. The trail's progress stays visible at the top.
2. Tapping the row or the box ticks the item.

**It works without coverage.** Ticks go into the sync queue and go up as soon as the connection is back — the same mechanism as tasks created offline. You see your action take effect immediately, even at the bottom of a valley.

Mobile is for **ticking**, not managing. Creating a campaign, changing items, setting repetition or completing a campaign all happen on the web.

#### Roles: who ticks, who manages

This is the point that causes the most confusion, because there are **four levels**, not two. In the role editor, the "Checklists" level comes with a "Check items" toggle:

| Level | What the person can do |
|---|---|
| **None** | The section does not appear |
| **View** | See campaigns and progress, change nothing |
| **View + check** | See **and** tick items. Cannot create, edit or delete a campaign |
| **Manage** | Everything: create, edit, repeat, duplicate, complete, delete — and tick |

**"View + check"** is the level most organizations don't know they have. It is the right setting for a volunteer or a seasonal employee: they do the work in the field and tick what they did, without being able to change the campaign by accident.

**Templates are a separate right.** They live in the place settings, not in day-to-day management. So someone can manage campaigns without touching templates, and the other way round — an administrator can prepare templates without being involved in the season's campaigns. If the **Templates** tab doesn't appear for you, that is the right you're missing.

**One trap to know:** "Manage" includes ticking. There is no need to also turn on the "Check items" toggle — it is forced on at that level anyway.

#### Three pieces of advice

**Start without a template.** Create your first campaign by typing the items. When you run the same one the following year, you'll know which to keep — and that is when a template earns its place.

**One item = one observable check.** "Culverts" either ticks or it doesn't. "Get the trail back in shape" never ticks cleanly, and the matrix becomes useless.

**Read the columns as much as the rows.** Rows tell you which trails are moving. Columns tell you which points are stuck everywhere — often the more actionable information.

### Structures and their inspection reports

URL: https://trail-sentinel.com/en/docs/inspect-structures
Applies to: web, mobile

A boardwalk, a culvert, a junction sign: those are **structures**. They aren't fixed once and for all — they're **watched**, at regular intervals, and that watching has to leave a trace.

That's the difference from a task. A task is born from a problem and dies when it's solved. A structure exists as long as the asset does, and accumulates an **inspection history** that tells the story of its ageing.

This page covers both halves: the Structures section, and the inspection report in detail. Configuring the **types** and their questionnaire lives elsewhere — see [structure types](/en/docs/manage-structure-types).

**Where:** left navigation bar, under **General** → **Structures**. On mobile, structures live on the **Field** view.

#### The section

_The structure list._
1. Grouping changes how you read the list.
2. The type's badge takes the colour of the risk level.

The section opens on a list paired with a map. Three view modes take turns from the toolbar:

| View | What it answers |
|---|---|
| **List + map** | Where my assets are, and which one I open |
| **Kanban** | How many I have at each risk level |
| **Calendar** | Which inspections fall in which month |

The **calendar** is the most underrated: it places each structure on the date of its next report. It's the view that answers "what's waiting for me in June".

##### Reading the list

Each row carries the structure's **name** and its **type**, preceded by a badge with the type's glyph. That badge **takes the colour of the risk level** — it's the visual code for the whole section:

| Colour | Level |
|---|---|
| Green | No risk |
| Yellow | Low risk |
| Orange | Moderate risk |
| Red | High risk |
| Grey | **Not evaluated** — no report exists yet |

The list **groups** four ways: by status, by type, by trail or by folder. **Folders** are yours: you file assets into them by dragging, and you can move several at once with Shift + click. You create one with the folder button, on the right of the small bar above the search field; on a brand-new place, where the list is still replaced by a welcome block, that block's **Create folder** button does the same thing.

##### The status can't be set by hand

On the kanban, dragging a card from one column to another does nothing — a message says why: **to change a structure's status, you have to create an inspection report.**

That's the most important rule in the section. The risk level isn't an opinion you adjust; it's the **result of a dated, signed inspection**. That's what makes the history defensible in front of an insurer or a municipality.

#### Creating a structure

On the **web**, from the section's **Create structure** button — or **from an image**, which reads the photo's position to place it.

On **mobile**, from the map's **+** button, standing at the asset.

A structure carries a name, a type, a position, a trail, a description and photos. The **name can fill itself in** if you've set up a numbering rule — see [structure types](/en/docs/manage-structure-types).

As with tasks, all of this works [offline](/en/docs/work-offline).

#### The inspection report

This is the heart of the module.

_The report form._
1. The next reminder date — absent when rescheduling is automatic.
2. A critical question, flagged as such.
3. Four ratings, plus "not applicable".

The form always has the same three blocks at the top:

**A general comment.** What you found, in one sentence or ten.

**The next reminder date.** It only shows **when automatic rescheduling is off** for that type. When it's on, the date is computed from the resulting risk and the field disappears.

**Photos** of the report as a whole.

Then comes the **evaluation**, if the type has an active questionnaire.

##### Answering the questions

Each question is rated on **four steps**, or marked **not applicable**. The labels name the risk, not the quality:

| Rating | Label | What it says |
|---|---|---|
| 1 | **Critical** | This element is dangerous |
| 2 | **Moderate** | It needs close watching |
| 3 | **Low** | Normal wear |
| 4 | **None** | Nothing to report |
| — | **Not applicable** | The question doesn't concern this asset |

Every answer also takes **a comment and photos**. That's what makes a report worth having: a 2 on "Decking" means nothing six months later; a 2 with a photo of the split plank reads itself.

A question marked **critical** carries an orange badge. Giving it a 1 puts the asset at **high risk** whatever the rest of the questionnaire says.

The details of the calculation — the formula, question weights, how "not applicable" is handled — are explained in [structure types](/en/docs/manage-structure-types).

##### Without a questionnaire

If the type has no active questionnaire, the form replaces the evaluation with a **status you pick by hand**. That's the simple mode: you look, you classify, you note the return date. Useful for an asset type that doesn't justify a grid.

##### What saving triggers

Three things, in order:

1. the **score** is computed and yields a **risk level**;
2. that level **becomes the structure's status** — what the whole crew sees;
3. the **next report date** is set, computed or entered.

#### The history

_A structure's reports._
1. The button creates a new report.
2. Each report keeps the status it produced, and its author.

A structure's page lists its reports newest first, **grouped by year** — a year picker saves you scrolling through ten years of inspections.

Each row carries the **badge of the status it produced that day**, the date, and the inspector's name. Opening a report shows the answers, comments and photos exactly as they were entered. **A report can't be edited**: it's a dated finding, not a draft.

##### Deleting a report

The ⋯ menu on each row lets you delete it. Two things to know:

**The report is archived, not destroyed.** It leaves the list, but the trace stays on the server — which matters for a legal file or a claim.

**The structure's status is recalculated.** It takes the one from the **most recent remaining report**. If none remains, the structure goes back to **Not evaluated**.

That's the right move when an inspection was filed on the wrong asset. It is not the right move for "erasing" a bad result.

#### Getting reports out as PDF

Two exports, at two scales.

**A single report**: the ⋯ menu on its row, **Download PDF**. That's the document you attach to an email.

**A whole batch**: the **Export PDF** button in the section's toolbar. One document, with **one structure per section and its latest report**. You choose:

- **Export all** — every structure that has at least one report;
- **Export with filters** — by status, type or trail, to narrow it down.

The limit is **50 structures per export**. Beyond that, tighten the filters — which is also a good way to cut a file into readable volumes.

That's the document that goes to the town council, the funder or the insurer. It's also the reason for everything else: without it, the inspection stays knowledge inside someone's head.

#### In the field

Mobile does the essentials: create a structure at its real position, open a page, **create a report** with its full questionnaire, comments and photos.

It all works offline. A report written at the bottom of a ravine goes out when the network returns, and the structure's status updates then — not before.

#### Who can do what

Two distinct rights in the activity manager:

- **Structures** — see the list and pages with read; create, edit and delete with write.
- **Structure reports** — write is required to **create or delete a report**.

Splitting the two is deliberate: you can hand inspection to someone without giving them the right to rename or delete assets. See [roles](/en/docs/understand-roles).

#### Four pieces of advice

**Photograph the answer, not the structure.** A wide shot of the bridge proves nothing. The photo of the rusted anchor, attached to the "Anchors" question, is evidence.

**Let automatic rescheduling build the calendar.** Set once per type, it fills the Calendar view on its own and you stop missing due dates.

**Only delete a report if it's wrong.** A bad result you erase is a history that lies — and that's exactly what an insurer looks for.

**Export at the end of the season.** The year-end PDF takes five minutes to produce and is worth ten emails of justification the following winter.

### Trail conditions: telling the public what's open

URL: https://trail-sentinel.com/en/docs/publish-trail-conditions
Applies to: web, mobile

The question you get asked most isn't "how many kilometres do you have?", it's "is it open today?".

**Trail conditions** answer that one. You build a report listing your trails with their state, you keep it current in seconds from the field, and you publish it on your website. Users see the same thing your crew sees, at the same time.

Three states, no more:

| State | What it means |
|---|---|
| **Open** | Rideable |
| **Under construction** | Rideable with care, or a crew is on it |
| **Closed** | Stay off |

That economy is deliberate. A seven-shade scale never gets kept up to date; three states do.

**Where:** left navigation bar, under **Administration** → **Trail conditions**.

#### One report per audience, not per network

A **condition report** is an ordered list of trails, attached to an activity. You can have several per activity, and that's often the right call: a public one for the website, a more detailed internal one for the crew, a seasonal one.

_An activity's reports._
1. The **Widget** button opens this report's embed page.
2. The menu renames or deletes the report.

Each report belongs to **exactly one activity**. On entering the section you pick the activity first, then the report — unless you only have one, in which case Sentinel takes you straight there.

#### Building the report

Inside, you build the list from two bricks: **trails** and **folders** to group them.

_A report's contents._
1. The handle reorders — the report's order is what the public will see.
2. A folder groups trails; its menu applies a condition to the whole folder at once.
3. A trail's condition is changed here.

A few mechanics worth knowing:

**Folders are one level deep.** A folder holds trails, never another folder. That's a deliberate constraint: a public report three levels deep isn't readable.

**The order is yours.** Drag the rows, or use **Sort** to arrange them all at once by difficulty and name. What you see here is exactly what a visitor will see.

**Nothing is saved until you hit Save.** Additions, removals, condition changes, reordering: it all accumulates locally and goes out in a single submission. If you leave the page with pending changes, the app holds you back.

**Applying a condition to a folder** is the highest-value gesture in the section: close "North sector" entirely after rain, then reopen the two trails that dried out.

**Removing a trail from the report doesn't delete the trail.** It leaves the public list, that's all.

##### The same trail in several reports

This is where it gets interesting. If a trail appears in two reports, changing its condition in one **propagates to the other** on save. You don't have to maintain two lists in parallel.

The same holds when adding: a trail already present elsewhere arrives carrying the condition it already has, not a default "Open".

##### The guard on "Open"

If you set a trail back to **Open** while it still carries in-progress tasks, Sentinel stops you and tells you how many. You get two buttons: **Set Open** anyway, or **Under construction**.

It isn't a block, it's a reminder — nine times out of ten, someone forgot a crew was still out there.

#### Automatic updating

Each report has a setting, in the ⚙ menu of its header: **automatic condition updating**. It is **on by default**, and here's precisely what it does.

When a task attached to a trail moves to **In progress**:

- that trail goes to **Under construction** in every report where the automation is on;
- unless it is already **Closed** — a manual closure is never overwritten.

When that task leaves In progress:

- Sentinel checks whether any other in-progress tasks remain on that trail;
- if none remain, the trail goes back to **Open**.

In other words, your report keeps itself current during the work, provided the crew moves its tasks to In progress when they start. That's the real reason to do it.

**When to turn it off**: when you want the public report to move only by human decision. The setting is per report — you can perfectly well run an automatic internal report and a manual public one.

#### From the field

On mobile, conditions are one of the view switcher's views, alongside the map and the checklists. You open it, you change a state, done.

The **place band stays on top** — it's the same shell as the map. There's no filter row and no filter button on this view though: it doesn't need them.

_A condition report on mobile._
1. The difficulty badge and the trail's name.
2. The state — tapping it opens the choice of three conditions.

Two differences from the web, both intentional:

**It's immediate.** No Save button: you pick the state, it goes. In the field, with gloves on, a two-step flow doesn't survive.

**You don't build the report from mobile.** Adding trails, creating folders, reordering: that's desk work. Mobile is for updating, not for building.

You'll also see a **prompt** appear when you start a task on a trail tracked by a report: "Do you want to set its condition to Under construction?". It's the manual counterpart of automatic updating.

#### Publishing on your website

This is the part your users see. The **Widget** button, on a report's row, opens its embed page.

_The widget's Installation tab._
1. The activation switch — while it's off, the report is reachable by nobody from outside.
2. The script, pasted once into the `<head>`.
3. The tag pasted where the widget should appear.

##### The normal method: two tags

The script in the `<head>`, **once per page** even if you display several reports. Then a `<div>` tag exactly where the widget should render. That's it: no account, no API key to protect, no code to write.

The `data-lang` attribute fixes the widget's language for your visitors, independently of yours.

##### If your platform blocks scripts

SharePoint, some intranets and sites with a strict security policy refuse external scripts. For those, the page offers an **iframe** — same content, no third-party script to load.

And if the iframe is blocked too, the address inside its `src` attribute is a **full page**: it opens as-is in a browser. You can link to it from a menu or send it by email.

##### What a visitor sees

_The widget on a customer's site._
1. The report's name and the time of the last update.
2. Each trail's state, with its difficulty symbol.

The widget draws itself with the host site's font, not Sentinel's — it's built to blend in, not to stand out. A **Customization** tab lets you set the width, corner radius, shadow, header and section colours, and decide whether to show the header, the date, and a **map of the tracks** beside the list.

Three things worth knowing:

**The widget refreshes on its own**, roughly every minute, without the visitor reloading the page. A trail you close from the field shows as closed on their screen shortly after.

**The address carries a token**, not your place's identifier. That token grants access to this report and nothing else: not your tasks, not your members, not your other reports.

**Turning the switch off cuts access**, immediately and everywhere the widget is installed. That's the gesture to know if a report gets published by mistake.

#### Who can do what

Conditions fall under the **Trail conditions** right in the place settings.

- With **read**: see the reports and the states, change nothing. On mobile the badges stop responding to touch.
- With **read and write**: create reports, build them, change conditions, enable the widget and customize it.

The right is the same for everything: there's no middle level that would allow changing a condition without being able to publish the widget. If you want field crews updating states, they need write — grant it, knowing they can also touch the widget.

#### Three pieces of advice

**Keep the public report short.** The visitor wants to know whether their usual loop is open, not read your 60 segments. Group by sector and only expose what they recognize.

**Leave automatic updating on** for the report your crew feeds, and get them into the habit of moving tasks to In progress. You get a current report with no extra gesture at all.

**Test the embed before handing it to your webmaster.** Open the `.../embed` address in a tab: if the page renders, the token is good and any remaining problem is on the host platform's side, not Sentinel's.

### Conversations: talking about a task, inside the task

URL: https://trail-sentinel.com/en/docs/use-discussions
Applies to: web, mobile

Coordinating a trail crew nearly always breaks down in the same place: a messaging group. "That plank at kilometre 4" comes up three times a season, each time in a different thread, and nobody can find last year's photo.

Sentinel's **conversations** fix that in one way only: the thread doesn't exist on its own. It's **attached to the thing you're talking about** — a task, a structure, a project, a checklist. You discuss the broken plank *inside* the "Broken plank" task. Six months later the exchange is still there, next to the photo, the GPS position and the status.

**Where:** left navigation bar, under **General** → **Conversations**. A thread also opens from the task, structure or project it belongs to.

#### Where conversations live

There's no "new conversation" button. A thread is born when someone writes the first message from a task, a structure, a project or a checklist.

The **Conversations** section then gathers every thread in the place in one spot.

_The Conversations section._
1. The icon says what it's about — the task's type, the structure's type, or a folder for a project.
2. The badge counts the messages you haven't read.
3. The filter narrows the list to tasks, structures or projects.

The list is sorted by recent activity and loads in batches of twenty as you scroll. It updates **live**: a message sent by a colleague moves the thread up without you refreshing anything.

Opening a thread marks it read.

#### Writing in a thread

_A conversation thread._
1. Your messages sit on the right in gold; everyone else's on the left with their avatar.
2. A mention shows in gold inside the text.
3. The paperclip adds photos — you can also drag and drop them onto the thread.

Four gestures, and that's all:

**Mention** with `@` — the most useful gesture in the section, detailed just below.

**Reply** to a specific message. The original stays displayed above yours, which keeps the thread readable when two topics cross.

**React** with an emoji. Useful for acknowledging without adding another message: a 👍 beats an "ok got it" that notifies everyone.

**Attach photos.** On the web, drag them straight onto the conversation. On mobile, the camera is one tap away.

##### Mentioning someone

A mention does two things at once, and the second is the one people forget:

1. the person gets a **notification**, even if they weren't following the thread;
2. they **start following the thread** from then on — so they'll get the later messages too.

It's the only way to pull someone into a conversation they never took part in. A member who never wrote in a thread receives nothing from it: without an `@`, your question won't reach them.

**How to trigger it.** On the web, type `@` in the input and keep typing: the list filters on what you write. On mobile you can do the same, or tap the **@** button in the input bar.

**Who shows up in the list.** The place's members, you excepted, sorted by name, eight at a time — narrow it down by typing a few more letters.

One detail that explains most "I can't find them in the list": **on the web, the list only shows members who have access to the current activity**. Someone restricted to skiing won't appear while you're working in mountain biking. When that happens, the fix isn't in the conversation but in their [activity restrictions](/en/docs/invite-and-manage-members).

Worth knowing: **on mobile the list doesn't apply that filter** and shows every member of the place. So you can mention someone there who won't see the task you're discussing — they'll get the notification without being able to open the item.

**What the reader sees.** The mentioned name shows in gold inside the message. A mention isn't a link: it's a visual marker, backed by a notification.

#### Who gets notified

This is the part people rarely get right first time, and it explains most "I was never told".

**You follow a thread as soon as you take part.** Writing a message subscribes you. Being mentioned subscribes you too. Nobody is subscribed by default to the place's conversations.

From then on, each message sent triggers this:

| Case | Who is notified |
|---|---|
| Plain message | Every subscriber of the thread, except you and except the people mentioned |
| Someone mentioned with `@` | Them, always, with their own notification |
| **Reply** to a message | **Only the author of the message you replied to** |

That third line is the surprise. **Replying is quieter than writing.** A reply doesn't wake the thread: it notifies exactly one person. If you want the crew to see your message, write it normally rather than as a reply — or mention the people concerned explicitly.

A message's author is never notified of their own message, and someone mentioned never gets two notifications for the same message.

##### Stepping out of a thread

The gear at the top of the thread opens two settings, **personal to you** — they change nothing for anyone else.

_A conversation's settings._
1. Mute turns off notifications for this thread.
2. Unread tracking decides whether the thread goes bold in the list.

The two are independent, and that's useful: you can **mute the notifications while keeping the unread counter**. The thread still shows bold in the Conversations section, but it no longer buzzes your phone. That's the right setting for an active thread you only need to catch up on later.

#### In the field

The thread is identical on mobile: same bubbles, same mentions, same reactions, same photos.

_A conversation on mobile._
1. The gear opens the same two settings as on the web.
2. The input field, with photo attachment on the left.

What changes is the **offline behaviour**, and it's complete:

- you read the messages **already downloaded**, with no signal;
- you **still write**. The message goes into the sync queue with your photos and mentions, and sends itself when the network comes back;
- what stays unavailable offline: **reactions** and loading messages older than the cache.

A message written offline isn't sent twice if the sync runs again — every message carries a creation identifier that acts as a guard on the server side. So you can send without thinking about it from the bottom of a ravine.

#### Who can read and write

Conversations fall under the **Conversations** right in the activity manager.

- With **read**: you see the threads and the messages, with no input field and no reactions.
- With **read and write**: you take part.

One detail that matters: **there is no private conversation**. Any member with read access sees every thread in the place — the conversation belongs to the object, not to the people who wrote in it. This isn't a messaging app; don't use it for anything the crew shouldn't read. See [roles](/en/docs/understand-roles).

#### Three pieces of advice

**Write inside the object, not next to it.** The value of a Sentinel conversation isn't the exchange, it's that you find it six months later beside the photo and the position. A message sent through another channel is a message lost.

**Mention rather than relying on subscriptions.** Someone who never wrote in the thread follows nothing. If you need an answer from a specific person, put their `@` in.

**React instead of replying "ok".** Every message notifies; no reaction notifies anyone. On a ten-person thread, the difference shows fast.

### Notification settings: choosing what interrupts you

URL: https://trail-sentinel.com/en/docs/notification-settings
Applies to: web, mobile

A trail crew that switches its notifications off misses the emergencies. A crew that leaves everything on ends up ignoring all of it. The right setting is in between, and it isn't the same for a coordinator as for a Saturday volunteer.

This page describes every switch, what it actually triggers, and the handful of rules that explain why you didn't get what you expected.

**Where:** on the web, the **bell** or the **user menu** at the top right → **Notification settings**. On mobile, **Notifications** → the **⋯** menu → **Notification settings**.

#### The three channels

Everything starts with three channels, set at the top of the screen.

| Channel | Where it lands | Set from |
|---|---|---|
| **Email** | In your inbox | Web and mobile |
| **Push** | On your phone's lock screen | **Mobile only** |
| **Notification** | The bell in the app, with the notification list | Web and mobile |

These are **master switches**. Turn "Email" off and no email goes out at all, whatever is set below. That's the move when you're away for two weeks.

**Push only exists on the phone**, for a simple reason: it's your device that has to allow Sentinel to notify you. You are asked once when the app starts, on the last step of the welcome flow described in [the first launch](/en/docs/first-sign-in). If you haven't granted it yet, turning the Push channel on here triggers the system prompt. And if you refused it once, the app can't ask again: you have to go through the phone's settings.

A consequence worth knowing: **until some device has enabled push, no push notification goes out at all**, even with the "Push" boxes ticked. The server needs a registered device to know where to send.

Two things happen when you allow push, and they don't follow the same rules:

- **The phone's permission and the device registration are immediate.** They don't go through *Apply*, and leaving the screen without saving doesn't undo them — a granted permission stays granted, because the system holds it, not the app.
- **The "Push" setting itself is a preference** like the others: it is only stored when you tap *Apply*.

Turning the Push channel off never asks for permission again: switching a preference off requires nothing from the system.

#### The detailed settings

Below the three channels sits a list of events. Each has **one box per channel**.

_The panel, on the web._
1. Only two channels here: push is set from the phone.
2. One box per channel and per event.
3. The report reminder is email-only, with its frequency.

The rule is an **and**: you get something on a channel if the master channel is on **and** that event's box is ticked. Turning a master channel off greys out the whole column — the boxes keep their state, but they no longer do anything.

_The same screen on mobile._
1. Three channels on mobile, push included.
2. The greyed-out column is a master channel that's off.

On mobile, the screen opens from **Notifications → the ⋯ menu → Notification settings**. On the web, from the **bell** or the **user menu**.

Either way, **nothing is stored until you confirm**: *Apply* on mobile, *Save* on the web. The button stays inactive until you've changed something, and the app catches you if you leave with unsaved changes.

If you answer **"Don't save"** to that prompt, the screen returns to exactly the settings that were in place when you opened it. The one exception, described above: the phone's push permission, which the app cannot take back.

#### What each line triggers

##### Invitation

| Setting | You're told when |
|---|---|
| **Invitation received** | Someone invites you to join a place |
| **Invitation accepted** | Someone **you** invited accepts |
| **Invitation rejected** | Someone **you** invited declines |

The last two only matter to whoever does the inviting — an administrator. A volunteer can turn them off and lose nothing.

##### Tasks and projects

This is the section that decides whether your inbox is useful or saturated.

| Setting | You're told when |
|---|---|
| **New task** | **Anyone** creates a task in the place |
| **Task assigned** | A task is assigned to you, or to one of your groups |
| **Update on my tasks** | The status changes on a task you **created** or are **assigned** to |
| **Update on all tasks** | The status changes on **any** task in the place |

The first two are targeted; the last two look alike but are worlds apart in volume:

- **"Update on my tasks"** follows you. That's what most people want.
- **"Update on all tasks"** sends you every status change on the network. On an active place that's dozens a day. Save it for someone genuinely driving everything, and preferably on the Notification channel rather than by email.

Same warning for **"New task"**: on a place where volunteers report a lot, it's noisy. It's also the only way to see reports arrive in real time — a coordinator's call.

##### Structures

| Setting | You're told when |
|---|---|
| **New report** | Someone files an inspection report on a structure |
| **Upcoming reports reminder** | Periodically, by email, with upcoming and overdue inspections |

The reminder is different: **it only exists by email**, and it has a frequency.

| Frequency | Sent | Contents |
|---|---|---|
| **Daily** | Every day | Reports due today, those in the next 5 days, and overdue ones |
| **Weekly** | Every Monday | All of the week's reports, and overdue ones |
| **Monthly** | The 1st of the month | All of the month's reports, and overdue ones |

All three always include **overdue reports**. It's the only mechanism in Sentinel that chases you about work that hasn't been done — every other notification reacts to an event.

Weekly suits most networks. Daily is for an intensive inspection season; monthly for a network with few structures.

##### Checklists

**Assignment** tells you when you're set as responsible for a checklist, or assigned to one.

Careful: **this section only exists on the web**. The setting applies to both apps, but the mobile screen doesn't show it. To change it, go through the web app.

#### Conversations aren't here

The absence is what surprises people most: **there is no setting for conversations**, even though they generate the most notifications.

That's deliberate. [Conversations](/en/docs/use-discussions) work by **subscribing to a thread**, not by a global setting: you're notified about the threads you take part in, and you mute them **thread by thread** — inside the conversation, with *Mute notifications*.

One useful detail: the **in-app** notification is capped at **one per conversation per hour** while you haven't read the previous one. Ten messages in ten minutes don't make ten badges. Push isn't capped — muting the thread is what stops it.

Mentions also escape these settings: being named with an `@` always notifies you, even in a thread you don't follow.

#### Why am I not getting anything?

In order, the real causes:

1. **The master channel is off.** That's cause number one. Look at the three cards at the top first.
2. **You didn't confirm.** Ticking a box isn't enough: you have to *Apply* or *Save*.
3. **Push was never enabled on a device.** No registered device, no push.
4. **The phone refused permission.** The app can't ask again; go through the system settings.
5. **You're the author.** Sentinel never notifies you about your own action.
6. **It's a conversation.** Check the thread's mute setting rather than this screen.

#### Three pieces of advice

**Set by role, not by person.** A coordinator wants "all tasks"; a volunteer wants "my tasks" and nothing else. Two settings, not ten.

**Put the volume on the Notification channel and the important things on email.** The bell absorbs noise without guilt; an email you ignore eventually becomes a file you ignore.

**Keep the report reminder on.** It's the only net that catches a forgotten inspection, and it costs one email a week.

### Share a task with a public link

URL: https://trail-sentinel.com/en/docs/share-a-task-publicly
Applies to: web, mobile

Sometimes a task has to leave the network. The excavator operator coming to fix the culvert is not a member. Neither is the municipality that has to approve the work. Nor the neighbouring club that manages the next section.

The **public link** answers exactly that need: a web address showing **one single task** — its position, its track, its annotations, its photos — to anyone who opens it, with no account and nothing to install. The rest of your network stays invisible.

The link can be switched off at any time.

**Where:** on a task's detail view — the **Share** button in the toolbar on the Web, the **Share** button in the action bar on mobile.

#### Create the link

Open a task, then **Share**.

On the **Web**, a dialog opens with a **Public link** toggle. Switch it on: the address appears right below, with a **Copy** button.

_The share dialog, public link switched on._
1. The **Public link** toggle: everything starts here.
2. The **Copy** button; to its left, the address truncated on screen.
3. The photo checkbox, with their count in brackets.

The box at the bottom spells out, before you switch anything on, what the public page will show and what it will never show.

On **mobile**, a sheet slides up offering two things that should not be confused. **Share with members** sends a link that only opens the task for network members. **Create a public link** is the one we are after here: it then opens your phone's share sheet, and you send the link by message, by email, or copy it.

_The share sheet on a task that is still private._
1. **Create a public link** — the row that makes the task visible to everyone.

Once the task is public, the sheet changes: a banner shows the address at the top — tap it to share it again — and the only other option is **Disable public link**. You will never see "create" and "disable" side by side.

_The same sheet, once the task is shared._
1. The status banner: tap it to share the address again.
2. Disabling replaces creating, in red.

Once the task is shared, the **Share** button carries a globe badge. That is your visual cue: one glance at the task tells you it is public.

#### What the recipient sees

A plain page, in your colours, that works on a phone as well as on a computer:

- the **task name**, its type and its status;
- a **map** with the point or the track, the trail concerned and your annotations, switchable to satellite view and expandable to full screen;
- the **GPS coordinates** with a button to copy them, for a point task;
- the **description**;
- the **photos**, viewable one at a time;
- three **downloadable files**: GPX, KML and GeoJSON.

What does **not** appear: your members, the assignment, the materials, the logged time, the discussions. Nor the project, the folder, or your other tasks. The page shows the task and nothing around it — and the share dialog reminds you of both lists before you switch anything on.

The page is not indexed by search engines. It is reachable by whoever holds the link — treat the link as a key.

#### The GPS files

The three formats exist because field tools do not read the same files.

| Format | For whom |
|---|---|
| **GPX** | The most universal one. Garmin units, Polaris Ride Command screens, onX. Your default choice. |
| **KML** | Google Earth, and anything that needs areas rather than plain tracks. |
| **GeoJSON** | Mapping software such as QGIS. |

The contractor downloads the GPX, loads it into their unit and drives to the exact point. No account, no app, and no phone call to have the route described to them.

#### Open the task in Sentinel

At the bottom of the public page, an **Open in Sentinel** button is there for network members who receive the link like everybody else.

It takes you to the right place for your device, with nothing to choose:

- **on a phone** with the app installed, the task opens in the app;
- **on a computer**, it opens in Sentinel on the web;
- **on a phone without the app**, it opens on the web too.

If you are not signed in, Sentinel asks you to sign in and then takes you straight to the task.

The button grants no extra access: it opens the task with **your** usual permissions. If the link points to a network you are not a member of, the app tells you so clearly instead of leaving you on an unchanged screen.

#### Photos, your call

The share dialog offers an **Include photos** checkbox. It is ticked by default, and the counter tells you how many photos would go out.

Untick it when the photos show something that should not leave: a licence plate, a private building, a person. The page stays complete for everything else — map, position, description, GPS files.

#### Close the link

The work is done and the contractor has left: reopen **Share** and use **Disable public link** (on the Web, switch the **Public link** toggle back off).

The address stops working immediately. Anyone reopening it sees a message saying the link is no longer available — not the task, and no trace of its content.

**Switching it back on later reuses the same address.** That is handy when you reopen a file with the same party. It matters if you closed the link because it had travelled too far: switching it back on puts it back in service for everyone who still had it.

#### What can go wrong

**The Share button is missing.** Public sharing requires edit rights on tasks. A read-only account can view the task but not make it public. See [Understand roles](/en/docs/understand-roles).

**A task with no location cannot be shared.** A task created without a position or a track has nothing to show on a map, so the **Share** button simply does not appear on it. Give it a location first.

**The recipient sees no photos.** Check the **Include photos** box in the share dialog — it may have been unticked.

### Trails: the backbone of your place

URL: https://trail-sentinel.com/en/docs/manage-trails
Applies to: web

This is the first thing to set up, and the one that makes everything else useful. A task attaches to a trail. A condition describes a trail. A checklist campaign runs across trails. The time report breaks down by trail.

Until your trails are in Sentinel, the rest works — but only halfway.

**Where:** left navigation bar, under **Administration** → **Trails**.

#### A trail belongs to one activity

The section starts by asking **which activity**. Mountain biking, hiking, cross-country skiing: each has its own trails, and a trail belongs to exactly one activity.

That is what lets a multi-activity place keep its networks separate. A member restricted to skiing will never see the biking trails — but that separation comes from the [member's activities](/en/docs/invite-and-manage-members), not from the trail itself.

#### Importing your tracks

You don't draw a trail by hand in Sentinel. You import it.

_The trail list for one activity._
1. The coloured dot is the difficulty level. That's the landmark you'll see on every map.
2. The distance, computed from the track — never typed by hand.
3. Import File(s): GPX, KML, or a ZIP archive holding several.
4. The checkbox, to select several trails and delete them in one go.

You can select **several files at once**. Each becomes a trail, attached to the activity you're currently in. A progress message follows you through the import.

Where do those files come from? Your watch or GPS tracking app, a survey done by a consultant, or an export from whatever tool you used before. Most mapping platforms export GPX.

The search at the top filters the list by name — handy once a network passes thirty trails.

#### A trail's page

Click a row to open it.

_A trail's page._
1. The track, drawn on the map.
2. The distance, computed from the track. It cannot be edited.
3. Activity and difficulty, the two fields that decide where and how the trail shows up.

The **name** is what your field teams see, in task lists and in the checklist matrix. Use the name people actually say, not the internal code.

The **description** is optional. Use it for what the track can't tell you: "wet rock after rain", "closed in spring".

The **difficulty** comes from the list you configure in its own section. Its colour is the trail's visual landmark everywhere else — on maps, in the kanban, in the checklist matrix.

As everywhere in the app, nothing applies until you hit **Save**, and you're stopped if you try to leave with unsaved edits.

#### Fixing a track

A trail got rerouted, or the original survey was rough? The **Update track** section replaces the geometry without touching the rest: the name, description, difficulty and — most importantly — **the tasks already attached** all stay put.

Three errors come up often at import time:

**"Multiple trails found in the file"** — your GPX holds several tracks. Split them into separate files, or use the multi-file import from the list.

**"No trail found in the file"** — the file only holds waypoints, no track. Common when you export favourites rather than a route.

**"File format not supported"** — Sentinel reads GPX, KML and KMZ. A `.fit` or `.tcx` file has to be converted first.

#### Deleting a trail

This is the action that deserves the most care. The confirmation says it plainly:

> This action will permanently delete this trail and **all associated tasks**. This cannot be undone.

In other words: deleting a trail erases the history of the work done on it. If the trail was simply closed or renamed, **edit it** rather than deleting it.

A single trail is deleted from its own page, at the bottom.

#### Working on several trails at once

From the list, tick the checkbox at the start of each row. As soon as one trail is ticked, the top of the screen changes: the search box gives way to the number of selected trails, **Cancel**, **Edit**, and **Delete trails**.

_Three trails ticked: the top bar changes._
1. Ticked rows take a tinted background — enough to see at a glance what you are about to act on.
2. **Edit** opens the form for the selection.
3. **Delete trails** wipes the whole batch, tasks included.

Three shortcuts are worth knowing:

- The checkbox at the top of the table selects **every trail on screen** — those of the current activity, and only those your search leaves visible.
- **Shift + click** on a second checkbox selects the whole range between the two, like in a spreadsheet.
- Clicking a trail's name still opens its page: ticking and opening are two separate gestures.

If you switch activity or change your search, the selection clears. That's deliberate: you don't act on rows you can no longer see.

##### Editing the selection

**Edit** opens a short form with two fields: **activity** and **difficulty**.

_The form for editing a selection._
1. The warning, which takes the place of the instruction as soon as the chosen activity differs from the list you're in.
2. The switch turned on: that field will be applied to the whole selection.
3. The switch turned off: the field is greyed out, and the trails' difficulty is left alone.

Each field has a switch. While it is off, the field is left alone — that is what lets you change the difficulty of thirty trails without saying anything about their activity. Turn on only what you mean to overwrite, then hit **Apply**.

This is the cleanup tool: thirty trails imported in one go all arrive with the same difficulty, and this is where you spread them out without opening thirty pages.

Be careful with the **activity** change: it doesn't just move the trail, it **takes its tasks along**. The trail then leaves the list you're in, since it now belongs to another activity.

##### Deleting the selection

The confirmation reminds you how many trails are involved, and the warning is unchanged: **the attached tasks go with them**. This is the kind of action you take after a botched import or during an end-of-season cleanup, not day to day.

#### Who can do what

You need write access to **Trails & Configuration** to import, edit or delete. In read-only, trails stay visible — they have to be, since tasks and maps refer to them — but the action buttons disappear.

That's also why this right raises itself when you grant Tasks or Structures in a [role](/en/docs/understand-roles): you can't work on tasks without seeing the trails they attach to.

#### Two pieces of advice

**Import everything, then clean up.** It is faster to import all your tracks and fix the names afterwards than to import them one at a time, polishing each.

**Settle your difficulties before importing.** Difficulty drives the colour, and the colour is what your team reads on the map. Setting the list up first saves you a pass over thirty trails.

### Activities: keeping your networks apart

URL: https://trail-sentinel.com/en/docs/manage-activities
Applies to: web, mobile

Many organizations maintain more than one network. The same woods hold bike trails in summer and cross-country ski tracks in winter, sometimes on different routes, with different crews and different seasons. A motorized club lives the same thing on a single corridor: ATV in summer, snowmobile in winter.

The **activity** is the wall between all of that. It is Sentinel's highest-level partition: a trail belongs to one activity, and tasks, structures, conditions, task types and structure types follow from there.

Without that wall, your summer map would show ski tracks and your statistics would blend the two.

**Where:** left navigation bar, under **Administration** → **Activities**.

#### Choosing your place's activities

The **Activities** section lists the eleven activities Sentinel knows about. You switch on the ones that concern you.

_The place's activity table._
1. The eleven possible activities — mountain bike, hike, cross-country skiing, alpine skiing, snowshoeing, trail running, gravel bike, fat bike, electric bike, ATV and snowmobile.
2. The switch decides whether the activity is offered in your place.

**Cross-country skiing and alpine skiing are two separate activities.** A resort that maintains both switches both on: each keeps its own runs, tasks and conditions, exactly like biking and hiking.

Nothing applies until you hit **Save**, and **at least one activity must stay on** — a place with none would have no possible trails or tasks.

**Turning a new one on is safe.** Sentinel automatically creates its default task type and structure type: you can start creating tasks in it right away, without going through the configuration sections first.

**Turning one off deletes nothing.** That activity's trails, tasks and history stay in the database. The activity simply stops being offered: it disappears from the picker and the lists. Switching it back on brings everything back.

One useful side effect: turning an activity off also removes it from your members' **activity restrictions**. Someone who only had ski access doesn't end up stranded with nothing.

#### Switching between activities

Day to day, you only work in one activity at a time. The picker at the top right says which one.

_The activity picker in the top bar._
1. The current activity. Everything on screen belongs to it.
2. The list of the ones you have access to.

Three things to know:

**The choice is remembered per place.** If you manage two places, each keeps its own preferred activity. You come back to the right one, and it survives closing the browser.

**The picker is inert if you only have access to one activity** — no arrow, no menu. That's not a fault.

**What you see depends on two things**, and this is the most common source of confusion: the **place's** activities (what your organization maintains) and the **member's** activities (the subset they were allowed, set on their [member page](/en/docs/invite-and-manage-members)). With no restriction, the member sees all of the place's.

In other words: if a colleague can't see cross-country skiing although you turned it on, check their activity restriction before doubting the place's configuration.

#### Switching activity on mobile

In the field, the picker is not at the top of the screen. It is a **round green button at the bottom left of the map**, in the row of floating buttons.

_The map's floating buttons, bottom left._
1. The activity picker — the current activity's icon, with a small chevron.
2. To its left: recentre on your position, and the map settings.

**It only appears if you have access to at least two activities.** That's the most common reason people can't find it: on a single-activity place, or for a member restricted to one, the button simply doesn't exist.

Tapping it opens the list.

_Choosing an activity on mobile._
1. The radio button marks the current activity.
2. Only the activities you have access to appear.

The choice is remembered the same way as on the web: you come back to the right activity next time you open the app.

#### Where activities show up next

Once your activities are chosen, they come back in four places:

| Place | Role |
|---|---|
| The top-bar picker | Choose the one you're looking at |
| The [Trails](/en/docs/manage-trails) section | Choose which one to import into |
| A member's page | Restrict what a person sees |
| Task and structure types | Attach a type to one or more activities |

#### Who can change the list

Changing a place's activities falls under the place's **administration** rights — it is a structural setting, on a par with the place's information.

If you can see the section and its switches but saving is refused, that is the right you're missing, not the trails one.

#### One piece of advice

**Only turn on what you actually maintain.** Every active activity adds an entry to the picker, a column to the configuration screens and one more choice at every trail import. A "just in case" activity costs the whole team friction, every day. You can always switch it on the day the network exists.

### Difficulties: the colour of your trails

URL: https://trail-sentinel.com/en/docs/manage-trail-difficulties
Applies to: web, mobile

A trail isn't just a track: it's a **rated** track. The difficulty is what lets a user decide whether to commit to it, and what lets your crew know what they mean when they say "the black one".

In Sentinel that rating isn't a mere label. A difficulty level carries two things:

- **a symbol** — the circle, square and diamond of the North American trail-rating convention;
- **a colour** — the one that paints the trail's track on every map in the app.

Setting your difficulties therefore sets how your whole network looks, everywhere at once.

**Where:** left navigation bar, under **Administration** → **Trail Difficulties**.

#### The seven levels you get out of the box

When your place is created, Sentinel installs seven levels. You have nothing to do to get started: they're already there, already rated, already coloured.

| Symbol | Name | Colour |
|---|---|---|
| White circle | Easiest | `#E5ECF7` |
| Green circle | Easy | `#029443` |
| Blue square | More difficult | `#3498DB` |
| Black diamond | Very difficult | `#000000` |
| Double black diamond | Extremely difficult | `#000000` |
| Double orange diamond | Proline | `#E18501` |
| Purple triangle | Road access | `#854E85` |

That's the convention nearly every mountain-bike and ski network in North America uses. If yours already follows it, you probably have nothing to change.

Two structural points worth knowing right away:

**Difficulties belong to the place, not to the activity.** Unlike task types, which are attached to an activity, the difficulty list is single and shared by all of your networks. The black diamond on your bike network is the same object as the one on your ski network.

**The order of the list is a real setting.** It isn't cosmetic: it's what sorts your trails. A trail list is displayed from the top of the difficulty list down, then by name.

#### The list

The section lives under **Trails → Difficulties** in the sidebar.

_The place's difficulty list._
1. The drag handle — this is what reorders the list.
2. The badge shows the level's symbol on a background of its own colour.

Drag a row to change the order; it saves immediately, there's no button to confirm. Sort from easiest to hardest: that's the order your trails will then appear in across every list.

The search box at the top filters by name, which only becomes useful past a dozen or so levels — rare, but possible.

#### Editing a level

Clicking a row opens its page.

_A difficulty level's page._
1. The colour — this is what paints the trail's track on the maps.
2. The symbol picker, five shapes.

Three fields, with three very different reaches:

**The name** is purely a display. Renaming it is safe: trails don't point at the name, they point at a stable internal identifier. You can go from "More difficult" to "Intermediate" without a single trail moving.

**The colour** is the most visible of the three. It applies everywhere, immediately: the trail's line on the map, the badge in the lists, the group headers in the task table, the dashboard charts. Change the blue on "More difficult" and your entire intermediate network changes colour at once.

**The symbol** is picked from a grid of five shapes: circle, square, diamond, double diamond, triangle.

One useful note here: the grid only exposes five shapes, while the seven built-in levels use seven. The white circle on "Easiest" and the double orange diamond on "Proline" each have their own artwork, but **neither of those two is offered in the grid**. If you edit one of those two levels and change its symbol, you won't be able to get back from the interface. In practice: leave the symbol of those two alone if you care about their original look.

Nothing applies until you hit **Save**, and the app holds you back if you leave the page with unsaved changes.

#### Adding a level

The **Add a difficulty** button creates a blank level: a name, a colour, a symbol. It lands at the end of the list — remember to drag it to its real place in the scale.

Create one when your network has a category the North American convention doesn't cover: a "Shared trail", a "Family beginner loop", a "Seasonal closure". These are real cases, and a dedicated level beats a hacked-up trail name.

#### What deleting one breaks

This is the takeaway of this page.

**Deleting a level does not reassign the trails that used it.** Sentinel deletes the level and stops there. The trails that carried it keep pointing at an identifier that no longer exists, and it shows:

- on the web, the trail falls back to the **"Easy" symbol drawn in black**, and its difficulty name is displayed in its raw technical form;
- on mobile, it goes **grey**, with an information icon in place of the symbol;
- in every list sorted by difficulty, it **drops to the bottom**, whatever its real level.

Nothing is lost and nothing is broken in the strict sense — the trail still exists, it's simply orphaned from its rating. But the map becomes misleading, which is exactly what you're trying to avoid.

**So the procedure is the reverse of the natural order**: first reassign every affected trail to another level, from each [trail's](/en/docs/manage-trails) page, and delete the level afterwards. If you aren't sure a level is unused, rename it rather than delete it — that costs nothing and breaks nothing.

#### Where difficulties show up

Once your levels are set, they come back everywhere:

| Place | What you see |
|---|---|
| The map | The colour of each trail's track |
| The trail list | The symbol, the level's name, and the sort order |
| Tasks and structures | The symbol in the by-trail group headers |
| The dashboard | The breakdown of tasks by difficulty |
| Trail conditions | The symbol when picking trails for a report |
| Mobile | Track colours and the symbol on the detail pages |

That's what makes a colour change so visible: there's no single place to update, everything follows automatically.

#### On mobile

The section exists in the mobile app too, and it's complete — you can create, edit, delete and reorder there.

The path: **Account → your place → Trail Difficulties**.

_The difficulty list on mobile._
1. Tapping a row opens the level's page.
2. The floating button adds a level.

Three gestures specific to mobile:

- **A long press** on a row grabs it so you can drag to reorder.
- **A swipe sideways** on a row reveals delete, one level at a time.
- **Edit**, top right, switches to multi-select: checkboxes appear and you can delete several levels at once.

Those deletions have exactly the same consequences as on the web — the same caution applies.

#### Who can change the list

Difficulties fall under the **Trails** right in the place settings.

- With **read** access you see the section and the levels without being able to change them: the add and edit controls disappear.
- With **read and write** you can create, edit, reorder and delete.

It's the same right that governs trails and activities — which is consistent: all three describe the network itself. If you can see the list but nothing is editable, that's the right to ask for, in your [role](/en/docs/understand-roles).

#### Three pieces of advice

**Set them before importing your trails.** The import assigns a difficulty to every track; you may as well have it land on the right scale the first time.

**Keep the scale short.** Seven levels already cover almost every network. A fifteen-level scale is unmanageable in the field and unreadable on a map.

**Rename rather than delete.** It's the only operation in this section that is both useful and completely risk-free.

### Task types: the vocabulary of your maintenance

URL: https://trail-sentinel.com/en/docs/manage-task-types
Applies to: web, mobile

The **type** is the first thing you pick when creating a task, and the only piece of information you read from a distance. On the map a task is just a pin with an icon in it: the type is what draws that icon. In the table, it's what groups. In the [filters](/en/docs/use-advanced-filters), it's the most-used criterion.

In other words, your task types are the vocabulary your crew describes its work with. Too poor and everything ends up as "Other". Too rich and nobody finds the right one at creation time, in the rain, with gloves on.

**Where:** left navigation bar, under **Administration** → **Task types**.

#### Two families

Sentinel separates **predefined** types from **custom** ones.

The **nine predefined types** are installed when your place is created. They cover the universal trail problems:

| Type | What it means |
|---|---|
| Fallen Tree | A tree across the track |
| Erosion | Soil washing away |
| Water | Runoff, standing water |
| Mud | A mud hole |
| Broken Plank | A damaged boardwalk or decking |
| Drain | A blocked drain, or one to install |
| Sign | A missing, broken or unreadable sign |
| Other | Whatever fits nowhere else |
| Segment | A whole stretch, not a point |

You can't rename them, change their icon, or delete them. The only thing you set on them is **which activities they're offered in**.

**Custom types** are yours: a name, an icon, and the activities concerned. That's where the gestures specific to your network live — "Boardwalk to rebuild", "Pothole", "Missing marker".

#### The list

The section lives under **Task types** in the sidebar.

_The place's task types._
1. The count for each family.
2. The badges say which activities the type is offered in — "Inactive" when there is none.
3. The activity filter, to see only what concerns one network.

The two families are always shown separately, custom first. The search filters on the name, across both families at once.

#### Creating a custom type

The **Create Custom Type** button opens a three-field page.

_A custom type's page._
1. The icon — clicking it opens the picker.
2. The activities this type will be offered in.

**The name** is what the crew sees at task-creation time. Write the gesture, not the category: "Boardwalk to rebuild" gets picked faster than "Timber infrastructure".

**The icon** matters more than you'd think. It's what you see on the map, at 30 pixels, among fifty other pins. An icon clearly distinct from the nine predefined ones beats a subtle variant.

**The activities** decide where the type appears — that's the next section.

Nothing applies until you hit **Save**, and the app holds you back if you leave with pending changes.

##### The icon picker

_Picking an icon._
1. The search — it matches the icon's **English name**.
2. The chosen icon is outlined.

The catalogue holds **more than 700 icons**: Sentinel's twenty-four house drawings, plus two full libraries (Font Awesome and Material Community). The icon you're after is almost certainly in there.

One trap, and it matters: **the search works in English**. Type `bridge`, not `passerelle`; `snow`, not `neige`; `hammer`, not `marteau`. Icon names come from the source libraries and aren't translated.

#### Activities decide everything

This is the section's central mechanic, and it holds for both families.

A type is offered at task-creation time **only in the activities assigned to it**. If you're working in mountain biking, you only see the types ticked for mountain biking. That's what keeps the creation grid short and relevant.

Three practical consequences:

**A type with no activity is invisible.** It stays in the configuration list, marked with an **Inactive** badge, and stays editable — but nobody can create a task with it any more, and it drops out of the filters. Tasks already created with it keep their name and icon. Remember that: it's the retirement mechanism.

**There is no delete.** Once created, a custom type can't be erased — not from the web, not from mobile. That's deliberate: tasks already created with that type still exist and must keep a valid type. To take a type out of circulation, **untick all of its activities** and save. It disappears from the creation screens, and the history stays readable. The same move works at creation time: you can create a type with no activity — it starts out inactive and gets switched on later.

**Turning an activity on or off affects the predefined types.** When you disable an activity in the [Activities](/en/docs/manage-activities) section, its predefined-type configuration is dropped; re-enabling it makes Sentinel reinstall the nine types, **all ticked**. If you had unticked "Drain" for skiing, you'll find it ticked again. Custom types keep their setting intact.

#### The Segment case

"Segment" sits in the predefined list but doesn't behave like the others. It's the type for **linear** tasks: instead of dropping a point, you draw a portion of trail — a stretch to reshape, a section to brush out.

Two differences to know:

- In the creation screen it's presented **separately** from the other types, because the gesture that follows isn't the same: you draw a track instead of placing a pin.
- It is **unavailable** when you create a task from a [photo](/en/docs/create-a-task-from-a-photo) or from a point on the map. Both of those flows start from a single coordinate; there's no segment to derive from it.

This isn't a limitation to work around: if you need to describe a stretch, start from the create button rather than from the photo.

#### On mobile

The whole section exists on mobile: browse, create, edit.

The path: **Account → your place → Task types**.

_Task types on mobile._
1. The activity filter bar, if your place has more than one.
2. Tapping a row opens the type's page.

The content is the same as on the web — same two families, same activity badges, same 700-plus icon picker. Predefined types are likewise limited to the activity setting. A type with no activity is dropped from the mobile creation screens too; only the **Inactive** badge in the configuration list is web-only.

Mobile has the advantage of being on site: if your crew runs into a recurring case the current vocabulary doesn't cover, the type can be created during the outing rather than three weeks later.

#### Who can change the list

Task types fall under the **Task types** right in the place settings.

- With **read**: see the list, without the add button or editable fields.
- With **read and write**: create types, rename them, change their icon and their activities.

It's a right distinct from trails and activities. So you can hand the maintenance vocabulary to a field lead without giving them control over the network's structure. If access is missing, that's one to check in your [role](/en/docs/understand-roles).

#### Three pieces of advice

**Start with the nine predefined ones.** They cover the essentials. Wait and see what lands in "Other": that's your list of custom types to create, written by use rather than by theory.

**A dozen types, not thirty.** The creation screen shows a grid; past a dozen you stop choosing, give up, and pick "Other".

**Restrict the activities right at creation.** A type that only makes sense in winter has no business in the bike grid all summer. It's thirty seconds at creation time, and a shorter grid for everyone the rest of the year.

### Structure types: inspection questionnaires and numbering

URL: https://trail-sentinel.com/en/docs/manage-structure-types
Applies to: web, mobile

A **structure** is a fixed asset on your network: a bridge, a boardwalk, a culvert, a sign, a jump. Unlike a task, it is never finished — it exists, it ages, and it has to be inspected.

The **structure type** is what makes that inspection possible. It carries three things nothing else in Sentinel carries:

- **a questionnaire** — the questions you ask standing in front of the structure, with their relative importance;
- **automatic rescheduling** — how long until you come back, based on the score;
- **numbering** — the name pre-filled at creation: `PV-001`, `PV-002`, `PV-003`.

It's the richest section in the configuration, and by far the one that pays off most once it's set.

**Where:** left navigation bar, under **Administration** → **Structure types**.

#### Two families, same as tasks

Four types are installed when your place is created: **Bridge**, **Drain**, **Sign** and **Jump**. You can't rename or delete them; you only set which activities they're offered in — plus their questionnaire, their scheduling and their numbering, which are genuinely yours.

Custom types are yours from end to end.

_The place's structure types._
1. The types you created — the "Inactive" badge flags the ones left with no activity.
2. The four installed out of the box.

Activities behave **exactly as they do for [task types](/en/docs/manage-task-types)**: a type is only offered in the activities assigned to it, a type with no activity becomes invisible, and that's the only way to retire one since there is no delete.

Untick every activity, save, and the type drops out of the structure-creation grid, out of the *Type* field when editing, and out of the filters. It stays in this list, marked **Inactive**, and structures already placed keep their name and icon. One aside: numbering set for a retired activity is not erased — it sleeps, and picks up exactly where it left off if you tick the activity again.

A type's page has **four tabs**. The first, *Basic information*, holds only the name, the icon and the activities. The other three are the real subject of this page.

#### The evaluation questionnaire

This is the heart of it. A questionnaire turns "I looked at the bridge" into a score out of 100 and a risk level, comparable from one inspection to the next and from one structure to another.

_The Evaluation form tab._
1. While this box is unchecked, the type has no inspection at all.
2. **Copy from** pulls in another type's questionnaire — handy to start from an existing bridge.
3. The handle reorders the questions; that's the order they'll be asked in the field.

**Nothing exists until the box is checked.** A type without a questionnaire is still perfectly usable: the structure is placed on the map, you can see it, you can attach tasks to it. It simply has no inspection report.

**"Copy from" replaces everything.** The app confirms before doing it. It's meant for building a second bridge type in thirty seconds, not for merging two questionnaires.

##### Writing a question

_A question's page._
1. The **Safety question** box — its consequence is explained below.
2. The description is read in the field: this is where you write the rating scale.
3. Importance, in four steps.

**The title** is what you see in the list, in the field, small. Short and concrete: "Decking condition", not "Verification of deck structural integrity".

**The description** is the real instruction sheet. This is where you win comparability between two inspectors: write **what the ratings mean**. "Rate 1 if a plank gives way, 4 if the decking is sound" beats "Check the planks" a hundred times over. Without that sentence, two people rate the same boardwalk 2 and 4.

**Importance** has four steps, and they're real weights in the calculation:

| Step | Weight |
|---|---|
| Low | 5 |
| Medium | 10 |
| High | 20 |
| Very high | 30 |

A "Very high" question therefore weighs **six times** a "Low" one. It isn't a decorative ranking.

##### How the score is computed

In the field, every question is rated **1 to 4**, or marked **not applicable**.

The calculation is exactly this:

```
score = Σ (rating − 1) × weight   ÷   Σ 3 × weight   × 100
```

Three consequences that surprise people who don't know them:

**All ones give 0, not 25.** The scale starts at 1; it's `rating − 1` that counts. The worst possible result really is zero.

**"Not applicable" removes the question from both sides of the division.** It neither penalizes nor rewards: it disappears. A missing handrail on a boardwalk at ground level doesn't drag the structure's score down.

**An unanswered question counts as 1.** It's treated as the worst rating, not as "not applicable". If a question never applies to a structure, tick "not applicable" rather than skipping it.

The score then falls into a risk level:

| Score | Level |
|---|---|
| 80 and above | No risk |
| 60 to 79 | Low risk |
| 40 to 59 | Medium risk |
| Below 40 | High risk |

##### The safety question

A question marked **Safety question** has veto power: if it gets **1 out of 4**, the structure is classified **high risk**, whatever the score.

That's the mechanism that stops the arithmetic from lying. A bridge whose anchors are failing but whose everything else is spotless would post a perfectly decent score — and be declared sound. Mark "Anchors and footings" as a safety question and it goes high risk, as it should.

Reserve it for what hurts someone. Two or three per questionnaire, not eight.

#### Automatic rescheduling

The tab only appears **if the questionnaire is active** — it would have nothing to schedule otherwise.

_The Automatic scheduling tab._
1. Unchecked, the next report's date is entered by hand at every inspection.
2. One delay per risk level, in days or months.

When it's on, the next report's date is computed when the inspection closes, from the risk level obtained. A sound structure reschedules far out; a high-risk one comes back in two weeks.

This is the setting that turns inspections into a **cycle** rather than a chore you forget. Set it once, and the list of structures due builds itself.

The delay is expressed in **days** (1 to 30) or **months** (1, 2, 3, 4, 5, 6, 9, 12, 18, 24). For high risk, use days: a dangerous structure doesn't reschedule in months.

#### Numbering

In the field, the person placing a trail's thirtieth marker doesn't want to decide what it's called. Numbering hands them the name up front.

_The Numbering tab._
1. One card per activity — numbering is set activity by activity.
2. Prefix, separator, number of digits.
3. The preview shows the next three names, live.

**The setting is per activity and per type.** "Boardwalk in mountain biking" and "Boardwalk in hiking" are two independent series, with different prefixes if you want.

Three fields:

- **Prefix** — up to 16 characters. `PV`, `BRDG`, `DR`.
- **Separator** — hyphen, underscore, dot, space, or none.
- **Digits** — 1 to 10. With 3 you get `001`. Choose based on how many structures you expect, not how many you have today: going from `PV-99` to `PV-100` breaks alphabetical sorting, `PV-099` then `PV-100` doesn't.

##### The scope: per trail, with off-trail on its own

This is the most important point in the section, and the least obvious.

The series **restarts at 1 for each trail**. The first boardwalk on "La Coulée" is `PV-001`, and the first boardwalk on "Le Belvédère" is also `PV-001`. **Off-trail** structures form a separate series of their own.

That's deliberate, and it matches how people talk in the field: "the second boardwalk on La Coulée", not "boardwalk number 47 on the network". If you wanted a single network-wide numbering, this won't give it to you.

##### It's a derivation, not a counter

Sentinel stores **no counter**. On every creation it looks at the names of existing structures of the same type, on the same trail, reads the highest number in the series, and offers the next one.

Four practical consequences:

**A deleted number gets reused.** Delete `PV-003` when it was the last one, and the next boardwalk will be called `PV-003` again. There's no permanent gap.

**The offered name is only a suggestion.** You can replace it. The app simply warns you if the name is already taken on the same trail.

**Changing the separator restarts the series.** Recognition requires the separator to match. After switching from `PV-001` to `PV_001`, the old names are no longer seen as part of the series, and the next name offered will be `PV_001`. The prefix, on the other hand, is compared **case-insensitively**: `pv-004` does continue on from `PV-003`.

**With no rule at all, Sentinel still continues an existing series.** If your structures are already named `Bridge 12`, `Bridge 13`, the next will be offered as `Bridge 14` without you configuring anything. The rule exists to *impose* a shape, not to switch the mechanism on.

Finally: **unticking an activity turns the suggestion off**, it doesn't reset it. The name field will simply be empty at creation.

#### On mobile

The mobile app carries the type list, creation, editing, and **the full questionnaire editor** — questions, importance, safety questions, scheduling.

_Structure types on mobile._
1. The two families, same as the web.
2. Tapping opens the type's page.

The path: **Account → your place → Structure types**.

One thing is missing: **the Numbering tab doesn't exist on mobile**. Mobile *uses* the rules — the name does arrive pre-filled when you create a structure, including **offline**, by reading the structures already cached and the ones sitting in the sync queue. But prefixes are only set from the web.

#### Who can change all this

Structure types fall under the **Structure types** right in the place settings.

- With **read**: see the types, the questionnaires and the rules, change nothing.
- With **read and write**: everything described on this page.

It's a right distinct from structures themselves: someone can inspect structures all season without ever being able to touch the questionnaire — and that's usually exactly what you want, because changing weights mid-season makes inspections incomparable. See [roles](/en/docs/understand-roles).

#### Four pieces of advice

**Write the rating scale into the description.** It's the single gesture on this page that decides whether two inspectors give the same structure the same score.

**Two or three safety questions per type.** Beyond that, everything lands on high risk and the classification stops meaning anything.

**Freeze the weights before the season starts.** A score is only comparable over time if the questionnaire hasn't moved.

**Set the numbering before the first outing**, not after. Renaming thirty boardwalks by hand is a lost afternoon; ticking a box takes ten seconds.

### Invite a member and give them the right access

URL: https://trail-sentinel.com/en/docs/invite-and-manage-members
Applies to: web

The **Members** section lists everyone who has access to your place. It also shows **pending invitations** — people you invited who haven't accepted yet. That is useful: an invitation still pending after two weeks is usually a misspelled address.

Each member carries three things: their **role** (what they may do), their **activities** (what they may see) and their **groups** (who work gets assigned to). These are three different questions, and mixing them up is the most common source of confusion.

**Where:** left navigation bar, under **Administration** → **Members**.

#### Inviting someone

The **Invite member** button opens a window that asks for everything at once.

_The invitation window._
1. The email. It is the only required field.
2. Groups, optional. They are applied automatically when the person accepts.
3. The activity restriction. Unchecked, the member sees every activity in the place.
4. The role. One per member.

Everything you set here is **attached to the invitation**, not applied right away. The role, activities and groups take effect the moment the person accepts. So there is nothing to redo afterwards.

#### What reaches the invited person

It depends on one thing: do they already have a Sentinel account?

**They already have an account and already work in a place.** The invitation appears directly in their app, under the notification bell. They also get a push notification on their phone and an email — depending on what they enabled in their notification preferences.

**They don't have an account yet, or don't belong to any place.** They get an email with a link. Once they enter their address and their verification code, your invitation greets them on their landing screen with an **Accept** button — there is nothing to hunt for.

That is why an invitation can stay pending for a while without anything being broken: the person still has to act on their side.

#### How the person accepts

Either way the gesture is the same: **Accept** brings them into the place, **Decline** removes the invitation with no other effect.

_The notification bell and the invitation received._
1. The badge shows how many invitations are pending.
2. Accept brings the person into the place. Decline removes the invitation, with no other effect.

The moment they accept, Sentinel **switches their active place** to yours and applies the role, activities and groups from the invitation in one go. They land straight in the right context, with the right permissions.

A person can belong to several places: accepting your invitation does not make them lose the others, it simply changes the one they are looking at.

#### Choosing the right role

The role answers the question: **what is this person allowed to do?** Three roles exist out of the box:

| Role | For whom |
|---|---|
| **Viewer** | Can only look at tasks and projects. For a partner or an official you want to give visibility to |
| **Editor** | Can create, edit and assign tasks and projects. This is the role for most of the field team |
| **Admin** | Can also manage place settings, the subscription, and invite other members |

A member has **only one role**. If none of the three fits, the **Roles** section lets you build a custom one, with the access level you want section by section.

When in doubt, give **Editor**. The role can be changed at any time from the member's page, and the change is immediate.

#### Deciding on activities

This is the most misunderstood setting, because it is not about permissions but about **scope**.

If your place runs several activities — mountain biking, hiking, cross-country skiing — each has its own trails, tasks and conditions. The activity restriction decides which ones the person sees.

**Unchecked (default):** the member has access to **every** activity in the place, including ones you add later. That is what you want most of the time.

**Checked:** you pick the activities, and you must select **at least one**. The member will only see those. Useful for a ski club volunteer who has no business in the biking tasks, or for a contractor hired on a single network.

Worth remembering: **role and activities combine**. An Admin restricted to cross-country skiing can do everything — but only in cross-country skiing.

#### A member's page

Click a row in the list to open their page. The header reminds you who it is — avatar, name, email — and three tabs split the rest.

##### Informations: changing access

This is where you change what was decided at invitation time.

_A member's Informations tab._
1. The page's three tabs.
2. The same three settings as in the invitation: groups, activities, role.
3. Nothing is applied until you click Save.
4. The danger zone, kept apart at the bottom, to remove the person from the place.

Changes only go out when you **save**. If you try to leave the page with unsaved edits, the app stops you and asks what to do — you don't lose your work to a stray click on "Back".

The **Remove member** button asks for confirmation before acting. It takes the person out of the place: their Sentinel account stays intact, and so do their tasks and history. They simply lose access to your place.

##### Recent activity: what the person did

_The Recent activity tab._
1. The coloured square shows the kind of action: blue for a creation, green for an edit, orange for a deletion, grey for everything else (a lookup, an export, a checklist launch).
2. The date and time of each action.

This is the log of that member's actions in your place: task creations, assignments, trail updates, structure reports, checklists launched or ticked off, conditions published, file deletions. Nothing is editable here — it's a record, not a tool.

Two concrete uses: understanding **who changed what** when a piece of data surprises you, and checking that a new hire actually got to grips with the tool in their first weeks.

##### Time log report: hours worked

_The Time log report tab._
1. The year's total, at the top.
2. The breakdown by trail — then, further down, by task type.

This report aggregates the **time entries** the member logged on their tasks. So it only fills up if the team records its time: with no entries, the tab stays empty.

Three breakdowns: a chart of time by month, the split by trail, and the split by task type. That is what you need to answer "how many hours did we put into La Coulée this year?" or to back up a report to a funder.

#### Who can do all this

You need write access to **Members** to invite, change a role or remove someone. With read-only access the section stays visible but the controls are disabled — that is deliberate: seeing who is on the team is useful to everyone, changing access is not.

If the **Invite member** button doesn't appear for you, that is the right you're missing.

### Groups: assigning work to a crew rather than a person

URL: https://trail-sentinel.com/en/docs/use-groups
Applies to: web

Some tasks have an obvious **who**. Others only have an obvious **which crew**. "The Saturday crew will handle it" is useful information; assigning it to a random person just to feel organized is not.

A group gathers members of your place under a name and a colour. Once created, it becomes an assignment target just like a person.

**Where:** left navigation bar, under **Administration** → **Groups**.

#### What it actually gets you

**Assigning without naming.** In a task's **Assigned to** field, groups appear alongside people. You pick "Saturday crew", and the task belongs to the crew.

**Reading the board at a glance.** On the kanban, a task assigned to a group shows a chip with the group's initials in its colour, with a small team icon. A task assigned to a person simply shows their name. You can tell them apart without opening the card.

**Setting access up in advance.** You can put someone into one or more groups **at invitation time**: the groups apply on their own when the person accepts.

A person can belong to **several groups** — an employee can be in both "North team" and "Bike patrol".

#### The group list

_The Groups section._
1. The group's colour and name. The colour is your landmark everywhere else in the app.
2. The member count.
3. Create a group: a name, a colour, that's it.

Pick clearly different colours. Two close greens look the same on an 18-pixel chip in a kanban.

#### Creating or editing a group

Click a row to open the group's page.

_A group's page._
1. The name and colour, editable at any time.
2. Every member of the place appears with a switch: on means they're in the group.
3. The danger zone, to delete the group.

The member list is the **whole place**, not just the group: you add and remove with the same switch, without changing screen. The search field above filters by name when the team is large.

As elsewhere in the app, nothing applies until you hit **Save**.

Deleting a group is **irreversible**. Members are untouched — they simply lose their membership in that group.

#### Three ways to change who's in a group

It is the same data, editable from three places depending on what you have in front of you:

| From | When it's handy |
|---|---|
| **The group's page** | You're building a crew: several people at once |
| **A member's page** | You're dealing with one person: all their groups at once |
| **The invitation** | The person hasn't arrived yet |

None of the three is "the right one" — they all write to the same place.

#### What a group does not do

This is the confusion to avoid, especially right after setting up roles.

**A group grants no permissions.** It does not replace the role and does not change it. Putting someone in "North team" gives them nothing extra: their permissions come only from their role, and their scope only from their activities. A group is an **organizational label**, not an access level.

**You can't filter by group yet.** The "Assigned to" filters list people. To find a crew's work, go by colour on the kanban.

#### Who can manage groups

Creating, editing and deleting a group needs write access to **Groups**. If the section doesn't appear in your sidebar, that is the right you're missing.

One subtlety: changing a person's groups **from their member page** falls under the **Members** right, not the Groups right. So someone who manages the team can reassign a member's groups without having access to the Groups section itself.

### Roles: deciding what each person can do

URL: https://trail-sentinel.com/en/docs/understand-roles
Applies to: web

The role is the only thing that grants permissions in Sentinel. Not the group, not the activity, not seniority: **the role, and nothing else**. That is why it's worth understanding how it works before hand-rolling one.

Every place starts with three roles: **Viewer**, **Editor** and **Admin**. For many organizations that's enough. You only need a custom role when someone must do *a bit more* than Viewer without getting *everything* Editor has.

The names and descriptions of those three roles can't be changed — they're translated automatically, and renaming them would break that. You can change their permissions, though, and create as many roles as you like.

**Where:** left navigation bar, under **Administration** → **Roles**.

#### Read a role before editing it

The editor opens with a summary, before the role's own name. Get into this habit: **read the summary rather than the grid**.

_The \_
1. A computed characterisation of the role — Full access, Read-only access, Partial access, Limited access…
2. The count: how many of the 20 permissions.
3. One line per domain, with its level. Exceptions appear underneath, in orange.

All twelve domains are **always shown**, including the ones at "None". Nothing is hidden: what is denied reads in its place, which keeps you from concluding too fast that a role grants less than it does.

The characterisation at the top is more than a count. A role that touches many domains but **only in read mode** is described as "Read-only access" rather than "Near-full access" — because that's the useful information.

The "except X" notes are filtered: an option is only flagged as off if it *could* be turned on as things stand. No point announcing "except Bulk edit" on a read-only role, where that option is structurally unavailable.

#### The twenty controls

_The permission editor._
1. The template bar: start from Viewer, Editor or Admin, then adjust.
2. The three-level selector — None, View, Edit.
3. The finer capabilities, as switches, nested under the area they depend on.

Twelve **three-level selectors** — None, View, Edit — for the big domains: Tasks, Projects, Structures, Checklists, Trails & Configuration, Trail Conditions, Members, Groups, Roles, Invitations, Billing, Administration.

Eight **switches** for specific capabilities attached to those domains: Time, Bulk edit, Export, Structure reports, Check off items, Discussion, Dashboard, Planification.

A template bar at the top lets you start from Viewer, Editor or Admin and then adjust. Careful: **applying a template replaces the whole configuration**, with no confirmation. Changed lines flash so you can see the scale of what just happened.

#### The surprising part: permissions depend on each other

This is the heart of it. You can't grant "Projects" without granting at least "View" on Tasks — a project is a bundle of tasks, the screen would be empty. About thirty links like this exist in the app.

Sentinel never blocks a control over it. It does two things instead:

**When turning something on**, it raises whatever is missing. A "Will also enable…" chip warns you beforehand, and automatically raised lines flash — even when they're off-screen.

**When turning something off**, it shows you the consequences and asks for confirmation.

_The impact panel, when removing a permission others depend on._
1. The level: None, View or Edit.
2. The lock chip lists what depends on this domain. Click it to see the impact.
3. Nothing is written until you confirm.

So no control is ever greyed out. You can always cut everything — you're simply shown the price first.

##### The dependencies you'll actually hit

| To turn on… | you need at least |
|---|---|
| Projects | Tasks at View |
| Time, Export | Tasks at View |
| Bulk edit | Tasks at **Edit** |
| Structure reports | Structures at View |
| Check off items | Checklists at View |
| Discussion | Tasks, Projects **and** Structures at View |
| Invitations | Members at **Edit** |
| Planification | Tasks at Edit, Groups at Edit, Members at View |

Four controls depend on nothing and condition nothing: **Dashboard**, **Trails & Configuration**, **Billing** and **Administration**. They're the only ones you can set in isolation without side effects.

One special case is worth knowing: setting **Checklists to Edit always turns on "Check off items"**, and it can't be undone. That's deliberate — server-side, managing checklists already authorises ticking. The state "manages checklists but can't tick" does not exist; showing it would make the screen lie.

##### Your choices don't get erased on their own

Sentinel remembers **what you chose yourself**, separately from what a dependency raised. When a cascade steps back down, it only lowers what you never set by hand.

Concretely: if you deliberately set Members to "View", turning off an unrelated switch later won't wipe it.

#### The guard that keeps you from locking yourself out

Sentinel refuses to remove role management from the **last** role that has it and has members. Without that guard, one bad move would make the Roles section permanently unreachable — nobody could undo it.

In the same spirit, editing **your own role** to remove your roles access triggers an explicit confirmation. Read it before clicking.

#### Assigning roles to your members

The **Members** tab of the Roles section shows a board: one column per role, one card per person. You change someone's role by dragging their card from one column to another.

Dropping someone into a **privileged** role — one that manages roles, billing or account settings — asks for confirmation. That's the kind of mistake nobody notices for a long time.

Changes are **immediate**: the person sees their permissions change without signing out, even while using the app.

#### Deleting a role

A deleted role doesn't take its members with it: they are **reassigned to the base role** (Viewer), and their new permissions apply right away. The base role itself can't be deleted.

#### Three pieces of advice

**Start from a template.** Pick Viewer, Editor or Admin, then adjust. Building from scratch walks you through inconsistent intermediate states that the cascade will fix behind your back.

**Re-read the summary before saving.** That's what it's for. If the characterisation at the top doesn't match what you intended, something got past you.

**Don't create one role per person.** A role describes a function, not an individual. If you're at seven roles for nine people, it's probably the activity or the group that needed adjusting, not the permissions.

### Planning: splitting the work person by person

URL: https://trail-sentinel.com/en/docs/plan-member-work
Applies to: web, mobile

The task board answers "what is there to do". **Planning** answers the other question, the Monday-morning one: **"who's doing what this week?"**

Same material — your tasks — turned around. Instead of a list per trail or per project, a board per person.

**Where:** left navigation bar, under **Administration** → **Planning**. Your own board is under **General** → **My planning**.

#### Choosing who you're looking at

The section opens on the list of people you can assign to, in two tabs.

_The list of members and groups._
1. The two tabs, with the number of members and groups.
2. One row per assignee — open it to see their board.

**Members** are the people in the place. Search matches the name **and the email**, which helps when two people share a first name.

**Groups** are your crews. A group is planned exactly like a person: it has its own board, and a task handed to it belongs to the crew rather than to anyone in particular. That's the right tool for "the Saturday crew" — see [groups](/en/docs/use-groups).

#### An assignee's board

_A member's board, with the task panel open._
1. The five status columns, each with its count.
2. The panel of tasks to assign, opened from **Add → An existing task**.
3. The search, the three filters and the counter: you always know how many tasks you're looking at.

The board shows that person's tasks in their status columns, and you drag them from one column to the next like on any kanban.

What's specific to this screen is the **task panel**. It opens from the **Add → An existing task** menu, and it lists the place's tasks that aren't already handed to someone else. **Dragging a task onto a column does two things at once**: it assigns it to the person *and* puts it in that status.

That's the gesture the whole section is built around. Splitting twenty tasks takes a minute, instead of twenty round trips through task pages.

##### Finding the right task

At the top of the panel, a **search field**. Its placeholder tells you what it covers — "Name, type, trail, folder, project…" — because it isn't guessable: typing *La Coulée* or *Spring opening* works just as well as a task name. The description is searched too.

Type three letters and the list narrows as you go. The counter to the right of the filters always tells you where you stand — "6 of 87".

Below the field, three buttons cover all the filtering:

- **Folder** — for the free tasks you've filed by job. "Give him the Spring opening folder" is the Monday-morning gesture.
- **Filters** — everything else behind a single button: status, trail, priority, type, **project**, reporter, assignee. The number on the button counts the active filters inside.
- **Dates** — creation or completion dates.

The cross clears everything at once.

##### Two ways to read the list

The button to the right of the search field switches between two layouts, and your choice is remembered:

- **The compact list** (default) — one line per task: its type, its name, its folder, its trail, the person it's already handed to. Around fifteen tasks on screen, which is what you want when splitting a big batch.
- **Detailed cards** — each task with a **map thumbnail** centred on it. Three per screen, but you see where the work is: that's what lets you group a job geographically rather than by whatever the titles happen to say.

##### Three shortcuts

- **Double-click** a task to add it straight as *New*, no dragging.
- **Shift + click** selects several tasks, then a single drag assigns them all — the badge on the drag preview tells you how many you're carrying.
- Hover a task and press **Space**: it opens in a window without leaving the board.

The panel **fades out while you drag**, so you can see the columns. It comes back when you drop.

It's the same panel in [projects](/en/docs/use-projects) and in "My planning": what you learn here serves all three screens.

##### Project tasks are here too

A person's board shows **all of their work**, whether it belongs to a project or not. A task from "2026 season opening" handed to Marc appears on Marc's board, with **a badge naming the project** so you know where it comes from.

The two readings coexist without contradicting each other:

| The question | Where to ask it |
|---|---|
| How is this job going? | The [project](/en/docs/use-projects) kanban |
| What's on Marc's plate? | The person's kanban, here |

It's the same task seen from two angles. Moving it between columns on one screen moves it on the other.

The panel's **Project filter** is there for exactly that: "give him the three tasks from the North bridge project" takes two clicks.

Two quieter omissions:

- the board only shows the **current activity**, as everywhere else;
- the panel doesn't offer **to-dos** — only tasks placed on a point or a trail segment.

Worth noting: inside a [project](/en/docs/use-projects), the panel works the other way round — it only offers **free** tasks, since its job is to attach them to the project. A task already attached elsewhere doesn't show up there.

##### The Done column

The fifth column shows no cards: it shows a message. Dropping a task on it marks it **done**, and it leaves the view immediately.

Nothing is lost: a member's board is a working surface, not a history. To find what has been completed, use the [status filter](/en/docs/use-advanced-filters) in the Tasks section.

#### My planning

The other side of the same material: what **you** have to do. It's a separate section, at the top of the menu, and everyone has it.

_The \_
1. The filter decides what the board contains.
2. Your groups are listed below, one by one.

By default the board shows **everything that falls to you**: what is assigned to you personally **and** what is assigned to the groups you belong to. That's the "All" setting.

The filter lets you narrow it down:

- **All** — your tasks and your groups';
- **Me only** — just what carries your name;
- **a specific group** — just what is handed to that crew.

"Me only" is the right setting when a crew shares a lot of tasks and you want to know what is personally yours. To tell the two apart at a glance, cards that came through a group carry **a badge with the group's name**.

The same task panel is here, with one meaningful difference: whatever you pull from it **is assigned to you**, never to the group — even when the filter is set to a group. It's a tool for taking work, not for handing it out.

Like a member's board, "My planning" shows **everything** that comes your way, project tasks included.

#### In the field

Mobile carries **"My planning"** as one of the view-switcher views, alongside Field, conditions and checklists.

_My planning on mobile._
1. The status on screen, with its task count — tap it to jump to another.
2. The dots say where you are among the four columns; swipe to move.

The screen shows **one column at a time**: on a phone, that's the right format. Swipe to reach the next one, or tap the status name to jump straight to the right one. There are four columns — New, Ready, In Progress, On Hold — and **no Done column**: in the field, finishing a task takes it out of the list.

Two things to know:

**It works offline.** The list is cached: you leave in the morning with your day in your pocket, and it stays readable without a network. What you do in the field goes back into the sync queue as soon as the network returns.

**There is no crew planning on mobile.** Assigning other people's work is done from the web. Mobile shows what falls to you, personally and through your groups, with no filter: the equivalent of the "All" setting.

#### Who can plan

Crew planning falls under the **Planning** right in the place settings, and it requires the **read and write** level: without it the section doesn't appear at all. That's consistent — a board where nothing can be moved would have no use.

"My planning" has no right of its own: being able to read tasks is enough, which is true of nearly everyone. It's your own work.

See [roles](/en/docs/understand-roles) to grant the planning right.

#### Three pieces of advice

**Assign to a group when the person doesn't matter.** "The Saturday crew" beats picking a name at random and changing it three times. Everyone will see the task in their own planning.

**Use the panel, not the task pages.** Opening twenty tasks to assign them one by one is the slowest route. Search, filter by folder or project, Shift + click, one drag, done.

**Switch to detailed cards to split a sector.** When the place matters more than the name, the map thumbnails help you hand someone a batch of tasks that are all in the same spot. For everything else, the compact list is faster.


## FAQ

### General

#### Does it work without Internet?

Yes. Sentinel saves your data locally and syncs automatically when you're back online.

#### What size organization is this for?

From 2 volunteers to 50 employees. The offering adapts to your needs.

#### Is my data secure?

Absolutely. Hosted in Canada, end-to-end encryption, and compliant with Canadian standards.

#### Can I export reports for insurers?

Yes, in PDF or Excel, with timestamped and geolocated photos.

#### Who uses Trail Sentinel?

Organizations that maintain trails: network managers, outdoor centers, bike centers, resorts, sport clubs and municipalities. Among them, Stowe Trails Partnership and Slate Valley Trails in Vermont, Copper Harbor Trails in Michigan, Sentiers du Moulin, Mont-Sainte-Anne and Contact Nature in Quebec, and Val d'Isère in France. The full list is on the customers page.

#### Is Trail Sentinel only for trails?

Trails are the core of the product, but the model — geolocated tasks, inspected structures, projects, checklists — applies to any outdoor territory that needs upkeep. Contact Nature, a conservation organization in Quebec, uses it for its hiking, snowshoeing and cross-country ski trails, but also for its ice fishing villages and the 92 fishing pools of a salmon river. Same tasks, same infrastructure inspections, same quality controls, on different objects.

#### Is Trail Sentinel used outside Canada?

Yes. Trail Sentinel is used in Canada, in the United States — including Vermont and Michigan — and in Europe, with Val d'Isère in France. The interface is available in English and French.

#### Does Trail Sentinel handle ATV and snowmobile trails?

Yes. ATV (quad) and snowmobile are two of Trail Sentinel's eleven activities, alongside mountain bike, hiking and cross-country skiing. A motorized club tracks its ruts, culverts, drainage and signage the same way a bike club tracks its trails — on the same map, with the same field app that works without coverage. Off-highway vehicle (OHV) networks are managed the same way.

### Platform

#### Can I map an entire trail network in one tool?

Yes. Sentinel shows your whole network on one interactive map, with every task and structure geolocated. The map works on web, iOS and Android, and stays usable offline in the field.

#### What should a trail organization look for in trail mapping software?

A map of the full network, geolocation of tasks and structures, an offline mode for the field, and exportable reports for partners and grants. Sentinel brings these together in a single web and mobile platform.

#### What types of tasks can I create?

A point marker (a fallen tree, a broken sign) or a segment over a distance (eroded zone, drainage to redo). Both formats cover the vast majority of maintenance issues.

#### Can a task be assigned to multiple people?

Yes. A task can be assigned to an individual or a group, depending on your organization.

#### What happens to a closed task?

It stays in the trail's history, viewable at any time. Useful for proving maintenance was done, or for detecting a recurring problem at the same spot.

#### Does it work without network?

Yes. You can create tasks, take photos and document without any cellular network. Everything syncs automatically as soon as signal returns.

#### What does Sentinel consider a "structure"?

Any permanent physical infrastructure on your network: bridges, walkways, stairs, lookouts, signs, tables, benches, shelters. You choose the types that apply to you and can add more.

#### Can I create my own inspection forms with my own questions?

Yes. You build your questionnaires from the web dashboard: free text, multiple choice, checkboxes, photos, severity levels. You can have a different form per structure type, or a universal form.

#### Do I have to fill out a form to document an inspection?

No. You can also do a free-form inspection: a few notes, a few photos, and it's in the file. The form provides structure when useful, the free-form inspection gets the job done when it's not.

#### Are the PDF reports branded with my organization?

Yes. Your logo appears on the PDF produced. It's ready to use for your partners, insurers, grant applications — no rework in Word needed.

#### How many projects can we have in parallel?

No limit. You can have one project per worksite, one per season, one per grant — all at the same time.

#### Can a task belong to multiple projects?

No. Each task belongs to one project at a time, to keep progress clear. You can move it from one project to another if needed.

#### Can we manage a budget per project?

For now, Sentinel focuses on progress (tasks done versus total tasks) and time invested. Dollar-based budget tracking is not yet integrated — we're working on the next version.

#### Do messages disappear when a task is closed?

No. The discussion stays attached to the task, even closed. You can still browse it from history — photos, audio and text included. Perfect for audits or lessons learned.

#### Can volunteers and external partners take part in discussions?

Yes, if their role allows it. You stay in control: a volunteer can take part in the discussions of tasks assigned to them, but not in projects they're not attached to.

#### Why use this instead of a Slack or Messenger group?

Because an external chat isn't tied to anything. Six months later, finding a specific message about a fallen tree takes an hour. In Sentinel, you open the task and the whole conversation is there, with photos and context.

#### Can I create multiple condition boards?

Yes. You create as many boards as activities — mountain biking, hiking, cross-country skiing, fatbike. Within each board, you group your trails by type or level using folders (enduro, cross-country, flow trail, for example). It's your network, your structure.

#### What statuses can I apply to a trail?

Three simple statuses: Open (trail rideable), Work in progress (active maintenance, with optional location) and Closed (inaccessible). You can also apply a status to an entire folder in one move — handy at season start and end.

#### Do conditions update automatically when someone works on a trail?

When a crew member sets a task to "In progress" on a trail, the app offers to flip the trail condition to "Work in progress". One tap, and your visitors see the update, with the work location pinpointed on the trail. When the task is completed, the app can also suggest reopening the trail. You stay in control, the app handles the reminders.

#### How do I embed the condition widget on my website?

You copy two HTML tags generated by Sentinel and paste them on any page of your site — WordPress, Wix, Squarespace, custom code. The widget shows up, updates automatically, and you can customize it: header colors, language (French or English), map display, shadows, rounded corners. No API to manage. And on platforms that block external scripts (SharePoint, strict-security intranets), an iframe version embeds with a single link.

#### What is a checklist used for in Sentinel?

To run the same series of checks across several trails at once: season opening, periodic inspection, brush clearing, grooming, closing. You write the list once, pick the trails, and Sentinel creates one checklist per trail. You then follow the whole network's progress on a single screen, instead of a shared file nobody opens in the field.

#### Do I need a template before I can start a checklist?

No. A template is a convenience, not a requirement: it saves you retyping the same list every season. If you don't have one yet, you type the items straight into the creation wizard. You can keep several named templates side by side — one per kind of operation.

#### Can a checklist restart on its own?

Yes. You set a frequency — weekly, monthly or yearly — and the next copy is created on the scheduled date, with the same items and the same trails. You decide when the repetition stops: never, on a date, or after a number of occurrences. It is built for recurring rounds: culvert checks, signage verification, weekly network sweeps.

#### Can I manage a summer network and a winter network in the same account?

Yes, and that is the normal setup. Each activity is a watertight partition: its trails, tasks, structures, types and condition board belong to it alone. A club that maintains bike trails in summer and snowmobile trails in winter switches on both activities and moves between them — the summer map never shows the winter routes, and the analytics never mix the two seasons.

### Team

#### How many members can we invite?

As many as you want. There's no limit on the number of members in Sentinel — invite your entire team, your volunteers, your partners and your contractors with no extra per-user fees.

#### Can a member belong to multiple organizations?

Yes. A technician can work for two different clubs with the same Sentinel account. They switch between networks directly from the app, without having to log in again.

#### How do we manage seasonal volunteers?

Invite them with a limited role for the season. At the end, you simply disable their access. Their contribution stays in the network history — photos, reports, time invested.

#### What about external partners (municipality, contractor)?

Give them a Viewer role on the activities that concern them. They see what they need to see, nothing more. Perfect for transparency without risk of error.

#### Can someone tick items without being able to manage checklists?

Yes. The "Checklists" role has four levels: no access, view, view with the right to tick, and full management. A seasonal volunteer can tick their round without being able to create, duplicate or delete a checklist. Managing templates is a separate permission, kept for administrators.

#### Can volunteers use Trail Sentinel alongside paid staff?

Yes, and it is a common setup. Roles and permissions decide what each person sees and can change: a seasonal volunteer can view and complete their tasks without reaching network administration. Stowe Trails Partnership, in Vermont, uses it for exactly that — easing communication between volunteers and staff around trail projects. Contact Nature goes one step further and shares access with certain active users who work directly alongside its teams in the field, on top of its employees and volunteers.

### Field

#### How accurate is the GPS tracking?

Modern smartphones provide GPS accuracy within 3-5 meters under open sky conditions. In dense forest, accuracy may decrease to 10-15 meters, but that's still precise enough to locate any trail feature. Sentinel also lets you fine-tune the pin location manually if needed.

#### Does GPS tracking drain my phone battery?

Sentinel uses smart GPS management. Location is only captured when you create or view a task, not continuously. This means minimal battery impact — you can work a full day in the field without worrying about your phone dying.

#### Can I use GPS tracking without internet?

Absolutely. GPS works independently of cell service. You can create GPS-tagged tasks anywhere, and they'll sync to your team when you're back in coverage. Pre-load your trail maps before heading out for the best experience.

#### Can I import existing trail data?

Yes. Sentinel supports GPX file imports, so you can bring in your existing trail network data. You can also export your task data for use in GIS applications or reports.

#### How long can the app stay offline?

Days, even weeks. As long as you don't reinstall the app, the data stays on your phone and syncs on the next connection.

#### Does the app drain the battery?

No. The app is optimized to use GPS only when needed — when creating a task or viewing a specific point, never continuously in the background. Battery consumption stays very low, even during a full day in the field.

#### Does it work on Android and iPhone?

Yes, both. Same features, same performance. Download from the App Store and the Google Play Store.

#### Can items be ticked without cell coverage?

Yes. The mobile app keeps campaigns, trails and items readable offline. A tick made without coverage shows up immediately and goes into the sync queue; it is replayed as soon as the connection is back. Nobody has to jot anything on paper to re-enter it later.

#### How does maintaining a motorized trail differ from a bike trail?

The corridor is wider, damage shows up as ruts and surface erosion rather than exposed roots, and built works — culverts, bridges, gates, regulatory signage — take a bigger share of the budget. In Trail Sentinel that means segment tasks rather than point markers for drainage and grading, a structure inventory with its inspection history, and exportable reports for landowners and grant applications.

### Data

#### What export formats are available?

PDF (formatted reports), Excel (raw data), CSV (for external analysis). Photos can also be exported as an archive for your presentations.

#### Can I customize the reports?

Yes. You choose the period, the trails, the task types, the team members. The report adapts to what you want to demonstrate.

#### How long is data retained?

As long as your account is active, everything is kept. If you cancel, we keep your data for 90 days to allow a reactivation or a complete export.

## Release notes

### Sentinel 2.8.1

## Your structures name themselves

Out in the field, whoever installs the thirtieth marker on a trail shouldn't have to decide what it's called. Until now,
every structure name was typed by hand — with everything that comes with it: `PV 12` sitting next to `PV-012`, skipped
numbers, and duplicates you only discover three months later while preparing an inspection.

Sentinel 2.8.1 brings **automatic structure numbering**. You describe the shape of the name once, and the app proposes
the next one every time you create a structure — at the office as much as in the field, with or without a connection.

**One rule per type and per activity** — Structure types now have a **Numbering** tab: a prefix (`PV`, `BRIDGE`, `DR`…),
a separator, and the number of digits. A live preview shows the next three names. A boardwalk for mountain biking and a
boardwalk for hiking stay two independent sequences, with their own prefixes if that's what you want.

**One sequence per trail** — Numbering restarts at 1 on every trail: the first boardwalk on one trail is `PV-001`, and
so
is the first boardwalk on the next. Off-trail structures form their own sequence. It matches the way people talk on the
ground — "the second boardwalk on La Coulée", not "boardwalk number 47 on the network".

**No counter to maintain** — Sentinel keeps no counter: on each creation it reads the names already in place and
proposes
the next one. A deleted number is therefore reused, with no permanent gap. And the sequence picks up from what you
already have: if your structures are named `Bridge 12` and `Bridge 13`, the next one is proposed as `Bridge 14`, even
without any rule configured. A rule is there to impose a shape, not to turn the mechanism on.

**The name is still yours** — It arrives pre-filled, never imposed. You can replace it with anything you like; the app
simply warns you if that name is already taken on the same trail.

**Even deep in the woods** — Offline, the proposal accounts for the structures already on the device **and** for the
ones
waiting to be synchronized. Two boardwalks created back to back in the same area can't end up with the same number.

Numbering is configured from the web app, and mobile uses your rules as they are. The details — prefixes, separators,
scope, edge cases — are covered in the
[structure types documentation](/en/docs/manage-structure-types).

## The trail you tap finally stands out

On the Field map, tapping a track filters tasks down to that trail. That was already true — but nothing really showed
it: the chosen trail got a halo in its own colour, so pale green under a green line, in the middle of fifty other
coloured tracks. You tapped, something changed, and you weren't sure what.

**The other trails recede** — As soon as a trail is selected, every other one drops into the background, very pale,
names faded, while yours thickens. Nothing disappears: you keep the shape of the network in view. The contrast comes
from recession rather than from adding a colour, which makes it read just as well on satellite as on the light basemap.

**The phone confirms** — A short buzz when the track is caught, the same as for tasks and structures. Aim for the line:
a trail's touch area is narrower than a marker's.

**A pill tells you what you're filtering on** — Zoomed in on a task, the chosen track no longer fits on screen. A pill
at the top left names it. And when it's the very trail you're walking, it replaces "You are in" rather than stacking
under it: the same name is never written twice.

**If you filter several** — The display changes character instead of piling up. A quieter dark capsule shows the
symbols of the ratings present in your filter, then the count: "10 trails filtered". It stays the same size whether you
filter two trails or fifteen.

Tap the same trail again to go back to the full view. It's the same filter as the panel's: what you set with your
finger on the map shows up under "Trail", and the reverse holds too. The details are in the
[mobile map documentation](/en/docs/tasks-on-mobile).

## Your task folders reach the phone

Folders group the tasks that get done together — "May 12 work party", "Before opening day". You filled them from the web
app, but the phone never showed them: out in the field you had to piece the work party back together from memory, task
by task, in the middle of the whole list. The tidying done at the office stopped at the door.

Sentinel 2.8.1 shows your folders in the Field list, and lets you open the contents of each one.

**A Folders heading, between the projects and the tasks** — One row per folder: its name, an arrow, and a gold folder
icon. The drawing is the same as a project's; colour is what tells them apart, gold for a folder and grey for a project.
A project also shows its task count and its progress — a folder carries nothing but its name.

**Three ways to look at it** — Tap a folder and its contents open like a project's: **Map**, **List** and **Kanban**, as
three tabs at the bottom of the screen. The map frames itself on the folder's tasks, and the kanban is the one you know
from My planning — one column per status, drag-and-drop to move work along.

**Every folder reopens the way you left it** — The mode is remembered folder by folder, not once for all: a scouting
folder can reopen on the map while a work-party folder reopens as a kanban. The kanban goes further and remembers the
column you were on as well. A project's details now behave the same way.

**A shortcut, not a drawer that hides things** — Filing a task in a folder doesn't remove it from the list: it stays
visible further down, in its status group. A folder opens a second path to the same tasks, it diverts none of them.

**Even with no network** — Folders are part of the data installed on the device, like the trails and the task types. The
heading shows up and a folder's contents can be browsed offline, with nothing to prepare.

Inside a folder you see the whole folder: the filters in the top bar don't apply there, so you never get an empty list
with no visible reason for it. The details are in the
[mobile list documentation](/en/docs/tasks-on-mobile).

### Sentinel 2.8.0

## Checklists: recurring work finally has its own place

Part of maintenance work never changes. Every spring, every patrol, every inspection brings back the same list of things
to do on each of your trails: clear the fallen trees, blow off the debris, check the signage, rake the entrances. Until
now, the only way to track that in Sentinel was to create one task per trail — and watch your task list fill up with
dozens of entries that all say the same thing.

Sentinel 2.8 fixes that with **checklists**. You describe the work once, you pick the trails it applies to, and Sentinel
creates a list to check off for each one. Your tasks go back to being what they should be: one-off jobs to get done.
Recurring work now has a home of its own.

![Checklists in the web app](/fr/version/2_8_0/web_checklist.mp4)

**A template you reuse season after season** — Save your list of items once — each with its own icon — then launch it as
often as you need without re-entering anything. The template stays optional: if you'd rather, you can write the items
directly while creating the checklist.

**One checklist per trail, in a single launch** — Tick the trails you're targeting, and Sentinel instantiates the same
list for each of them. One action replaces creating dozens of tasks by hand.

**All the progress in a single grid** — A checklist's detail shows a full-width matrix: your trails as rows, the items to
check off as columns. A ticked box, an empty box — the state of your whole network reads at a single glance, without
opening anything. Up top: the number of trails, overall progress, and time elapsed since launch.

**A person in charge and an assignee** — Just like your tasks, every checklist can have a person in charge and an
assignee — an individual or a group — so everyone knows who's leading and who's doing.

## Check it off in the field, follow it from the office

Checklists don't live in the web app alone. In the field, the mobile app puts them a few taps away: from the map, open
the list of active checklists, pick your trail, and tick items off as the work gets done.

![Checklists in the mobile app](/fr/version/2_8_0/mobile_checklist.mp4)

**Ticked on site, visible instantly** — Every box checked in the field shows up right away in the office grid, and
progress recalculates in real time. Nobody has to call in to find out how the patrol is going.

**Even deep in the woods** — Like the rest of Sentinel, checklists work with no signal. Your ticks are kept on the
device and sync on their own as soon as the connection comes back.

**A discussion per trail** — Every row in the grid has its own conversation. A stump that won't budge, a culvert to look
at again, a photo to show the crew: the discussion stays attached to the right trail, with an unread-message counter
right in the grid. Those exchanges also show up in your Conversations section, alongside all the others.

## A recurrence that runs without you

Truly recurring work doesn't just need structure: it needs to come back on its own. So every checklist can be scheduled
to relaunch itself.

**As flexible as your calendar** — Pick a daily, weekly, or monthly frequency, with a free interval (every two weeks,
every three months…), one or several days of the week, or a specific day of the month. Set a start date, and an end:
never, on a given date, or after a number of occurrences.

**You decide what happens to the previous one** — When it comes due, Sentinel creates the new checklist and, depending on
your choice, automatically completes the one that's ending or keeps it active long enough to finish the last trails.

**Always know what's coming** — A checklist's detail states its cadence and the date of the next occurrence in plain
language. And if you simply need a copy right now, the Duplicate button starts a fresh grid with the same trails and the
same items.

## Share a task with the public

Some work deserves to be explained to the people who use your trails. A bridge under repair, a temporary detour, a
section closed for the duration of a project: instead of trying to summarize everything in a post, you can now open a
public link to the task itself.

![Public task share page](/fr/version/2_8_0/share_webapp.mp4)

**A link you open, and close, whenever you want** — Sharing is enabled task by task, never by default. One switch, one
link to copy, and it's live. A badge appears on the task to remind you it's public, and the link is revoked as fast as
it was created.

**A page anyone understands in three seconds** — Visitors land on a clear page: the type of work and its status, the task
name, the trail involved, then a map showing exactly where it is. The point or the track appears with the same pin as in
the app, and your annotations — zones, lines, points of interest — are there too. The map opens full screen and switches
to satellite view.

**Your photos, your call** — The task's photos are included by default, in a gallery that opens large with a single
click. A switch removes them if you'd rather keep the page plain.

**What never leaves** — Name, description, position, trail, status, annotations, and photos: that's it. Your members,
your assignments, your materials, your logged time, and your discussions stay strictly internal. The page also asks
search engines not to index it: it travels through your link, not through Google.

## Take the task into your GPS

A web page is perfect for informing people. To actually get there, you need coordinates. So every shared task offers a
download in **GPX**, **KML**, and **GeoJSON** — the point or the track, annotations included, ready to open.

GPX imports into a handheld GPS or an outdoor app, KML opens in Google Earth, and GeoJSON goes straight into mapping
software. Your volunteers, your contractors, and your municipality reach the right spot on the first try, without anyone
having to pass coordinates along by hand.

## The web app gets a fresh look

The entire web app has been reworked to breathe better and to look like itself from one screen to the next.

**A card for every section** — Each section now sits in a white card resting on a grey background. Content is clearly
framed, the interface feels calmer, and the visual rhythm stays the same whether you're in Tasks, Trails, Members, or
Billing.

**One header, one obvious way back** — Every section shares the same header bar: title on the left, search and actions on
the right, and a full-height back button as soon as you open a detail. Opening a record now takes the whole screen, just
like checklists — and you always come back out at the same place.

**More room for your data** — Lists and tables take up all the available width, and rows of buttons have been folded into
a discreet menu. Less wasted space, more rows visible without scrolling.

## Satellite view comes to the web app

The mobile app could already switch between the standard base map and satellite imagery. The web app now does it too —
everywhere a map appears.

![Satellite view in the web app](/fr/version/2_8_0/satelite_webapp.mp4)

A small toggle at the top right of the map switches between **Standard** and **Satellite**. The standard base map stays
the most readable one to work in: trails, tasks, and structures stand out clearly. Satellite view puts everything back
into the real terrain — tree cover, streams, cutovers, parking areas — which helps enormously when judging an access
route, planning a new section, or making sense of an area you don't know yet. Switching keeps your position and your
zoom: you never lose your place.

### Sentinel 2.7.0

## Annotate the map to explain every task

A task isn't always just a point on the map. Sentinel 2.7 lets you annotate the map directly as you create or edit a
task, with three tools: the point, the line, and the zone. It makes your tasks far more vivid and shows, at a glance,
what to do and where to do it.

No more vague explanations buried in a description field: you draw the information right where it matters, on the ground
itself.

![Annotating the map](/en/version/2_7_0/annotate_mobile.mp4)

**Points of interest, with photos** — Add points around the task to flag everything that matters for getting it done. A
trail task that requires fetching rocks deeper in the woods? Mark the exact spot with a point and attach one or more
photos, so there's no doubt about what to look for.

**Lines and tracks** — Draw a line to show a route, an access path, or a bypass — for instance a detour to build at the
exit of a section. In the field, record the track simply by following your GPS position as you walk; or draw it by hand
directly on the map. Either way, the route appears clearly on the task.

**Zones to outline** — Circle a zone to flag a constraint or a perimeter to respect. Building a new section of trail and
need to protect a nearby wetland? Outline it as a zone right on the map: the team knows exactly what to avoid before
they
even get there.

## In the field and at the office

Annotations are available everywhere: on the mobile app, to draw on site the moment you spot the work to be done, and on
the web app, to prepare a task from the office. They can be added both when creating and when editing a task.

Each annotation can be given a name and a color, to tell an access path from a sensitive zone or a point of interest at
a
glance. And because everything syncs, an annotation drawn on the web shows up in the field on the task's detail, and
vice
versa.

![Annotating the map](/en/version/2_7_0/annotate_web_app.mp4)

## Closing the loop

With the description, photos, voice notes, and materials already attached to every task, annotations complete the
picture. A Sentinel task no longer just says what to do: it shows where, with what, and how — on the map as much as in
the detail. One more way to make sure every job is understood without ambiguity — and done right the first time.

## Your trail conditions, now on a map

The public trail-conditions widget, introduced in Sentinel 2.5, can now show a map beside the list. Your visitors no
longer just read statuses: they see your whole network at a single glance.

![Trail conditions widget with map](/en/version/2_7_0/condition.png)

**The whole network at a glance** — Trail paths appear on the map, colored by their condition: open, closed, or under
construction. The state of your network jumps out, with no need to scan the list line by line.

**Standard or satellite view** — Pick the base map that shows your network best: a clean standard base map, or satellite
imagery to place the trails in their real-world surroundings.

**A livelier experience** — The list and the map sit side by side, for a more visual, more dynamic, and more intuitive
way to check conditions — embedded right in your website, without visitors ever having to leave it.

## In the field, the map follows you and scans your surroundings

The location button on the mobile map gains three modes, one tap after another. The first recenters on your position.
The second locks the map onto you and follows your every move. The third brings you back to the overview of your whole
network.

![Annotating the map](/en/version/2_7_0/live_tracking.mp4)

**A scan mode that surfaces what's nearby** — As soon as the map locks onto you, a radius appears around your position
and automatically surfaces the tasks and structures within a few dozen metres of you, without touching your filters. As
you walk, you spot at a glance everything there is to do right beside you — like a detector.

**Always in the right place, without thinking about it** — The map recenters on you with every step, while respecting
your zoom: set it once and it sticks. And because the follow reuses your already-active GPS position, it adds no extra
battery drain.

**Even offline** — Scan mode works online and off: nearby tasks and structures show up even deep in an area with no
signal.

## A compass to keep your bearings

On the mobile app, a compass now appears on the map as soon as you rotate it. It always points north and, with a single
tap, snaps the map back to north so you can get your bearings in an instant. When the map is already aligned to north,
the compass fades away on its own to keep the screen uncluttered.

![Annotating the map](/en/version/2_7_0/north.mp4)

### Sentinel 2.6.0

## Work anywhere, even offline

Sentinel 2.6 pushes the limits of fieldwork: even with no connection at all, your team keeps working as usual. Tasks,
time, and structures stay fully editable offline, and everything syncs automatically the moment the network is back —
no data loss, no double entry, no manual steps.

This is a rare capability in field-management tools: most require a connection for the smallest change. Sentinel works
wherever your trails take you — deep in the woods, up a mountain, anywhere without cellular coverage.

**Editable tasks offline** — Create, edit, complete, or delete tasks with no connection. Change the status, assignment,
priority, description, or location — everything stays available. Your changes appear immediately in the list, on the
map, and in the detail view, exactly as they would online.

**Time logging offline** — Log the time spent on a task right in the field, even without a network. Logged hours are
kept locally and sync automatically once the connection is restored.

**Structures and inspections offline** — Create a structure and fill out its inspection report right away, with no
connection — even for a structure you just created offline. Photos, evaluation answers, and reports are queued and
synced
together as soon as the network returns.

**Automatic sync and merge** — As soon as the connection is back, Sentinel sends your changes in the background. If a
teammate edited the same task in the meantime, Sentinel automatically merges the non-overlapping changes (one changes
the name, the other the status → both are kept). Only genuine conflicts — the same field changed differently on both
sides — are surfaced for you to resolve. No manual merging in the vast majority of cases.

## Inspection calendar view

In the web app, the Structures section gains a third view mode: a calendar view that lays out the upcoming inspections
to be done, month by month.

![Inspection calendar view](/fr/version/2_6_0/calandar.mp4)

**A clear overview** — Each structure appears on the date of its next scheduled inspection, calculated from its latest
report. At a glance, you see what's coming up this month and plan your rounds accordingly.

**Overdue at a glance** — Overdue inspections are clearly flagged, so no deadline slips through unnoticed.

**Simple navigation** — Move from one month to the next, jump back to today in one click, and click any structure to
open
its detail directly. The view respects the section's active filters.

### Sentinel 2.5.0

## Let your trails speak, effortlessly

Sentinel 2.5 turns your team's fieldwork into public information: trail conditions automatically follow in-progress
tasks, with no one on the team having to update anything manually.

**Condition boards** — Create condition boards organized by activity type (biking, snowshoeing, cross-country skiing,
etc.). Each board groups your trails with a clear status: Open, Closed, or Under Construction. Trails can be organized
into folders to reflect your network's structure, and an entire folder's status can be changed in a single action.

![Condition boards](/fr/version/2_5_0/conditions.mp4)
![Condition boards on mobile](/fr/version/2_5_0/conditions_mobile.mp4)

**Automatic sync with tasks** — When a task linked to a trail moves to "In Progress" status, Sentinel automatically
offers to set the trail's condition to "Under Construction." When the last in-progress task is completed, the condition
returns to "Open." No need to update conditions manually — they follow the team's actual work in the field.

**Automatic reminders** — As long as a task remains "In Progress" on a monitored trail, a reminder is sent after
8 hours, then every 24 hours via push notification and email, to prevent a trail from staying under construction due to
oversight.

**Embeddable public widget** — Each condition board generates a widget you can embed directly on your website. Your
visitors see up-to-date conditions without leaving your site, and the widget updates automatically.

## Structure Folders

Structure management gets more flexible with a new folder system and multiple grouping modes.

**Custom folders** — Create folders to organize your structures by whatever logic suits your network: by sector,
infrastructure type, priority, or any other criteria. On the web version, move structures between folders using drag
and drop, with the ability to select multiple structures at once for batch moves. On mobile, a folder picker is
available when creating or editing a structure.

**Grouping modes** — The structure list can now be grouped in four different ways: by status, by type, by trail, or by
folder. Combine groupings to get the view that fits your needs — for example, structures grouped by trail, then by
status within each trail.

**Kanban folder filtering** — The structure Kanban view includes a folder sidebar that lets you quickly filter the
displayed structures by the selected folder.

## Camera Zoom Controls

Sentinel's built-in camera gets a major upgrade with zoom controls inspired by the native iOS camera interface.

**Zoom level selector** — Three buttons (0.5x, 1x, 2x) let you instantly switch between your device's ultra-wide,
wide-angle, and telephoto lenses. No more being limited to a single lens — you now have access to your phone's full
optical range to capture your observations with the right framing.

**Pinch to zoom** — In addition to the buttons, the pinch gesture provides smooth, continuous zoom control, just like
the native camera app. Perfect for fine-tuning your framing when documenting a detail in the field.

## Photo Annotations

Sentinel 2.5 lets you annotate photos directly before attaching them to a task or sharing them in a discussion. Draw
freehand to point out a detail, circle an area to fix, or add a visual comment — with five preset colors, a custom
color picker, three stroke widths, and undo/redo, so your message reads at a glance.

![Photo annotations](/fr/version/2_5_0/annotation.mp4)

## User Preferences

The web version now includes a preferences panel accessible from the user menu, letting you customize the app's behavior
to match the way you work.

**Auto-open tasks** — By default, clicking a task in the list automatically opens the detail panel in addition to
centering the map. You can disable this if you prefer to simply locate the task on the map without opening the panel on
every click.

**Auto-open structures** — Same option for structures: choose whether a click opens the detail view directly or just
recenters the map.

## Inspection Report Deletion

You can now delete an inspection report directly from a structure's report list, using the context menu. A confirmation
is required before each deletion to prevent mistakes.

The report is archived rather than permanently deleted, preserving the complete inspection history — an important point
in a context of legal requirements or insurance. After deletion, the structure's status is automatically recalculated
based on the latest active report.

### Sentinel 2.4.0

## Organizing work beyond the map

Sentinel 2.4 simplifies how your team organizes its work by introducing a new way to manage the tasks that don't
happen on the field.

**A new type of task** — A task can now exist without a point on the map, for anything that doesn't tie to a specific
spot: preparation, administrative follow-ups, purchases, planning, communication. These tasks include a description,
one or more assignees, an optional due date, and can hold photos, audio memos, and files.

**"Planning" section** — A new Kanban view designed for managers, providing a quick overview of all members and groups.
It lets you organize the tasks assigned to each person — by day, by week, or however you need — and manage the team's
workload from a single place.

![Feature demo](/fr/version/2_4_0/planif.mp4)

**"My Planning" section** — Each user now has their own personal Kanban view, bringing together all tasks assigned to
them, whether geolocated or not. At a glance, they can see what needs to be done, what's in progress, and what's
completed, without having to filter through the global lists.

![Feature demo](/fr/version/2_4_0/my_planning.mp4)
![Feature demo](/fr/version/2_4_0/my_planning_mobile.mp4)

**Kanban view in projects** (mobile) — In addition to the map and list views, projects now offer a Kanban view on
mobile. It groups tasks with the assignee's name shown directly on each card, making it easier to manage projects from
the field.

![Feature demo](/fr/version/2_4_0/project_kanban_mobile.mp4)

## User Groups

You can now create groups to structure your team (for example: patrollers, mechanics, inspection crew). A task or
project can be assigned to a group or to a user, making it simpler to distribute work without having to pick each
person individually. Each group has its own planning view, and group management is controlled by a dedicated
permission.

![Feature demo](/fr/version/2_4_0/groups.mp4)

## @-Mentions in Discussions

When writing a message in a discussion, typing `@` now opens an autocomplete that suggests your teammates. A mention
notifies the person directly, ensuring they see the message without having to watch the thread.

![Feature demo](/fr/version/2_4_0/discussion.mp4)

## Discussions on Mobile

The discussion system has been redesigned on mobile for a better experience. The discussion icon in the top bar now
opens a list of all active discussions by task, instead of redirecting to notifications. You can easily follow ongoing
conversations and pick up right where you left off, just like on the web version.

![Feature demo](/fr/version/2_4_0/mobile_discussion.mp4)

## Task Creation from Photo

You can now create a task directly from a photo. When the photo contains geolocation data, Sentinel automatically
detects the trail and positions the task at the exact spot where the photo was taken. For example, a visitor reports a
fallen tree and hands you their photo — just import it and the task is placed at the right location on the trail, with
no manual search required.

![Feature demo](/fr/version/2_4_0/task_image.mp4)

### Sentinel 2.3.1

Added two new activities:
- Snowmobile
- ATV/Quad

### Sentinel 2.3.0

## Sentinel on the Web

This is the missing piece that completes Sentinel. The web version, fully rebuilt, is now available.
https://app.trail-sentinel.com

The mobile app remains the field tool — fast, accessible, and designed for real-world conditions. The web version takes
over at the desk, on a large screen with a keyboard and mouse, to plan, oversee, and analyze the team's work in the
comfort of a computer.

**A visual dashboard** right when you open it: critical open tasks, at-risk structures, overdue reports, completed
tasks, with trends over the selected period. The essential information is there, at a glance, without having to
navigate.

![Web dashboard with KPI cards, charts, and trend graphs](/en/version/2_3_0/trail-management-dashboard-kpi-charts.png)

**Kanban boards for planning** — Tasks, structures, and projects can be organized in columns by status and dragged from
one stage to the next. It's the planning tool that was missing to get a clear view of what's to do, in progress, or
done, across the entire team.

![Kanban board with tasks organized by status columns](/en/version/2_3_0/kanban-board-task-management.png)

![Task list with interactive trail map showing task locations](/en/version/2_3_0/task-map-trail-locations.png)

![Task list with detail side panel showing map, info, and photos](/en/version/2_3_0/task-detail-panel-map-photos.png)

**Project analytics and tracking** — Each project has its own statistics view: time spent per member, workload
distribution, progress. Perfect for tracking advancement and balancing efforts within the team.

![Project view with kanban board and task progress tracking](/en/version/2_3_0/project-tracking-kanban-progress.png)

**Batch editing, advanced filters, and exports** — Edit several tasks at once, turn filters into projects, export data
to Excel or PDF. The tools a manager expects to work efficiently at scale.

Accessible from any browser, with no installation. With the combination of mobile in the field and web at the office,
Sentinel now covers the full work cycle of trail managers.

## Structure Inspection Reports

You can now create inspection reports for each of your structures, directly from the app.

Sentinel offers two approaches for your inspections, depending on the level of rigor you need.

**With evaluation form** — When questions are defined in a structure type, each report becomes a structured form. The
inspector answers each question by assigning a score from 1 to 4, and can add a comment, photos, and audio memos per
question to document their observations.

![Inspection report form with evaluation questions](/en/version/2_3_0/structure-inspection-evaluation-form.png)

![Answering an evaluation question with score, comment, and media](/en/version/2_3_0/inspection-question-scoring-media.png)

The overall score is automatically calculated using the weighted scoring system, where each question can carry a
different weight in the final score based on its importance.

![Structure detail view with map, status, and inspection history](/fr/version/2_3_0/fiche-structure-carte-statut.png)

**Without evaluation form** — For structures that don't require a detailed form, or for quicker follow-ups, the
inspector creates a simplified report. They manually select the status, add a general comment, photos, and audio memos,
then set the next inspection reminder date themselves.

**PDF exports and email notifications** — Each report can be exported as a PDF, making archiving and sharing easier — a
valuable asset when dealing with legal, insurance, or liability requirements. When a report is submitted, a notification
can also be sent by email with the PDF report attached, keeping the entire team informed in real time.

The advantages of using evaluation forms are significant:

- Standardized inspections across all team members
- Standardized working methodology within your process
- Complete traceability of all inspections, useful for legal requirements or liability cases
- Better perception with insurers thanks to a rigorous, documented methodology
- Contributes to the safety of your equipment and infrastructure

Reports are accessible from each structure's detail view, sorted chronologically.

## Audio Memos

Sentinel 2.3 introduces a new way to attach media to tasks: audio memos. When creating or editing a task, you can now
record a voice memo directly from the app — a faster and more natural way to add a detailed explanation than typing text
in the field.

![Audio memo recorder on the task editing screen](/en/version/2_3_0/audio-memo-voice-recording.png)

Audio memos are also available in structures and in inspection reports, letting you capture an observation verbally
instead of writing it down.

When an inspection report is exported as PDF, each audio memo is automatically transcribed in the document, so that
verbal observations are just as clear and usable as written ones.

### Sentinel 2.2.0

## Custom Trail Difficulty Levels

Every trail network is different. Until now, Sentinel offered a fixed list of difficulty levels. With version 2.2.0,
you now have full control to define your own difficulty levels.

You can now:

- Create difficulty levels with any name and color you choose
- Reorder levels with drag-and-drop
- Edit or delete existing levels

![Difficulty levels list](/en/version/2_2_0/rating_list.png)

![Add a difficulty level](/en/version/2_2_0/rating_add.png)

![Choose a rating color](/en/version/2_2_0/rating_color.png)

Whether your network uses a classic rating system or a technical scale specific to your activity, Sentinel now adapts
to your needs.

## Interface Improvements

- Improved trail layer ordering on the map

## Bug Fixes

- Improved static map image quality
- Fixed duplicate prevention during media synchronization
- Improved file upload stability

### Sentinel 2.1.0

This update fixes several bugs introduced in the previous version.

You can see all the changes in version 2.0.0 [here](/en/release/2.0.0).

### Sentinel 2.0.0

## Introducing Structures: one of our most requested features

Trail managers have been asking for a simpler way to track bridges, boardwalks, signage, technical features, and all the critical elements that require regular maintenance.

With Sentinel 2.0, you can now:
- Create structures directly on the map, just like you do with tasks
- Keep a complete inventory of all critical assets and their location
- View images by year to review past conditions at a glance
- Customize structure types, similar to custom task types
- Combine planned maintenance with unexpected issues in a single system

**Our next version, soon to be released**, will add the ability to create inspection reports on each structure, and get a quick overview on the overall condition (good, bad, dangerous) of all your structures.

These features are part of our plan to help trail managers and their team stay proactive, improve user safety, and meet rising legal and insurance requirements.

![Structure Map](/en/version/2_0_0/structure_map.png)

![New Structure](/en/version/2_0_0/new_structure.png)

![View Structure](/en/version/2_0_0/view_structure.png)

## Create tasks anywhere

Not every issue happens on a trail. With Sentinel 2.0, you can now create a task **without linking it to a specific trail**.

Use it for objects or hazards not tied to a trail, or features and points of interest you want to record.

When creating a task, you now have a unified experience and can choose to:
- Attach the task to a nearby trail
- Associate it with any trail from the list
- Or place it freely on the map

This update also improves GPS positioning and reduces duplicate task creation.

![New Task](/en/version/2_0_0/new_task.png)

![Select Marker](/en/version/2_0_0/select_marker.png)

![Task Conflict](/en/version/2_0_0/task_conflict.png)

## Performance and speed improvements

We know your time on the ground is valuable. Sentinel 2.0 brings major optimizations to keep everything running fast and reliably.

- Faster installation with lighter local files (trails, custom task types, etc.)
- A new section to review data installed on the phone and reinstall it when necessary
- A rebuilt synchronization system for low or unstable network conditions
- Technical improvements across the app for quicker, more stable responses
- A fix ensuring previously selected filters remain saved when returning to the app
- Adds several new icons to use when creating your custom tasks and structure types.

![Icons](/en/version/2_0_0/icons.png)

**Sentinel 2.0** is smoother, faster, and more dependable wherever your trails take you.

### Sentinel 1.7.1

Added two new icons used in the creation of custom task types:
- An icon representing a tree branch.
- An icon representing bicycle tracks in the snow.

### Sentinel 1.7.0

Minor bug fixes

Added a new icon for the task type that represents trail accessibility

### Sentinel 1.6.9

Minor bug fixes

Preparation for the upcoming major Sentinel 2.0 update

### Sentinel 1.6.8

Image compression optimization during task creation.

Image compression optimization during task updates.

### Sentinel 1.6.7

Performance improvements when displaying tasks

Improved user session management in case of unstable network connection

### Sentinel 1.6.6

## Voice recognition for task entry

Our new flagship feature is the integration of voice recognition when creating or modifying tasks. Now, you can dictate the description of your tasks directly to the application, making entry faster and more natural than ever.

No more typing long texts on your keyboard! Simply press the voice recognition button and speak - the application will automatically transform your words into text for your task description.

![Voice recognition](/en/version/1_6_6/voice.png)

## Fixes and improvements

In addition to this major new feature, we have also resolved several minor bugs to improve the overall stability and performance of the application. Our team remains dedicated to providing you with a seamless experience, and these fixes are part of our ongoing commitment to quality.

### Sentinel 1.6.5

## Multi-user time entry

When entering time for a task or project, it is now possible to add time for multiple people simultaneously. This feature is particularly useful for group tasks, making time entry much more efficient.

![Time entry](/en/version/1_6_5/time.png)

## Creating tasks from a project

It is now possible to add tasks directly from a project, significantly simplifying the task creation process. To add a task to a project, simply use the "+" button from the project page.

![Create task from project](/en/version/1_6_5/create_new_task_project.png)

![Project task list](/en/version/1_6_5/create_new_task_project_list.png)

## Notifications grouped by category

Notifications are now grouped by category, making them easier to review and preventing important information from being missed. This improvement makes alert management more intuitive and efficient.

![Notifications](/en/version/1_6_5/notification.png)

## Performance improvements

The application has been optimized to work more efficiently on older phones, providing a better user experience on all devices.

## Bug fixes

Resolution of duplication issues when synchronizing tasks created offline

Fixed the bug where, in some cases, tasks were created in duplicate

Optimization of image loading to improve overall performance

### Sentinel 1.6.4

- Fixed an issue where, on certain Android versions, the application would remain stuck on the loading screen.
- Resolved a problem where, in case of poor network quality, the "Save" button wouldn't respond properly when adding tasks, causing duplicates.
- Fixed a task synchronization issue where images weren't being synchronized in some cases.
- Fixed the issue that prevented saving the selected activity type.

### Sentinel 1.6.3

## Share images and react in conversations

You can now send images, react to messages with emojis, and reply to specific messages, just like in any modern chat.

Use conversations to keep everything about a task in one place and keep your team aligned.

![Task](/en/version/1_6_3/task.png)

![Chat](/en/version/1_6_3/chat.png)

![Emoji](/en/version/1_6_3/emoji.png)

## More stability during low connection

We know that many trail networks are located in areas with low to none Internet connection. Even though you can already create a task while offline, we are constantly improving the stability of the app to make sure it always responds well.

Sentinel now handles low or unstable connections better than ever, keeping the app responsive even when coverage is spotty.

## User experience improvements

We know that you like being out there, building stuff, playing with dirt, and most importantly riding your trails! There is no time to look for a button in the app, or click 10 times to get to a page. We get you!

We've simplified key sections to make your experience smoother and quicker, so you can focus on the trails.

### Sentinel 1.6.2

## Modify multiple tasks in bulk

After a full year of using Sentinel and hundreds of hours of work, you probably have a lot of tasks that are not up to date, or not relevant anymore.

As you are planning your trail work for the next season, you realize that you have multiple tasks in Sentinel that need to be marked as done, or re-prioritized. But doing that one task at a time would be very time-consuming!

That is why we are releasing a new feature to help you save time.

Going into the list view of your tasks, you can access the option to "Edit multiple tasks" at the same time by clicking on the three-dot menu.

![Mass export](/en/version/1_6_2/export_mass.png)

Use the filters to narrow down your search and select only the tasks you want to update. Let's say you want all the tasks that were created before January 2025, no worries!

![Export filter](/en/version/1_6_2/export_mass_filter.png)

Go to the next step and choose the modification you want to make. You want to mark all these tasks as "Done"? Let's do that!

![Mass values](/en/version/1_6_2/mass_values.png)

And voilà! All the corresponding tasks will be updated at the same time, and it only required a couple of clicks on your end.

*Note: This feature is only accessible to "Admin" members.*

## Export data into an excel file

You're using Sentinel for a couple of months now, and you are probably at this stage where you would like to have a deeper analysis of all the work that has been done on your network.

How much time has been put into each project?

Which trail required the most maintenance?

Do we have the same erosion or water issues over and over again?

Trying to answer all these questions through a mobile device can be tricky. That is why we are releasing a new feature to export your data into an excel file!

Going into the list view of your tasks, you can access the option to "Export data" by clicking on the three-dot menu.

Select the tasks you want to export. It could be all of the tasks created in your account, or you could also narrow down your search by using the filters.

Having all your data in an excel file also gives you the ability to share the information with external contributors, your board of directors, or even financial and legal institutions. It also enables you to transfer the data to another system or application you might be using internally.

![Data export](/en/version/1_6_2/export_data.png)

### Sentinel 1.6.1

## Manage member access by activity

This new feature is applicable if multiple activities are available on your network.

Until now, every member had access to all the activities available on an account. This could lead to mistakes that were difficult to erase.

It is particularly true if you have different trail crews for each activity (mountain biking, hiking, nordic skiing, etc.). Sometimes, a member would wrongly create a task for "hiking" instead of "mountain biking" just because the map was previously set on "hiking".

You can now choose who has access to which activity, and reduce these errors. Depending on the role you assign to a member, this person will be able to edit tasks and projects only for the activities you give them access to.

![Member view](/en/version/1_6_1/member_view.png)

![Member list](/en/version/1_6_1/member_list.png)

![Member invite](/en/version/1_6_1/member_invite.png)

By default, the member has access to all activities. Simply activate the option to restrict their access to specific activities.

![Create task activity](/en/version/1_6_1/create_task_activity.png)

When creating a task, a member will be prompted the option to change the activity before going any further.

## Manage task types by activity

This new feature is applicable if multiple activities are available on your network.

Sentinel provides predefined task types to choose from when creating a new task, and you can also create custom types to reflect the type of work specific to your trails.

Until now, all these types, predefined or custom, are common among all the activities available on your network. However, a "Broken Plank" issue might not be relevant for "nordic ski", and a "Water" type might not be useful for "hiking". Having too many options has led to errors and can also be a bit messy to deal with on the interface.

With this update, you can now assign a task type to specific activities so the type would only appear when creating a new task in the selected activities. The same is true for custom types.

![Task type predefined](/en/version/1_6_1/task_type_predefined.png)

![Task type list](/en/version/1_6_1/task_type_list.png)

![Task type create](/en/version/1_6_1/task_type_create.png)

By default, a task type is available when creating a new task in all activities. Simply remove specific activities from the menu to hide this type when creating a new task in those activities.

## Filter by creation date

After several weeks or months of using Sentinel, you might be facing lots of tasks and projects to manage, order, and update.

The filter menu is a good way to dig down when searching for specific tasks. And to go even further, we added the creation date of a task as a new filtering option.

![Filter created](/en/version/1_6_1/filter_created.png)

By activating this filter, you can choose to see your open tasks created "before", "after", or "on" a certain date.

## Improve localization with trail names

When a network is made of numerous trails, it can be hard to identify precisely on which trail our GPS position is standing, and which trails are around us.

To improve visibility on the map, the names of the trails will now appear when zooming more closely on the main map, as well as when creating a new task.

![Task add](/en/version/1_6_1/task_add.png)

![Task map](/en/version/1_6_1/task_map.png)

### Sentinel 1.6.0

## Start a conversation around a task

Each task or project requires a good level of collaboration between team members. Being able to write down updates on a task every time someone works on it can be very helpful in order to know where to start again the next day, and create a maintenance log.

![Discussion task](/en/version/1_6_0/discussion_task.png)

![Discussion mention](/en/version/1_6_0/discussion_mention.png)

![Discussion message](/en/version/1_6_0/discussion_message.png)

On each task or project page, the new button **"Conversation"** gives access to the conversation page for this specific task or project. Every member with at least an "editor" access can send a message into the conversation, and each member already involved in the conversation is then notified.

You can also mention a member using the **@** symbol to address a message to a specific person, who will receive a notification.

Our goal is to help you bring every relevant information surrounding a task in the same place and accessible to everyone in your team. That is why all messages in the conversation are saved and the history is available at all times.

You can use the conversation as a maintenance log, and to remind yourself and your team of the work that has been done and of what remains to be done.

## Notifications Center

Depending on your notifications settings, the volume of notifications you receive can quickly become overwhelming and no interface in the app allows you to go back to the list of notifications. The notification center now allows you to consult previous notifications and make sure you did not miss anything!

![Notifications](/en/version/1_6_0/notifications.png)

![Notifications options](/en/version/1_6_0/notifications_options.png)

This notification center is still accessible from the same menu in your account settings. Notifications are listed in chronological order. Each notification contains several elements of information for a quick identification, and each one can be clicked on to get you to the specific item or activity.

All previous notifications are saved even when marked as read, allowing you to easily get back to previous activities. You can also choose to delete all notifications to keep a clear notification center. In that case, all your history will be deleted.

## Quick "mark as done"

As of now, to close a task, you needed to edit the task, change the status to **"Done"**, and save your modifications. This process, even though is not complicated, can be seen as too long when you need to get down with a busy day at work.

With this new update, every step of this process is brought to only 1 click. A button labeled **"Mark as done"** is available directly from the task page and will change the status to **"Done"** automatically.

![Mark as done](/en/version/1_6_0/task_mark_done.png)

This is also very beneficial when you want to go over the remaining tasks of a project and mark them all as done.

### Sentinel 1.5.1

## Internet Connection Timeout Issue

Resolved an issue where a timeout on the internet connection could occur under certain conditions. This problem could lead to task duplication during their creation. Duplications are now avoided thanks to this update.

### Sentinel 1.5.0

Now, when creating a segment task, you have the ability to select the specific track segment you wish to use.

Additionally, if you create a new task that needs to be synced, it is now properly synchronized with the server as expected.

### Sentinel 1.4.9

Resolving the issue where the picture-taking button ceases to function on certain devices.

### Sentinel 1.4.8

Changing location was failing after several tries.

Previously, when an invitation was accepted, the default activity was not rightly selected.

A removed member could still access the account.

In the past, after a certain delay during the creation of the task, the photo that has been added was not saved.

### Sentinel 1.4.7

This update fixes app crashes randomly happening when opening the app.

We apologize for the inconvenience and are delighted to offer a smoother, more reliable experience with this update.

### Sentinel 1.4.6

## Monitor your maintenance for multiple activities

When your trail network is dedicated to multiple activities like mountain biking, hiking, or even snowshoeing and nordic skiing, importing all the different trails on a single map becomes crowded and hard to visualize.

We've added the ability to segment your map by activity type, so that you can only see the trails meant for one activity at a time.

Simply open the layout options menu, and select the activity you want to display on the map.

![Activity list](/en/version/1_4_6/activity_list.png)

![Activity map](/en/version/1_4_6/activity_map.png)

*Prerequisite: you must activate the different activities you want to see in the settings of your account and import all the files for the corresponding trails. We can help you in this process, so don't hesitate to contact us!*

## Customize the type of tasks you create

As of now, when creating new maintenance tasks on your trails, only preset types are available (fallen tree, broken plank, etc.), as well as an "Other" option. However, when ending up with tons of "Other" tasks, it can be hard to have a good overview of the work you need to tackle on the field.

With custom types, you can create tasks that better reflect the type of maintenance work corresponding to your network and your needs. You have big machine-built projects under way? You could create "excavator" or "compactor" as custom types and select them in your new tasks.

![Custom type list](/en/version/1_4_6/custom_type_list.png)

![Custom type add](/en/version/1_4_6/custom_type_add.png)

Go into the settings of your account and find the "Custom task types" menu to start creating your custom types.

![Custom type parameters](/en/version/1_4_6/custom_type_parametters.png)

### Sentinel 1.4.5

This new version brings two major updates: the ability to add time estimates to a task, and to access reports on the total hours completed on your tasks and on each trail.

This version also simplifies the user experience on multiple screens: adding images via the phone camera, filtering out projects, deleting a project, changing the map to a satellite mode.

## Easier way to take pictures

When creating a new task, the app now directly opens your phone camera, removing unnecessary steps in the process where previously you had to choose between taking a picture or selecting from the gallery.

You can take multiple pictures at the same time before attaching them to the task.

The speed of this step has been increased.

![Photo full](/en/version/1_4_5/photo_full.png)

![Photo add task](/en/version/1_4_5/photo_add_task.png)

## Adding time estimates to a task

Being able to compare the time completed on a task with an estimation brings more maturity to project management.

When creating a task, an estimated number of hours can be entered in a specific field.

When a task is added to a project, the estimated time for this task is automatically included in the total estimated time of the project.

The completion % in time for a project is available along with the completion % in number of tasks. It is calculated as the total number of hours completed divided by the total number of hours estimated.

All this data is stored in your account history so that eventually you can export it and exploit it through your own tools and methods.

![Project time](/en/version/1_4_5/projet_time.png)

![Task estimate](/en/version/1_4_5/task_estimate.png)

![Task view time](/en/version/1_4_5/task_view_time.png)

## Individual reports on working hours

These reports give you access to your working hours per month, and can be filtered out by project, by type of task, or even by trail. This feature allows a user to track the number of hours they invested in a project, and to better understand how their work is distributed among the different tasks.

This data is private to each user and only reflects the completed hours of work for this particular user.

![Time log](/en/version/1_4_5/time_log.png)

## Switching to satellite mode

From the map of your trail network, you can now choose between the satellite mode and the standard mode by selecting the "Layer" icon.

The satellite mode can bring more precision when adding a new task by giving a more representative view of the terrain.

![Satellite](/en/version/1_4_5/satellite.png)

![Satellite menu](/en/version/1_4_5/satellite_menu.png)

![Satellite button](/en/version/1_4_5/satellite_button.png)

### More options when deleting a project

When deleting a project, the app now offers you two different options to deal with the associated tasks. You can delete them as well, or save them and unlink them from the project.

Note: deleting a project and the associated tasks is irreversible. If you wish to save your data history, we recommend changing the status of the project and the tasks to "Done".

### Project and tasks "Done" filtered out by default

When all the tasks of a project are marked as "Done", the project will be hidden by default in the list. Same goes for all the tasks marked as "Done", both in the list and on the map.

To display these items, you can open the filter menu and select the status "Done".

### Advanced filters on projects

On top of the existing filter options for tasks, you can now filter projects by status, by creator, or by assignee. Whether you are looking for projects in progress or done, projects created by a particular person or those managed by another member, these filters can help you find the desired project.