
## One operational system for guard teams, control rooms, and client reporting

Security operations break down when every workflow lives in a different place. Incident notes sit in chat groups. Patrol checks sit in logbooks. Guard movement is reconstructed from phone calls. Client updates depend on whoever has time to write a summary.

MyProtektor brings those workflows into one mobile-first platform for field teams and control rooms.

## What MyProtektor connects

### Incident reporting

Guards can report incidents from the mobile app with structured details, photos, timestamps, and location context. Admins review incidents in the dashboard before publishing client-visible updates.

### GPS guard tracking

Guard movement history gives operations managers a clearer view of where teams were during a shift. Routes, timestamps, and activity context help turn presence into evidence.

### QR patrol verification

Patrol checkpoints use cryptographically signed QR codes. Guards scan checkpoints from the mobile app, and the dashboard shows patrol activity, overdue points, and scan history.

### Panic alerts and response coordination

The panic workflow captures location, identity, and device context so the control room can see who raised the alert and coordinate a response from the dashboard.

### Client-ready visibility

Clients only see what your team publishes. MyProtektor keeps internal operational work separate from client incident updates, so communication stays professional and controlled.

## Built for practical rollout

MyProtektor is designed for teams that need operational visibility without proprietary hardware. Guards use Android or iOS smartphones, admins work from the web dashboard, and the same platform supports field reports, patrol evidence, control-room activity, and client communication.

[Book a demo](/contact) | [View pricing approach](/pricing)


Security Operations Software for Modern Guard Teams


## The phone call you dread on Monday morning

A property manager rings your office. "My tenants say they didn't see a guard all weekend. Were your people actually there?"

You know the guards were on site. You're fairly sure. But you have no way to prove it. The patrol book might have entries, or it might not. Even if it does, anyone could have written those times in advance. You end up calling the shift supervisor, who calls the guard, who says "yes, I was there." The property manager doesn't buy it.

This is the accountability gap that costs security firms real money. Not because guards aren't doing their jobs, but because there's no verifiable proof that they did.

## How MyProtektor handles it

### Live guard positions on one map

The Guard Tracking Map shows every guard's real-time position on Google Maps. A sidebar displays four status metrics, Active, Responding, Available, and Unassigned, so you can assess operational capacity at a glance. Each guard appears as a card with their name, current status, and time since last GPS update. If a guard's device goes silent, you see it immediately.

![Guard movement history showing shift route, timestamps, and playback controls for patrol proof](/images/solutions/prove-guard-presence/guard-movement-history.png)

### Live map and historical proof work together

Guard tracking is useful because it combines live visibility with historical evidence. You can see where people are now, and later prove where they were during a specific shift.

![MyProtektor live guard map showing current locations, statuses, and active guards](/assets/images/screenshots/web/team/team-map.png)

The live team map shows active guards, site context, and current operational status at a glance.

![MyProtektor movement history view showing shift route playback and timestamped path history](/assets/images/screenshots/web/team/movement-history.png)

Movement history then turns that live data into audit evidence. This is the screen you open when a client asks for proof.

### Movement history for every shift

Select a guard and a specific shift, and you see exactly where they went. A route polyline connects every recorded GPS point, with start and end markers. Four stats summarise the shift: total GPS points, distance covered, active time, and idle time. Playback controls let you step through the route and watch the shift unfold on the map.

This is the evidence layer. When a client asks whether guards were on site, you show them the route, timestamps, distance, and all.

### Battery-adaptive GPS intervals

GPS tracking adjusts frequency based on battery level. More frequent updates when the phone is charging or above 50%, less frequent when battery drops below 20%. Guards can complete a full shift, even a long one, without the app killing their phone. No dedicated GPS trackers needed.

### Offline detection

A server-side function checks every 30 minutes for guards whose GPS data has gone stale. If a guard's phone dies, loses signal, or the app gets killed by the operating system, the system flags them as offline with the exact time of last contact. You can act on it before the client notices.

## Why this matters for your business

**Disputes die on arrival.** When a client questions guard presence, pull up the movement history for that shift. The route, the timestamps, the distance, the conversation moves from "were they there?" to "what should we focus on next?"

**Guards are protected too.** A guard who did their job has data to back it up. If a resident claims they "never saw anyone," the GPS data shows the guard was walking the perimeter at 3 AM.

