How It All Works
A plain-language tour of how the REDENES app fits together: the five tabs, the modules behind them, and how one shift flows from sign-in to closing an incident.
Agencies & Roles
How agencies, memberships, ranks, statuses, groups and administrator roles decide what you can see and do in REDENES, and how to switch your active agency.
How Data Updates
What REDENES downloads when you sign in, what it fetches on demand, what stays cached on your device, and how the edits you make find their way back to the server.
Working Offline
Which parts of REDENES keep working without a signal, which turn read-only, what gets queued for later, and the banners that tell you where you stand.
How Alerts Reach You
Follow an alert from the moment something happens to the sound your phone makes: push delivery, critical alerts, duty states, muting, repage and escalation.
Device Permissions
Every device permission REDENES asks for, the reason it needs it, and exactly which features stop working if you say no - plus how to change your mind later.
Devices & Sessions
How REDENES identifies your device, what a session is, what happens when you sign in on more than one device, and how the screensaver and timeouts behave.
Life of an Incident
Follow an incident from the first dispatch through active response, command and closure, and see which screens and records are involved at each stage.
Choosing How to Talk
Chat, campaign, phone call, push-to-talk, radio and conference side by side - who receives each one, whether it is logged, and when to reach for which.
Why Screens Differ
Why two agencies running REDENES can see different forms and checklists on the same screen, how to recognise a server-built screen, and how saving works.
Glossary
Plain-language definitions for the abbreviations and REDENES-specific terms you meet across the app, from PAR and GAR to codeplug, isochron and Server UI.