Updated July 2026. Matter multi-admin can place one supported device on more than one controller fabric. That can be useful when a household wants Apple Home for one set of automations and another Matter controller for different devices or users. It can also leave hidden access behind if the household treats every controller, account, role, automation, and recovery route as one permission.
The Connectivity Standards Alliance describes Matter as an IP-based application layer designed to work across ecosystems. That does not make every function portable. Read the current Matter overview from the Connectivity Standards Alliance, then verify the exact device type, Matter version, controller, Thread Border Router where needed, region, app, firmware, feature exposure, and account rules before buying or sharing access.
Map the system before opening a second fabric
| Layer | Record | Test |
|---|---|---|
| Security device | Brand, model, device type, Matter version, radio, firmware, power, battery, mount, code location, reset method, and owner | State, command, local warning, history, low battery, tamper, restart, reset, and recovery |
| Controller fabric | Platform, account owner, household, controller, hub, region, remote-access path, recovery owner, and support route | Local and remote control, controller loss, internet loss, account lockout, and restored service |
| Thread network | Border routers, credentials, placement, power, network path, firmware, and preferred owner | One border router offline, all border routers offline, power return, and route repair |
| People and roles | Owners, residents, guests, children or restricted users, installers, support users, and former members | Add, limit, remove, expire, recover, and prove the old path fails |
| Automations | Trigger, condition, action, controller, account, device name, safety limit, and rollback | Duplicate trigger, stale state, delay, controller conflict, internet loss, and manual override |
Understand what multi-admin does not merge
A device may appear in two Matter controllers while each controller keeps its own room name, household roles, scenes, automations, notification settings, history, remote-access policy, voice-assistant permissions, and account-recovery route. A lock code, camera recording plan, alarm PIN, professional-monitoring contact, garage credential, or vendor app can remain outside Matter.
Do not give a contractor, house sitter, cleaner, tenant, or short-term guest broad controller ownership just to operate one door or light. Use the narrowest role available. If the platform cannot limit the person to the required device and time, an individual lock code, alarm user, vendor guest, local keypad, or physical key may be the safer route.
Inventory every fabric and controller
- Open every home, household, building, or location in each controller app. Record the account owner, administrators, residents, guests, pending invitations, old users, recovery methods, subscriptions, and linked voice services.
- List every Matter device by model, serial or asset identifier, room, controller name, vendor-app name, firmware, radio, and fabric. Do not rely on similar display names.
- Mark the controller that owns each automation, scene, schedule, notification, remote path, and safety rule. Duplicate names do not prove duplicate logic.
- Record which device functions are missing or different in each controller. Check locks, contact sensors, motion sensors, lights, plugs, thermostats, blinds, bridges, cameras, and alarm controls separately.
- Store setup codes according to the maker’s instructions. A photographed code in a shared album, contractor thread, listing photo, or move-in document can become an access and reset risk.
Add the second controller in a controlled window
Back up names, rooms, automations, schedules, user lists, recovery routes, and important settings first. Confirm there is a working physical key or other safe fallback before testing a lock. Tell household members what will change and choose a period when doors, alarms, heating, medical equipment, garage access, and care routines do not depend on an untested automation.
- Update only the documented controller, border router, app, or device required for the commissioning path. Do not batch-update the whole property.
- Start from the controller that already owns the device and use its current multi-admin or sharing flow. Avoid a factory reset unless the exact device instructions require it.
- Record the commissioning window, code source, account, phone, controller, network, device LED or state, and final fabric membership.
- Rename the device consistently but keep a unique asset identifier in the inventory. Test a harmless state or command from both controllers.
- Check every existing automation before enabling a new one. Two controllers can issue competing commands without showing one combined rule.
Build a permission matrix
| Person | Controller A | Controller B | Vendor and security platforms | Expiry |
|---|---|---|---|---|
| Primary owner | Owner, billing, recovery, and full configuration | Owner or documented backup | Alarm, lock, camera, monitoring, and support ownership | Review quarterly |
| Resident | Only the home and devices needed | Only if a real job requires it | Individual lock and alarm credentials | Move-out date |
| Guest or helper | Time- and device-limited if the controller supports it | No access unless separately justified | Scheduled code or narrow vendor guest | End of visit or shift |
| Installer | Temporary supervised access | Temporary only for the assigned controller | No billing, monitoring, camera-history, or recovery ownership | End of job |
Apple’s current Home sharing guidance separates residents and guests and lets the home owner manage access. Apply the same least-access test to every second controller. Apple Home membership does not prove access is removed from a different Matter fabric, the vendor account, the alarm platform, or saved setup codes.
Protect security devices from unsafe cross-controller rules
- Do not let geofencing, occupancy, television state, a voice phrase, one phone, or a single motion sensor unlock, open, or disarm on its own.
- Keep smoke, heat, carbon monoxide, medical, water-shutoff, and emergency routines within their certified and documented system boundaries.
- Treat a camera, doorbell, or smart speaker as a separate privacy surface. Matter support on another accessory does not grant or remove video, audio, history, or download access.
- Use direct door and window sensors for perimeter state. A camera inference, automation state, or controller tile is not a direct alarm zone.
- Document the manual override, physical key, local keypad, siren, monitoring test mode, and recovery order before adding automation.
Test conflicts, stale state, and timing
Run each test 10 times where safe. Record the physical event time, controller A state and alert, controller B state and alert, vendor-app state, automation start, command, device response, history, and recovery. A clean test needs agreement about the physical state, not identical user interfaces.
| Test | Expected result | Failure to catch |
|---|---|---|
| Open and close a contact | Both controllers show the correct state and recover without a duplicate unsafe action | Stale tile, reversed state, delayed alert, duplicate automation, or missing history |
| Lock and unlock with a safe fallback ready | Physical bolt, door alignment, both controller states, vendor history, and access record agree | Jam, false locked state, code confusion, remote command failure, or auto-unlock loop |
| Change a shared device name or room | The inventory explains which fields synchronize and which stay local | Automation silently points at the wrong device or duplicate name |
| Disable one controller | The other controller’s documented local job continues or fails in a known way | Hidden dependency on the offline hub, account, cloud, or border router |
| End optional service | The permanent unpaid state matches the written record | Lost history, remote access, automation, alert, support, or security feature |
Run outage and recovery tests
Disconnect internet safely and record local control, remote control, automations, notifications, history, locks, direct sensors, sirens, cameras, vendor apps, and missed events. Then test one controller offline, one Thread Border Router offline, all border routers offline, and the documented AC-power-loss path. Do not create a real emergency.
Restore the network in the written order. Record how long each controller, border router, device, state, automation, history, alert, and remote path takes to recover. Check clock and timestamp accuracy. A controller that eventually reconnects can still leave a dangerous stale state during the gap.
Remove a person or fabric completely
- Remove the person from every controller household, vendor app, lock account, alarm account, camera share, garage app, voice assistant, monitoring contact list, billing account, support role, and recovery path.
- Cancel pending invitations, shared links, temporary codes, schedules, API tokens, web sessions, and old-phone sessions.
- Delete or transfer automations, scenes, shortcuts, dashboards, and notifications owned by the departing account.
- If retiring a controller fabric, follow the maker’s documented removal sequence. Reset only the devices that cannot be removed safely another way, and prove required controllers still work.
- Test the old person’s phone, controller app, vendor app, lock code, alarm PIN, shared link, voice path, and account recovery. Each old route should fail.
Use the HomeKit member-removal checklist for Apple Home offboarding and the device-replacement checklist when hardware leaves the property.
Keep the alarm boundary clear
Matter state and controller automations can support a home routine, but they do not prove professional monitoring or emergency dispatch. If the property needs a security system, record direct alarm zones, local warning, communicator, internet and cellular paths, event types, monitoring center, contacts, verification, cancellation, emergency call, permit, dispatch, test mode, and restoration.
For an alarm platform with optional service, compare the current Abode Smart Security Kit and Abode plans. Verify the exact model, current integrations, Matter and Apple Home claims, plan features, alarm behavior, user permissions, and monitoring terms. Do not infer those functions from Matter support alone.
45-minute multi-admin acceptance test
- Reconcile every device to a model, fabric, controller, account, role, radio, network path, room, automation owner, recovery route, and physical fallback.
- Trigger each approved contact, motion, lock, light, plug, and other security-related device 10 times. Compare physical state, both controllers, vendor app, alerts, history, and automation.
- Add a temporary user with the minimum role. Prove the person can do the assigned job and cannot reach restricted devices, settings, billing, history, or recovery.
- Disable internet, one controller, and one border router separately. Run the documented power-loss test, then record missed events, delay, stale state, local operation, and restoration.
- Remove the temporary user from every platform and prove all old access and recovery routes fail.
- Save screenshots, timestamps, firmware, account owners, failures, fixes, rollback, and the next quarterly test date.
FAQ
Does Matter multi-admin create one shared administrator account?
No. It lets a Matter device join more than one controller fabric. Accounts, household roles, remote access, history, cameras, alarm users, and monitoring permissions can still remain separate.
Does removing a person from Apple Home remove access from every Matter controller?
Not necessarily. Remove the person, device, invitation, automation, shared link, recovery route, and controller access in every fabric, then test the old path.
Can Matter replace a monitored alarm system?
Matter can help controllers exchange supported device state and commands. It does not by itself prove a local siren, cellular path, monitoring center, emergency call, permit, or dispatch process.
What should be tested after adding a second Matter controller?
Test state, commands, names, rooms, automations, notifications, history, remote access, internet loss, controller loss, power loss, account recovery, user removal, and restoration in both systems.
