The security company's management system: schedule, clock-in, patrols, weapons and pay — in one place.
Sign-in for managers and employees.
An unusual pattern at a specific site, post, or piece of equipment — more than what happened there before. Not a final finding, and not a judgment on an employee (a name never appears here): it needs a look from someone who knows the site.
What has happened on this screen since you signed in. The permanent, complete record — who clocked in, who changed the shifts, who corrected attendance — lives in the audit log on the server and cannot be deleted.
Simulated preview — not a real action on the server, and it does not touch your data. Clicking the button runs a staged 19-second sequence: a guard doesn't show up for a night shift, the system detects the gap and sends an alert, then a replacement is shown stepping in. The first two steps — detection and the alert — already happen today automatically and in real time, on real data. The third step, assigning the replacement, is today a manager's click; this preview shows what it will look like once the automatic staffing engine is connected and does that step on its own too. You can stop it partway and run it again with "Reset".
Magen is the engine that builds the shifts. The name itself means Shield — and that's exactly what it does, in three words: Assigns every post, Holds the legal limits, And stays loyal to the worker. Instead of a site manager spending a whole day on Excel and phone calls, the engine takes every availability request the employees submitted, checks each assignment against labor law, and splits nights and weekends evenly among everyone — in one click.
| Employee | Availability submitted? | Reminders |
|---|
How it works: Every employee submits by Wednesday 18:00 — by voice, by text, or on the grid — in My Area. The system automatically reminds anyone who hasn't submitted: Sunday–Monday once a day, from Tuesday twice a day — until they submit or submissions close. On Wednesday evening Magen builds the shifts, and on Thursday every employee gets their shifts on their phone.
What Magen checks on every assignment: that no one works more than 12 hours a day, no one exceeds the overtime cap, and everyone rests at least 8 hours between shifts — including the transition from one week to the next. It assigns shifts based on the availability employees submitted, and splits nights and weekends evenly. Shifts that take a manager a whole day to build, with all the phone calls and arguments — are built here in one click, and reports exactly how many checks it passed and how many violations it found.
Leave the account on this device. You can sign in again with your phone and password.
Each calculation is built from the employee's classified hours (regular, 125%, 150%, Shabbat) times their rate, plus travel and the statutory deductions from the company settings. Every active employee is linked automatically — nothing to set up. A published calculation never changes; a correction issues a new version that points to the previous one. The official payslips (PDF from accounting, released on the 9th) are managed under official payslip management.
| Employee | Hours | Gross | Net | Status | Read | Consent | |
|---|---|---|---|---|---|---|---|
| Choose a month and click "Build drafts". | |||||||
Each employee's classified hours (regular, 125%, 150%, Saturday) and the export for accounting live on the management board.
| Site | On site now | Status |
|---|
Every user sees and does only what's within their scope: the boss sees everything and can do everything. A site manager manages only their own site — its employees, chats and invites. Anyone above you in the chain can remove you; you can't remove anyone above you. An employee's phone number is visible only to their direct manager — everyone else sees "Phone hidden".
Enter a name, phone number and email — the system creates a personal activation link and emails it; you can also pass it on by WhatsApp or SMS. The employee opens the link, chooses a password and goes straight into the right site.
A new client arrives with a list. Paste the columns from Excel here — name, phone, role, site (and email, if any) — and the system creates an account and a personal activation link for each person. A row that fails is reported with its reason and does not stop the rest.
A client is the other side of the contract, and a site is not a client: one client holds several sites and one contract covers them all. Every clause you type here is measured against the site's real data. A clause you leave empty is not measured and is not counted — so an empty contract will not get a score.
Cameras, alarms, access control, gates and lighting. There is no live monitoring here — Mifkada has no connection to the systems on site, and anyone showing "98% camera uptime" without such a connection is making it up. What is measured is a human inspection: who checked, when, and what they found. An item marked faulty opens an incident immediately.
What the contract requires: how often a patrol is due, and which checkpoints must be visited on every round. A checkpoint with coordinates carries location proof; one without carries only a tap. Frequency 0 = the site does not require patrols.
Every weapon by serial number. Issue only to someone whose firearm licence and shooting refresher are valid; the employee confirms receipt in their profile; taking it back returns it to the armoury. Every issue and return is kept in a log that is never deleted. Exceptions appear here at the top and go to the site manager.
What's created here is available to every field employee through their "Forms" card — by default for every site, or for one site only.
What was planned against what was actually delivered, per site: hours, posts, patrols, incidents and response times, equipment checks and contract clauses. Every number is a row count, not an estimate — and a site with no requirement defined gets no compliance percentage for it.
| Site | Hours delivered / planned | Posts staffed | Patrols | Incidents · response | Contract |
|---|---|---|---|---|---|
| Loading… | |||||
Hours accrued from actual clock-ins in your scope. "Manual" are hours a manager recorded by hand, not measured against the site radius; "outside the radius" is a clock-in measured far from the site.
| Employee | Site | Hours | Of which manual | Shifts | Outside site radius |
|---|---|---|---|---|---|
| Loading… | |||||
An emergency alert is not broadcast to the whole company. It goes down one level only — to the sender's direct reports — and up to their direct manager. If no one acknowledges within 20 seconds, the alert escalates one level, and so on up to the general manager.
All of these channels work right now, without paying anyone: they use what is already on the employee's phone and browser.
Invitations, passwords, and messages are sent with one tap — a conversation opens with the text ready.
Tapping an employee's number calls them from the computer or the phone.
An emergency call pops up as a notification even when the system is in the background or in another tab.
Verifies that the guard is on site when clocking in — via the phone's GPS.
The employee scans the code off the screen and is signed in — without typing anything.
The employee downloads the weekly shifts straight into the phone's calendar.
| What is allowed | General manager | Regional manager | Site manager | Guard |
|---|---|---|---|---|
| Open and close a site | ✓ | — | — | — |
| Onboard and dismiss employees | ✓ | ✓ | Own site | — |
| View an employee's personal file | ✓ | ✓ | Own site | — |
| Edit employee details | ✓ | ✓ | Own site | — |
| Move an employee between sites | ✓ | ✓ | — | — |
| Create and delete chat channels | ✓ | ✓ | Own site | — |
| Management Dashboard and profitability | All | — | — | — |
| Audit log | ✓ | — | — | — |
| Build the shifts | ✓ | ✓ | Own site | — |
| See who is on site | All | Own region | Own site | — |
| Reset an employee's password | ✓ | ✓ | Own site | — |
| Personal app and shift swaps | ✓ | ✓ | ✓ | ✓ |
Permissions follow the signed-in user: everyone sees only the people below them in the management chain, and enforcement happens on the server, not by hiding screens.
Tick ✓ whoever you want to delete. What is ticked is deleted permanently with all its history (shifts, clock-ins, messages, availability, patrols, weapons, payslips). What is not ticked stays. Before deleting you see the list of names and must type DELETE.
| Delete | Name | Role | Site | Ever signed in? | History |
|---|---|---|---|---|---|
| Loading… | |||||
A ticked ✓ site is closed permanently: its shifts, attendance points, checkpoints, positions and patrol plans are deleted. Attendance history of employees who stay is kept, and anyone assigned to a closed site moves to the first remaining site. At least one site must remain.
| Delete | Site | City | Active employees | Shifts |
|---|---|---|---|---|
| Loading… | ||||
Adds 20 fictitious test employees to the site you choose and places them in the work schedule for this week (shifts that have not started yet) and next week — automatic build, top-up for shift leads and the control room, and publishing, just as a manager would. They are marked "Test employee", get no emails or no-show reminders, and anyone who has not clocked in is not counted as missing in Live status or on the management dashboard. A week that already has a schedule is left alone. Test employees are never added to a site with real field staff. Clicking again creates no duplicates. To try the employee screen: "Personal file" → "Reset password" gives a one-time password (sign in from a private window); for shift leads and the control room — "Issue link" in "Who sees what — permissions".
| Name | Role | Site | Access | Status |
|---|
Clicking "Personal file" opens the employee's full details — ID number, phone, address, pay, weapon and notes. Only a manager can see this. Termination requires a second click to confirm, and the employee is not deleted — they move to "Terminated" status with their full history kept.
Since October 2023, every security company in Israel knows the drill: an Order 8 goes out, and suddenly a fifth of your guards don't show up. Drag the slider to see what happens to coverage when a given share of each team is gone, and which site is left exposed — a planning exercise on your sites' real post counts.
The Enforcement of Labor Laws Act makes the client civilly liable for the wages of the contractor's employees, and its defense is a certified wage auditor's check. This report is your sales tool in front of that client — and a single fine avoided (up to ₪42,100 per violation, 2026) pays for the system.
For every site, in real time: what the client pays per hour, what the hour really costs you (wages per the sector extension order + social benefits + night and weekend premiums) — and what you keep. A site that loses money is flagged immediately, not at year end.
| Site | Client pays per hour | Costs you per hour | You keep | Status |
|---|---|---|---|---|
| Government Complex, Tel Aviv | ₪92.00 | ₪78.40 | ₪13.60 | Profitable · 15% |
| Ofek Tower, Petah Tikva | ₪88.50 | ₪76.10 | ₪12.40 | Profitable · 14% |
| Capital Mall, Jerusalem | ₪79.00 | ₪73.90 | ₪5.10 | Thin margin · 6% |
| Hotel, Dead Sea | ₪71.00 | ₪74.20 | ₪3.20 loss | Losing money! |
Every requirement by role, site and position — firearm licence, shooting refresher, certification and first aid. Magen blocks an assignment when the validity has expired — across the hours of the shift, not by today's date.
| Employee | Qualification | Status | Shifts after expiry |
|---|---|---|---|
| Loading… | |||
A guard finishing a shift reports what happened in it. An open defect reaches the site manager, the regional manager and the security officer immediately, and stays open until someone closes it.
Every appointment, termination, attendance correction, hours change and shift build is recorded here. Rows are hash-chained: no middle row can be changed or deleted without breaking the chain.
| When | Who | What | Details |
|---|---|---|---|
| Loading… | |||