**Problems surface early.** Offline detection means you catch a dead phone or lost signal during the shift, not the next morning when the client calls. And when a [panic alert](/solutions/emergency-response) fires, the same GPS system shows your admin which guards are nearest, so assignment decisions happen in seconds, not minutes.

**Reports preserve the evidence.** GPS movement history is retained for 30 days. Need to keep it longer? Generate a Guard Movement report (PDF or CSV) and archive it. Guard Reports and Performance Dashboard exports are also available for client or internal use.

## No new hardware required

Everything runs on the guards' existing smartphones, Android or iOS. No dedicated GPS trackers to buy, no SIM cards to manage. The mobile app handles location tracking, battery-adaptive intervals, and offline data sync. A guard starts their shift, and tracking begins automatically. Each guard's GPS history is also accessible through their [team profile](/solutions/guard-team-management), alongside their certifications, skills, and shift records.

For detailed setup instructions, see the [Guard Map documentation](/docs/admin/team-map). For battery and data impact, see [Battery & Data Usage](/docs/admin/battery-and-data-usage).

[View pricing →](/pricing)


Use the same guard location context when panic alerts arrive.

Give operators live visibility into guards, incidents, and patrol activity.

GPS guard tracking software for security operations. Prove patrols, view live guard locations, review shift routes, and export movement reports.

GPS Guard Tracking Software

GPS Guard Tracking - Prove Every Shift with Location Data


## A guard is in trouble. How long before your control room knows?

This happens every week in field security operations. A guard at a commercial property phones the control room at 3 AM, whispering that someone is cutting through the perimeter fence. The operator asks where exactly. The guard says "near the loading bay, I think." The operator asks which property, the guard gives a street name but cannot remember the complex number.

By the time someone works out the address, finds an available guard on the radio, and confirms they are actually nearby, eight or nine minutes have passed. The situation could escalate, the guard could be in danger, and your company has zero documented proof of what happened.

The problem is not lazy operators or careless guards. The problem is that phone calls are a terrible way to handle emergencies. They carry no location data, no identity verification, no timestamps, and no audit trail.

## How MyProtektor handles it

### One-tap panic replaces five phone calls

When a guard, or a client, taps the panic button on the MyProtektor mobile app, five things happen at once. GPS coordinates arrive instantly, so the operator knows exactly where the alert came from. The reporter's identity is confirmed automatically, name, role, phone numbers, emergency contact. Device status shows battery percentage and network type, so the operator knows if they might lose contact. The emergency is categorised immediately into one of five types: panic, medical, fire, security, or evacuation. And a timeline starts recording, logging the exact moment the alert was triggered and when it was acknowledged.

Your operator does not need to ask a single question to begin coordinating the response.

![Panic alert details showing GPS, reporter identity, and device status in the MyProtektor control room](/images/solutions/respond-faster-emergencies/panic-alert-details.png)

### Incidents tracked through their full lifecycle

Emergency alerts land on the [operations board](/docs/admin/operations-board), alongside every other active incident. Four Kanban columns mirror how control rooms actually work: Incoming alerts that need attention, Dispatched incidents with guards assigned, Attention for situations needing escalation, and Resolved for completed cases. Every status change is timestamped with the responsible person.

Guards can also report 21 incident types beyond emergencies, from theft and trespassing to medical emergencies and noise complaints. Each report captures GPS coordinates, photos, and severity level (low, medium, high, critical).

### Guard assignment from the map

When a panic alert arrives, your admin opens the [guard tracking map](/docs/admin/team-map) and sees which guards are nearest to the incident. Distance is shown as an aid. The admin selects a guard and assigns them manually. This is a deliberate design choice, your experienced operator makes the assignment decision, not an algorithm that doesn't understand your sites or your team.

![Guard assignment map showing available responders and emergency context for dispatch](/images/solutions/respond-faster-emergencies/guard-assignment-map.png)

### Guards and clients use the same emergency system

Emergency response is not web-only. Guards receive assignments on the mobile app, and client users can trigger enabled emergency workflows from the same platform with role-based visibility and controls.

![MyProtektor guard mobile app showing a high-priority emergency assignment notification](/assets/images/screenshots/mobile/guard/notification.png)

When control room staff assign a responder, the guard gets a clear mobile alert immediately instead of relying on a call chain or WhatsApp message.

