Skip to main content

Settings

How SafeRouteZW is set up.

Account preferences

Who you are signed in as

Name
Not signed in
Role
Your role is decided by the server. The browser only displays it.
None
Email
None
Session
There is no authentication backend yet, so this is not a real sign-in.
Not signed in
Data mode
Set with NEXT_PUBLIC_DATA_MODE. In API mode, pages show only what the backend provides.
Live API

Theme

Appearance

Colour theme
A dark theme is planned in the design but has not been drawn, so it is not offered.
Light

Notification preferences

What should interrupt you

Not available yet
  • New high-priority reports
  • Failed processing jobs
  • Failed alert deliveries

The header bell already lists items that need you, from live counts. Saved preferences need a settings API.

RSS polling

How often feeds are checked

Read-only
Scheduler check
The scheduler looks for new articles. Individual sources can poll at their own interval on the Data Sources page.
Every 3 minutes
Polling and AI processing
A slow AI step never delays feed polling, and the reverse.
Independent

Keyword filtering

Which articles are read further

Read-only
Relevance threshold
Articles scoring below this are filtered out and never fetched in full.
0.40
Ruleset
Incident, vehicle, road, place and traffic-impact terms. A match only means “read further”. It never means “verified”.
Zimbabwe road-safety keywords

AI processing

How articles become incident candidates

Read-only
Extraction model
Each run records its own model name and version.
Reported by each extraction run
Privacy redaction
Sender names and phone numbers are masked before text leaves the pipeline.
Before every AI call
Candidate threshold
Events below this confidence are kept on the article but do not become incident candidates.
0.50
API credentials
Keys live on the server. The browser cannot read or change them.
Never shown here

Editorial workflow

Rules that cannot be switched off

Fixed policy
  • Human editorial approval is mandatory. AI output can never publish anything.
  • An approval applies to one exact bulletin version. Editing creates a new version that needs fresh approval.
  • Decisions and bulletin versions are append-only and are never rewritten.
  • Approval and delivery are separate. An approved bulletin has not necessarily reached any channel.

Roles and permissions

Who can do what

Read-only
Roles and whether each can record editorial decisions
RoleWhat it is forCan decide
adminManage sources and settings. May record editorial decisions.Yes
editorReview evidence and approve, reject or request changes.Yes
contributorSubmit and annotate reports. Cannot record decisions.No
serviceAutomated and AI accounts. Can draft, can never review.No
These rules are enforced by the server and the database. Hiding a button in the browser is never security, and roles cannot be changed from here.