For years, the routine might have been simple. The adults left in the morning, the house was armed, and someone disarmed it in the evening. Then the routine changed. An older child now walks home from school and comes in through the back door before anyone else is home. One parent leaves early while the other is still inside. At two in the morning, someone is up with the baby, walking down the hallway to the kitchen and back.
The house is the same. The alarm system may be exactly the same. What has changed is what the family wants it to tell them.
That shift brings one distinction to the surface quickly: knowing that something happened isn’t the same as knowing who did it. A door opening is one piece of information. Who used the alarm is another.
The Alarm Hasn’t Changed. The Questions You Ask It Have
When a household is small and keeps a shared schedule, an alarm mostly has one job. The question it answers is roughly: did something happen while nobody was supposed to be home?
That question doesn’t go away as the family grows. It just stops being the only one. Once several people come and go on different timetables, through different doors and at different hours, the alarm becomes part of everyday life rather than something switched on when the house is empty.
The questions a growing family starts asking:
- who has interacted with the system, not just whether something happened;
- which entrance people actually use day to day;
- what should stay protected after everyone goes to bed;
- who needs which notifications;
- who should be able to see images from inside the home.
None of these is about buying more equipment. They’re about what the existing system records, who it tells and when.
A Door Opening Isn’t the Same as Knowing Who Came Home
It’s easy to treat “the back door opened” and “my son got home” as the same piece of news. To an alarm system, they’re not.
A door detector records an opening at that door. That’s its whole job. Separately, when someone disarms the system, the system records that interaction and, depending on how it was done, may also record which user did it.
Ajax’s KeyPad Plus is a clear documented example. When someone enters a personal code, the username is displayed in the notifications and events feed. When someone uses the keypad’s common code, the device name is displayed instead. Ajax’s Tag key fobs and Pass cards follow the same logic: when the credential is bound to a user, the username appears in the notifications and events feed.
So a personal code or an assigned Tag can identify the user who disarmed the system. In a family routine, that can be useful context around someone arriving home. But it records the interaction with the security system, not the person’s physical arrival. The door event and the disarm event are two separate entries, and the system doesn’t combine them into a statement about who walked in.
That’s why it matters how each family member operates the system. A shared code tells you the keypad was used. Personal codes or assigned Tags tell you which user used it. Neither turns the alarm into a way of tracking people.
The Back Door Becomes Part of the Family Routine
As children become more independent, the front door may stop being the only entrance that matters to the family. A child comes through the side gate and in through the back. Someone steps out to the yard and back in again. Different family members settle into different doors.
That changes what the household wants to know about an entrance while people are home and the system is disarmed. One documented example is Ajax’s Chime feature. With the system disarmed, sirens and keypads with a built-in buzzer can make a short sound when selected opening detectors are triggered. It’s set up detector by detector, so the back door can chime while other openings stay quiet.
It’s worth being clear about what Chime is. Ajax states that when the feature is enabled, detector-triggering notifications aren’t sent to the Ajax apps; only the sirens at the property sound. So Chime can tell someone in the house that a chosen door has just opened. It doesn’t send a parent at work a message about it. Local awareness and a remote notification are different things, and a family planning around the back door needs to know which one it’s actually setting up.
A New Baby Changes What “Armed at Night” Needs to Mean
Before the baby, night might have been simple: everyone in bed, alarm on. With a newborn, the house doesn’t go still after bedtime. Someone gets up, walks down the hallway, heads to the kitchen and comes back. A full-house arming setup that suited a sleeping household can sit awkwardly with that.
Ajax documents one way of handling this, called Night mode. Rather than arming everything, it arms only the devices set to take part. Opening, glass-break and motion detectors, as well as cameras, can each be included or left out. Ajax describes the purpose plainly: keep doors and windows protected while you sleep, while still being able to move freely inside the home. It can be switched on manually or scheduled before bed.
The point isn’t the feature name. It’s that “armed at night” doesn’t have to mean everything armed or nothing armed. It can mean the outside of the house stays protected while the routes the family uses at night stay usable.
Questions to settle before planning night protection:
- which external doors and windows still need protecting overnight;
- which internal routes people actually use at night;
- which devices should form part of the night setting;
- who should be told if something is triggered overnight.
The answers will look different in a single-storey house with the nursery next to the main bedroom than in a two-storey home with the kitchen downstairs, which is why there isn’t one correct night configuration.
Not Everyone in the Family Needs the Same Notifications
As more people use the system, notification design becomes a separate household decision. Being a system user doesn’t necessarily mean needing every notification.
Ajax groups notifications into categories, including alarms, malfunctions, changes of armed mode and other system events. According to its documentation, an admin, or a PRO with system configuration rights, can configure push notification preferences for all users, while users without admin rights can adjust their own.
That makes notifications something to decide rather than a default.
Questions worth deciding for each system user:
- do they need alarm notifications;
- do they need to know when the system is armed, disarmed or switched to Night mode;
- do they actually use the app, or mainly the keypad or a Tag;
- do they need to hear about malfunctions and other system events.
There’s no single right answer, but it’s worth deciding deliberately rather than leaving every user on the same settings.
All of this is about who inside the family hears about what. Whether someone outside the family should receive alarm events is a different question, covered in our explainer on the difference between monitored and unmonitored alarms.
Cameras Answer a Different Family Question
An alarm event and visual context answer different questions. The alarm tells you that something happened at a particular point. An image shows what was there. In a home where several people live, adding images brings a question of its own: who can see what, and under what conditions?
Ajax’s Photo on demand is one documented example. It lets users take pictures with the built-in cameras of compatible Ajax motion detectors, and Ajax itself mentions finding out what the children are doing as one possible use. Access isn’t all-or-nothing. Permissions are set per user and can allow photos at any time or only while the detector is armed. When someone requests a photo, other users of the system receive a notification naming who requested it.
There’s one documented limit to keep in mind. Ajax states that privacy settings don’t apply to photos taken when a detector is triggered in an alarm. All system users with access to the hub’s events feed can view those.
Before giving family members visual access, decide:
- who actually needs Photo on demand;
- whether their access should work at any time or only while detectors are armed;
- who has access to the events feed;
- whether everyone understands that alarm-triggered photos follow different access rules.
None of this means a family needs cameras inside the home. It means that if images are part of the system, deciding who can see them belongs in the plan, alongside who gets notifications.
If what the family wants is a full camera system rather than photos linked to the alarm, that’s a separate project, covered on our page about CCTV installation in Melbourne.
Design Around the Household, Not Just the Empty House
A growing family doesn’t necessarily need more security. It may instead need the system it already has to fit the people living with it: the children who come home on their own, the door they actually use, the way the house is used at 2 am, and who needs to know or see what.
Underneath all of it is the distinction this article started with. A door opening and a user disarming the system are different pieces of information. A system set up with that in mind gives a family clearer answers than one that treats every event the same way.
That’s why a residential alarm system planned for a family home starts with how the household actually lives, not just with a floor plan. Who comes and goes independently, which entrances matter day to day, what needs protecting overnight and who needs information are what an installer has to understand before deciding how the system should behave.
Frequently Asked Questions
What happens if an Ajax Tag or Pass isn’t assigned to a user?
It can still be used, but the system has no person to attach to it. Ajax states that when a Tag or Pass isn’t bound to a user, the device name is shown in notifications and the events feed instead of a username, and the user field in the device’s states shows “Guest”. Binding each credential to a family member is what puts names in the feed.
Will the alarm warn me if the back door was left open when I arm it?
Only if it’s set up to. Ajax’s System integrity check can prevent arming when, for example, a window isn’t closed or a device has lost connection, but it’s disabled by default. If arming with malfunctions is allowed, the user has to confirm, and everyone with access to the events feed receives a notification listing the issues. If it isn’t allowed, the problem has to be fixed first.
Does switching on Night mode count as disarming?
Not when you switch directly between modes. Ajax explains that, when group mode isn’t in use, the armed mode replaces Night mode and vice versa. Moving from armed to Night mode, users only receive the notification about Night mode activation, and the log doesn’t record a disarming event, because the system wasn’t disarmed in the app or by another device.
Can every family member see alarm photos?
Photos on demand depend on the permissions each user has been given. Photos taken when a detector is triggered in an alarm are different: Ajax states that privacy settings don’t apply to them, and all system users with access to the hub’s events feed can view them. So deciding who has access to the events feed matters as well.
Sources
- Ajax Systems — KeyPad Plus user manual
- Ajax Systems — Tag and Pass user manual
- Ajax Systems — What is Chime, and how does this function work
- Ajax Systems — What is Night mode and how does it work
- Ajax Systems — How Ajax notifies users of alerts
- Ajax Systems — What is System integrity check
- Ajax Systems — What is Photo on demand and how it works