![MyProtektor guard mobile app showing active assignments with location and status details](/assets/images/screenshots/mobile/guard/assignments.png)

The guard then sees the assignment context on the phone: what happened, where it happened, and what needs to happen next.

![MyProtektor client mobile app showing a one-tap panic alert screen](/assets/images/screenshots/mobile/panic.png)

Client users use the same emergency infrastructure when the security company enables it. Their alert reaches the same control room workflow with GPS context and identity attached.

## Why this matters for your business

**Response time becomes measurable.** The system logs two timestamps: when the alert was triggered and when it was acknowledged. That's the number clients and insurers always ask for, and now you have it documented automatically. The [guard tracking map](/solutions/guard-tracking) shows who responded, from where, and how long it took to get there.

**The full incident lifecycle is traceable.** From the first report through assignment, investigation, and resolution, every step is recorded with who did what and when. No more reconstructing events from memory after the fact.

**21 incident types cover real operations.** Theft, robbery, burglary, vandalism, trespassing, assault, medical emergency, fire, suspicious activity, your guards categorise accurately at the point of reporting, not after the shift when details get fuzzy.

## Getting started

Same app, same phone. Guards and clients tap one button. No special hardware, no training beyond "tap here if there's an emergency." Panic alerts work on all plans, it's a core feature, not a premium add-on.

The panic button is a single tap, not continuous background tracking, so battery impact is negligible. If signal drops at the moment of the alert, the panic queues locally and sends the moment connectivity returns, the GPS coordinates captured at the time of the tap are preserved. Once the emergency is handled, the full incident lifecycle, from alert through resolution, is managed on your [control room dashboard](/solutions/control-room).

For step-by-step guidance on managing incidents, see the [Operations Board documentation](/docs/admin/operations-board) and [Incident Map documentation](/docs/admin/incident-tracking).

[View pricing →](/pricing)


Use guard location context to decide who should respond.

Manage alerts through the same incident board operators use every day.

Emergency response software for guard teams. Send panic alerts with GPS, identity, device status, incident workflow, and control room assignment.

Panic Button for Security Guards

Emergency Response - From Panic Alert to Guard Assignment


## The logbook says the patrol was done. Was it?

At security sites everywhere, a guard writes "22:00, Main Gate checked" in the logbook. Maybe they were there. Maybe they wrote it from the guardhouse. Maybe they wrote five entries at once at the end of their shift. You have no way to know.

When a client asks for proof that patrols happened, the logbook gives you handwriting and good intentions. That is not proof, it is a liability.

Paper patrol records cannot tell you when a checkpoint was actually visited, whether the guard was physically present, or if critical points were skipped entirely. You find out about missed patrols only when something goes wrong, a break-in at the warehouse that should have been checked hourly, a fire door left unlocked at the loading bay.

## How MyProtektor handles it

### Cryptographically signed QR checkpoints

Guards scan QR codes at physical checkpoints using the MyProtektor app on their smartphone. Each QR code is signed with Ed25519 cryptography, and the signature is verified on the device itself, no internet connection required at the point of scan. A photocopied or photographed QR code fails verification instantly.

Each scan captures the checkpoint identity, an exact timestamp, the guard's GPS coordinates, the checkpoint's priority level, and an optional photo to document conditions at the point.

To be transparent: the system records the guard's GPS position but does not validate it against the checkpoint's physical location. The QR code itself, physically mounted at the checkpoint, is the proof of presence. The guard has to be standing in front of it to scan it.

![QR checkpoint watchlist showing overdue, due soon, and on-schedule patrol points with timestamps](/images/solutions/stop-missed-patrols/overdue-alerts.png)

### Patrol setup lives at site level

Patrol verification is not just a watchlist. It starts with site setup, checkpoint creation, and printable QR assets that guards can use in the field.

![MyProtektor site monitoring dashboard showing patrol status across client sites](/assets/images/screenshots/web/site-monitoring.png)

At the site-management level, operations staff can see where patrol risk is building up across the portfolio before a client raises the issue.

![MyProtektor site details screen showing site-level patrol context and assigned operational data](/assets/images/screenshots/web/site-view.png)

Each site then becomes the working area where patrol points, checkpoint status, and local operational detail are managed.

