Guides Matter Multi-Admin Explained: Sharing Devices Across Apple Home, Google, Alexa
Matter multi-admin, explained
Multi-admin is the feature that makes "works with everything" real: one Matter accessory can be controlled by Apple Home, Google Home and Alexa at the same time, from one radio and one pairing. It is also the feature people misunderstand most, because sharing a device is not the same as sharing a home.
What multi-admin means
Every Matter ecosystem you add a device to creates its own fabric — a separate security domain with its own credentials and its own administrator. Multi-admin simply means the accessory belongs to more than one fabric at once, and each fabric's controller can talk to it independently. The Connectivity Standards Alliance describes it exactly that way: join the device to several Matter fabrics and administer it with several different Matter controllers.
There is no "master" ecosystem. Apple Home does not grant Google Home permission, and vice versa — each admin commissioned the device itself and holds its own credentials. The device keeps a list of fabrics and serves them all.
What you need
- A Matter-certified accessory. Check the protocol in our compatibility matrix; HomeKit-only gear cannot do this at all.
- A controller in each ecosystem. For Apple Home that means a home hub — Apple requires one before any Matter accessory can be added. A HomePod mini, HomePod, HomeView or Apple TV covers it.
- A Thread border router per ecosystem, for Thread devices. A Thread accessory needs a border router on each fabric it joins. Apple's own hubs do that job; Google and Amazon need their own Thread-capable hardware. Background: what a Thread border router is.
Sharing a device, step by step
- Commission normally in the first ecosystem. Add the accessory in Apple Home as usual (see how to add a device to Apple Home).
- Open the accessory's settings in that app and find the multi-admin entry. In Apple Home it is Turn On Pairing Mode at the bottom of the accessory's detail view.
- Copy the setup code that appears. This is a fresh code for this commissioning window — the code printed on the device label will not work a second time.
- Add the device in the second ecosystem using that code, not the QR code. In Google Home: Devices → Add → Set up without QR code. Other apps use similar wording.
- Assign a room and name in the second app. Treat it as a brand-new device, because for that ecosystem it is one.
The pairing window is temporary. If the code expires before the second app accepts it, open the window again and use the new code.
What is shared and what is not
| Item | Shared across ecosystems? |
|---|---|
| Device state — on/off, brightness, lock state, temperature | Yes, because it is the same physical device |
| Device name and room | No — each ecosystem keeps its own |
| Scenes and automations | No — they live in the app that created them |
| Firmware and vendor settings | Usually per vendor app or per ecosystem; expect to update in one place |
| People and permissions | No — Apple Home sharing and Google Home sharing are separate systems |
That table explains the most common confusion: sharing a device with a second ecosystem does not give the people in that ecosystem access to your Apple Home, your rooms, or your automations. They see one device, freshly named.
Practical limits
- Scenes and automations are never shared. Two ecosystems means two sets of rules that can fight each other — a Google routine turning a lamp on at sunset while an Apple Home automation turns it off. Pick one ecosystem as the automation brain and use the other for voice or dashboards.
- Cameras are the weak spot. Cameras only became a Matter device type with Matter 1.5, released in November 2025, and the standard uses WebRTC for the stream. Camera hardware and ecosystem support are still arriving, so in practice most cameras today are not multi-admin devices. HomeKit Secure Video cameras certainly are not — HSV is Apple-only by design (see HSV storage and camera limits).
- Removing a device removes one fabric, not all. Deleting an accessory in Apple Home strips Apple's fabric; the device stays commissioned in Google Home. To truly start over you need a factory reset, which clears every fabric.
- Not every vendor exposes the pairing mode. Some apps hide multi-admin behind an account or firmware version. If you cannot find it, the vendor app or the manual is the place to look — this is a UI gap, not a Matter limitation.
- Some device types share better than others. Plugs, bulbs, sensors, switches and locks are the reliable cases. Anything with a vendor cloud — doorbells, robot vacuums, pet feeders — often exposes only part of its feature set through Matter, so the second ecosystem may see a switch where the first sees a whole product.
When multi-admin is worth the effort
- Mixed households. One person on iPhone, one on Android: the same lock or lamp appears in both Apple Home and Google Home, and neither person needs the other's phone.
- Voice where you need it. Alexa in the kitchen, Apple Home on the watch, one set of devices behind both.
- Migration without downtime. Add the new ecosystem first, confirm everything works, then remove the old fabric at your leisure.
It is not worth it if both ecosystems only ever control the same three bulbs — you get double the naming work and two places for automations to break. The trade-offs of running two ecosystems are covered in Apple Home, Alexa and Google together.
Where multi-admin fits in the bigger picture
Multi-admin is a property of the Matter layer, which is why it does not exist for HomeKit-only accessories. If the vocabulary is still fuzzy — Matter versus Thread versus HomeKit — read Matter vs Thread vs HomeKit first, then check each device's protocol in the matrix. Battery-powered devices you plan to share are usually Matter over Thread, which is also why the border-router question comes up twice.
For a worked example of the same devices living in two ecosystems, the pet-tech list at LimeCats shows how feeders and cameras split between Apple Home and vendor apps — a useful reality check on how much of a product actually travels through Matter.
FAQ
Can one Matter device really be in Apple Home and Google Home at once?
Yes. That is what multi-admin is for: the accessory joins a separate fabric for each ecosystem, and each ecosystem's controller administers its own fabric. State changes are shared because it is one physical device, but names, rooms and automations are not.
Do I need a hub in every ecosystem?
Effectively yes. Apple Home requires a home hub before a Matter accessory can be added, and a Thread accessory needs a Thread border router on each fabric it joins, so Google or Amazon need their own Thread-capable hardware.
Can I reuse the setup code printed on the device?
No. The label code works once, for the initial commissioning. For a second ecosystem you open a pairing mode in the first app, which generates a new 11-digit code for that commissioning window.
Are scenes and automations shared between ecosystems?
No. Scenes, automations and routines stay inside the app that created them. Running two ecosystems means maintaining two sets of rules, which is why most people keep one as the automation brain.
Does removing a device from Apple Home remove it from Google Home too?
No. Removing the accessory in Apple Home deletes Apple's fabric only; the device remains commissioned in the other ecosystem. A factory reset is the only way to clear every fabric at once.
Can I share a camera across ecosystems with multi-admin?
Not in practice today. Cameras only became a Matter device type with Matter 1.5 in November 2025, and hardware plus ecosystem support are still rolling out. HomeKit Secure Video cameras are Apple-only and cannot be shared this way.