![MyProtektor QR creation dialog for creating signed patrol checkpoints](/assets/images/screenshots/web/qr-create.png)

Checkpoint creation happens in the dashboard, where you define the patrol point and generate the signed QR code.

![MyProtektor QR print dialog showing checkpoint QR code ready for deployment on site](/assets/images/screenshots/web/qr-print.png)

Once created, the code is printed and mounted at the real-world checkpoint where the guard must physically scan it.

### A dashboard that shows what's overdue before you ask

The QR Checkpoint Watchlist on your main dashboard displays up to 12 checkpoints, sorted by urgency. Four states give you the picture at a glance: overdue checkpoints where the expected interval has passed, due soon checkpoints approaching their window, never scanned points that have not been checked since creation, and upcoming points with time remaining.

Critical and high-priority checkpoints that are overdue appear first. You see the problem before the client calls about it.

### Offline-resilient by design

Security sites often have connectivity dead zones, basements, parking garages, rural perimeters. MyProtektor handles this by queuing scans locally on the device when there's no connection. Data syncs to the cloud automatically when the guard moves back into signal range. No scan is ever lost.

![MyProtektor guard mobile app showing patrol history and checkpoint verification on the phone](/assets/images/screenshots/mobile/guard/patrol.png)

## Why this matters for your business

**Forgery is not an option.** Ed25519 cryptographic signatures mean a QR code cannot be duplicated, photographed, or faked. The guard's phone verifies the signature before accepting the scan. Paper-based patrol systems have been gamed for decades, and some companies have lost contracts because they could not prove patrols happened.

**Problems surface before incidents happen.** When a checkpoint goes overdue, you know immediately. You can call the guard, reassign the round, or investigate, instead of discovering the gap after a break-in. The watchlist on your [control room dashboard](/solutions/control-room) flags overdue points sorted by priority, so the most critical checkpoints get attention first.

**Audit-ready records.** Every scan is timestamped with GPS data and guard identity. When a client, insurer, or auditor asks for patrol records, you export the data as a PDF or CSV report, not a stack of logbooks that may or may not be legible. Patrol Analytics reports (Professional plan) give you completion rates and patterns over time.

**Guard accountability without micromanagement.** The system does not tell guards how to do their job, it proves that they did. Guards follow their normal routes, scan checkpoints as they pass them, and the dashboard confirms the round was completed. For security firms managing multiple sites with rotating guards, this turns patrol compliance from a trust exercise into a documented fact.

## Getting started

Print the QR codes from your dashboard, mount them at the physical locations guards must visit, and organise them into folders by site. Set priority levels and check intervals per checkpoint. Guards scan with their phone, no additional hardware, no special training.

Patrol verification requires the Professional plan. For setup instructions, see the [Patrol Points documentation](/docs/admin/patrol-points).

[View pricing →](/pricing)


Patrol Verification - QR Proof at Every Checkpoint


## The WhatsApp problem every security company knows

A guard reports a break-in attempt at a residential site. Within minutes, the client chat is flooded, residents asking questions, sharing rumours, posting unverified information. Every security company managing residential or commercial contracts knows this scenario. Your operations manager is fielding calls from the client, the site manager, and people who saw the messages.

The incident was handled. The guard responded correctly. But the communication turned a controlled situation into a crisis of confidence.

WhatsApp groups are fast, but they are uncontrolled. Anyone can post anything. There is no review process, no editorial control, and no way to ensure clients see only verified, accurate information.

## How MyProtektor handles it

### One app, role-based access, no separate client portal

MyProtektor uses a single app for everyone: guards, admins, and clients. The difference is what each role can see. There is no separate "client portal" or "client app" to install and maintain, visibility is enforced by the platform based on the user's role.

Owners and Admins see everything: all incidents, guard tracking, patrol monitoring, analytics, and team management. Guards see incidents, can file reports, scan checkpoints, and manage their shifts. Clients see published incidents for their assigned sites.

### The publish toggle, editorial control built in

When a guard files an incident report, it enters your internal workflow. Admins see it immediately and can investigate, assign guards, update the status, and add notes. The incident stays internal until an admin explicitly toggles it to published.

This is a deliberate action, not an automatic process. Your admin reviews the report, ensures the information is accurate and appropriate, and then publishes it. Only then does the client see it.

Draft reports, guard locations, internal notes, and operational communication stay invisible to clients, always.

![Publish toggle on incident detail showing admin control over client visibility](/images/solutions/keep-clients-informed/publish-toggle.png)

### Client panic button

Client users can use the same one-tap panic infrastructure as guards when enabled by the security company. Their alert reaches your control room with GPS coordinates, timestamp, and identity, the same priority and data quality as a guard's alert.

### What clients actually see in the app

The client experience is not theoretical or hidden behind a sales promise. Clients get a real mobile app with a dashboard, incident feed, live map, and role-limited emergency workflow.

![MyProtektor client mobile dashboard showing nearby incidents, status, and quick actions](/assets/images/screenshots/mobile/dashboard.png)

The dashboard gives clients a quick read on what is happening around them without exposing internal operator tools.

![MyProtektor client mobile incidents feed showing published incidents with photos and details](/assets/images/screenshots/mobile/incidents.png)

The incident feed is where published updates live. Clients see reviewed information, not internal draft notes or guard chatter.

![MyProtektor client mobile live map showing published incident activity in the surrounding area](/assets/images/screenshots/mobile/map.png)

The live map gives neighbourhood context while still respecting privacy and publication controls.

![MyProtektor client mobile panic alert screen for one-tap emergency escalation](/assets/images/screenshots/mobile/panic.png)

And when the situation is personal and immediate, the panic button is one tap away inside the same app.

## Why this matters for your business

**Professional image.** Your clients see verified, reviewed information through a professional interface, not a chat thread where anyone can post anything. That is the difference between a security firm that manages communication and one that reacts to it. For residential and commercial properties, this is often the difference between retaining a contract and losing it.

**Editorial control prevents damage.** A false alarm reported by a guard stays internal until you confirm it. A sensitive incident involving a specific resident is reviewed before clients see details. A break-in that was handled cleanly gets published with the right framing. You decide what gets shared and when, not the most anxious person in a WhatsApp group.

**No separate systems to manage.** One app, one login, one set of credentials for every role. No "client portal" with its own maintenance, its own bugs, and its own onboarding process. When you add a new client, they download the same app your guards use. When they open it, they see only what their role permits.

**Clients and property managers get what they need.** In site security, clients want regular evidence that your company is performing. Published incidents give them a verified, timestamped record of how your team handled situations on their property. No more "can you send me a summary email at the end of the month."

## Getting started

Invite clients from your dashboard, they download the same MyProtektor app and sign in. Guards file reports through the same app they already use for patrols and shift management, so adoption is not a separate problem. If a client's phone loses signal, published incidents sync the next time they open the app, nothing is lost. Their view is automatically restricted to published incidents for their assigned sites. No configuration needed beyond the invitation.

Client communication connects to your broader operation: published incidents originate from the same [emergency response](/solutions/emergency-response) workflow your guards use, and your [control room dashboard](/solutions/control-room) shows published vs internal status at a glance.

For details on inviting clients and managing visibility, see the [Client Access documentation](/docs/admin/client-access).

[View pricing →](/pricing)


Client Communication for Security Teams

Client Communication - Professional Updates, Not WhatsApp


## Three incidents. Two panics. One operator switching between four apps

Friday night at 11 PM. A panic alert comes in from a residential site. While your operator pulls up the guard roster in a spreadsheet, a second incident report arrives from a warehouse. The phone rings, a client asking about a suspicious vehicle reported 20 minutes ago that nobody followed up on. This is what running a security control room looks like when your tools don't talk to each other.

Your operator has the incident in one app, the guard schedule in a spreadsheet, the client details in a CRM, and the site map in Google Maps. By the time they piece together who is available and where, the situation has already escalated.

Every additional tool switch costs time. Every missing piece of context creates risk.

## How MyProtektor handles it

### One dashboard, full visibility

MyProtektor's web dashboard consolidates your operational data into a single screen. At the top, four KPI tiles show your current picture: Total Incidents, Needs Attention (critical and high severity, still open), Open (awaiting resolution), and Closed. A time range dropdown lets you filter from 24 hours to 365 days.

Below the KPIs, the 10 most recent incidents appear in a table with severity, status, assigned guard, and time since creation. Open incidents are prioritised at the top. A live feed sidebar streams events as they happen, incidents, status changes, field reports from guards, so the operator on duty always has the latest picture.

![MyProtektor control room dashboard showing patrol watchlists, access control activity, and site operations widgets](/images/solutions/run-your-control-room/dashboard-operations-widgets.png)

### The control room is more than one dashboard tab

The main dashboard is the operational summary, but real control-room work moves between live map, workflow board, and reporting views without losing context.

![MyProtektor incident map showing live incidents with GPS context and map filtering](/assets/images/screenshots/incident-map.png)

The incident map gives your operator geographic awareness immediately: where incidents are happening, which sites are affected, and what needs attention first.

![MyProtektor operations board showing incident workflow from report to resolution](/assets/images/screenshots/security-ops.png)

The Operations Board is where incidents move through the workflow. Incoming, dispatched, attention, and resolved states make handovers and accountability explicit.

![MyProtektor reports page showing export-ready reporting for client and internal use](/assets/images/screenshots/reports.png)

And when a client, manager, or auditor asks for proof, reporting is part of the same environment. You do not move data into a second tool just to explain what happened.

### Incident lifecycle management

The [operations board](/docs/admin/operations-board) manages incidents through four stages: Incoming alerts that need attention, Dispatched incidents with guards assigned, Attention for situations requiring escalation, and Resolved cases. Three views, board, list, and table, let your operators work in the format that suits them. Every status change is timestamped with the responsible person.

Guards in the field send real-time updates through field reports: All is in Order, Suspicious Activity, Need Backup, or a Custom Note. These appear on the dashboard and in the operations board, giving your control room live intelligence from the ground.

### Everything else on the same screen

Guard tracking, site monitoring, patrol checkpoints, and access control activity all appear as dashboard widgets, no app switching. The [guard tracking map](/solutions/guard-tracking) shows who is where. The QR Checkpoint Watchlist flags overdue patrols. The access control widget shows the last five gate decisions. Site widgets display patrol point counts per location.

### Analytics for the bigger picture

On the Standard plan and above, the [analytics tab](/docs/admin/analytics) gives you trend data: incident trends over time, severity distribution, type breakdown, response time distribution, and guard performance rankings. This is where you move from reactive to informed, identifying patterns, comparing guard performance, and spotting operational gaps before they become incidents.

Reports and exports (Professional plan) let you generate PDF and CSV documents for clients, insurers, and internal review. Site Reports, Audit Reports, Emergency Reports, and Guard Performance reports are all available through the reports page.

## Why this matters for your business

**Faster decisions under pressure.** When everything is on one screen, the operator doesn't waste time switching between apps. The panic alert, the available guards, and the map are all visible at once.

**Multiple operators, same live data.** All data syncs in real time. Two operators can work the same shift, see the same incidents, and update statuses simultaneously without conflicts.

**Data-driven improvement.** Analytics show you which incident types spike on weekends, which guards respond fastest, and where your operation has gaps. That's how you improve, with numbers, not guesswork.

**The professional control room that wins contracts.** When a prospect visits your operation and sees a live dashboard with real data instead of a whiteboard and radio, that's a different conversation. When an insurer asks for incident response metrics, you export the report. When a client audits your record-keeping, the data is timestamped and traceable. This is the kind of operational visibility that retains contracts and wins new ones.

**What if internet drops?** The mobile app continues working offline for guards in the field. Incident reports, patrol scans, and panic alerts queue locally and sync when connectivity returns. The dashboard needs an internet connection, but the guards' work is never lost.

**Do we need special equipment?** No. Any web browser on any screen. Desktop monitors work best for control room environments, but a laptop on the ops manager's desk works too. No plugins, no installation, no IT department required.

## Getting started

Open a web browser and log in. The dashboard works on any screen. No installation, no plugins, no configuration. Your data appears the moment your team starts using the mobile app.

For detailed documentation, see the [Dashboard guide](/docs/admin/dashboard), [Analytics guide](/docs/admin/analytics), and [Operations Board guide](/docs/admin/operations-board).

[View pricing →](/pricing)


Move panic alerts through the same operational workflow.

Show live guard positions and movement history alongside incidents.

Security control room software for guard operations. Manage incidents, live maps, patrol status, access activity, reporting, and response workflows.

Security Control Room Software

Control Room Dashboard - Your Full Operation on One Screen


## Monday morning at a managed property. A resident claims they were denied entry at 7:15 AM

They are upset. They say the guard was rude. They want the guard's name and they want something done about it. Your operations manager needs to verify what actually happened.

In a traditional setup, that means finding the right logbook, hoping the entry was actually written down, and hoping the handwriting is legible. If the guard was on a different shift rotation that week, tracking down the right person adds another layer of effort.

The sign-in book gives you disputes with no resolution. Digital access control gives you data.

## How MyProtektor handles it

### Three ways to verify at the gate

Guards scan QR codes using the MyProtektor app on their existing smartphone. No special hardware, no turnstiles, no cabling.

**Resident Access IDs**, each resident has a personal QR code, cryptographically signed with Ed25519. The guard scans it, and the app verifies the signature on the device itself, no internet required. The result is one of three states: VERIFIED (resident assigned to this site), CAUTION (valid QR but not assigned to this site), or DENIED (invalid or forged code).

**Visitor invitations**, admins create a visitor invitation from the web dashboard, generating a QR code that can be shared with the visitor via WhatsApp or email. When the visitor arrives, the guard scans their invitation and captures a photo.

**Walk-up registration**, for unplanned visitors, guards register them on the spot by capturing their name and a photo directly through the app.

After every scan, the guard selects the site and taps Grant or Deny. The decision is logged immediately.

![Visitor invitation management showing invitation records and sharing controls for gate access](/images/solutions/digitise-gate-access/invitations-management.png)

### Guards verify access from the mobile app

The admin dashboard handles invitations, policies, and logs. The actual verification happens at the gate on the guard's phone, where speed and clarity matter.

![MyProtektor access control dashboard showing visitor scans, statuses, and entry history](/assets/images/screenshots/web/access-control.png)

From the web side, your operations team sees the full stream of granted, denied, invited, and walk-up events across sites.

![MyProtektor guard mobile app scanning an access QR code to verify entry on site](/assets/images/screenshots/mobile/guard/access-scan.png)

At the checkpoint, the guard scans the QR code in the mobile app, gets the decision instantly, and the event is logged back to the dashboard.

### Every decision logged and traceable

Every access decision captures the guard's identity, the resident or visitor's identity, the site, the timestamp, the verification result, and the grant/deny decision. When a resident disputes an entry decision, or claims it never happened, your operations manager opens the access log and has the complete record in seconds.

### A dashboard with three views

The access control dashboard gives admins three tabs: Activity (all gate events with summary stats, total scans, granted, denied, grant rate), On-Site (visitors currently checked in), and Invitations (create, share, and track visitor invitations). The main dashboard also shows the last five access decisions in a compact widget.

## Why this matters for your business

**Disputes end with data.** The guard's name, the timestamp, the resident's identity, and the decision, all documented automatically. No conflicting stories, no illegible handwriting, no missing logbooks. When a property manager, HOA, site manager, or operations lead asks "what happened at 7:15 AM?", you have the answer in seconds.

**Forgery protection.** Ed25519 cryptographic signatures mean a QR code cannot be photocopied, screenshotted, or faked. If someone tries to present a screenshot of someone else's Access ID, the scan fails. This matters at residential communities, campuses, facilities, and managed access sites where entry disputes are common and security teams get blamed when unauthorised people enter.

**Works offline.** QR verification runs on the device, the guard does not need internet to verify a resident. Scans queue locally and sync to the cloud when connectivity returns. Basements, parking garages, remote gates, and sites with poor signal are all covered. When network outages, weak coverage, or power disruptions interrupt cloud-only tools, offline verification keeps gate decisions moving.

**Visitor management without paperwork.** Security firms managing estate access spend hours on visitor logbooks, writing names, checking IDs, flipping through pages. Digital invitations shared via WhatsApp before the visitor arrives mean the guard scans a QR code instead of filling in a form. The visit is logged automatically.

## Getting started

Generate resident Access IDs and visitor invitations from your web dashboard. Share them via WhatsApp or email. Guards scan with the same MyProtektor app they use for everything else, no new hardware, no gate integration, no cabling. Access control requires the Professional plan.

Access control data feeds into your [control room dashboard](/solutions/control-room) via a compact widget showing recent gate decisions, and connects to [guard tracking](/solutions/guard-tracking) since guards must be on an active shift to scan.

For setup instructions, see the [Access Control documentation](/docs/admin/access-control).

[View pricing →](/pricing)


Digital Access Control - Replace the Sign-In Book


## A client asks for proof of qualifications. The certificates are in a filing cabinet, and the key is with someone on leave

Your client needs to confirm that the guard assigned to their site holds the right security licence, training record, and current First Aid certificate. You know the guard is qualified. But the certificate is in a filing cabinet at the office. The office key is with the operations manager who is on leave until Thursday. The licence number is written on a piece of paper that nobody can find.

The guard has the skills. Your company lacks the system to prove it.

This is a compliance gap, and it surfaces at the worst possible moment: when a client, an insurer, or a regulator asks for documentation you should be able to produce in seconds.

## How MyProtektor handles it

### The guard roster, everyone on one screen

The team management page shows every person in your organisation in a single table: name, current status (On Duty or Offline), role, specialisations, and most recent activity. Summary counters at the top break down totals, who is on shift, who is on an active incident, and role distribution.

![MyProtektor team management roster showing roles, statuses, and guard records in one table](/assets/images/screenshots/web/team/manage-team.png)

Filters let you narrow the view by role (Guard, Admin, Owner), by status (On Duty, Offline), and by active incident assignment. When an incident comes in and you need to find who is available, you see it in seconds, not minutes.

### Guard profiles with five tabs

Click any guard and their unified profile opens with five tabs. **Profile** shows personal details and emergency contact information. **Work** covers employee ID, department, supervisor, and work schedule. **Skills** is where certifications live, each specialisation with cert dates, expiry, certification numbers, and uploaded documents. **Activity** shows recent logged events. **Movement** links to their shift-scoped GPS history.

Nine specialisations are tracked: Crowd Control, K9 Handler, Firearms, First Aid, Access Control, Surveillance, VIP Protection, Event Security, and Patrol. Each entry stores certification dates, expiry dates, certificate numbers, and uploaded documents, the kind of records that regulators, insurers, and clients ask for.

### Certificate expiry alerts before they become a problem

A Cloud Function runs every Monday at 8:00 AM and checks for certificates that have expired or will expire within the next 4 weeks. When it finds one, it notifies the relevant Admin and Owner via push notification, email, and the activity feed. You don't discover an expired certificate during a client audit, you know about it weeks in advance.

![MyProtektor team analytics view showing performance and certification visibility for the security team](/assets/images/screenshots/web/team/analytics.png)

Team analytics adds another management layer: beyond who is on shift right now, you can review performance patterns, certification coverage, and broader team health over time.

### Shift management, guards start when ready

Guards start their own shifts from the mobile app. There are no pre-assigned rosters or schedules, the guard taps "Start Shift," completes compliance checks (background location permission, battery optimisation disabled), and GPS tracking activates automatically. Admins see each guard's duty status on the dashboard in real time: on-duty, on patrol, break, emergency, offline, or off-duty.

![MyProtektor guard mobile app showing active assignments and daily operational context](/assets/images/screenshots/mobile/guard/assignments.png)

This is a deliberate design. Field security operations often have variable schedules, last-minute changes, and guards covering for each other. A rigid pre-assigned roster would create more friction than it solves.

## Why this matters for your business

**Compliance readiness.** When a client, insurer, or regulator asks for guard qualifications, you open the profile and show the certificates. Digital records with dates, numbers, and uploaded documents, available in seconds from any device.

**Smarter assignment.** When an [emergency](/solutions/emergency-response) needs a specific skill, firearms for a high-risk escort, First Aid for a medical emergency, K9 for a perimeter breach, you know who has that qualification and who is on duty.

**Reduced admin overhead.** No paper filing cabinets, no spreadsheets tracking expiry dates, no manual reminders. The system tracks it and alerts you before anything lapses.

## Getting started

Guards download the MyProtektor app and sign in. Admins complete their profiles, personal details, work information, and certifications, from the web dashboard. The guard's mobile app shows only what they need for their daily work. No separate HR system, no data migration, no training beyond the initial profile setup. Once a guard starts their shift, their [GPS movement history](/solutions/guard-tracking) is recorded automatically and accessible through the Movement tab in their profile.

For step-by-step instructions, see the [Guard Management documentation](/docs/admin/team-management) and [Profile Settings documentation](/docs/admin/profile).

[View pricing →](/pricing)


MyProtektor Solutions