Matter Fabrics & Multi-Admin: Control One Device From Two Apps
A Matter fabric is a secure, private network of Matter devices and controllers that share a common set of security credentials and can talk to one another. Multi-admin (short for multiple administrators) is the Matter feature that lets a single device belong to more than one fabric at the same time — so the same smart plug or bulb can be controlled from Alexa, Google Home, and Apple Home simultaneously, without picking a favorite. In plain terms: a fabric is the "club" a device joins, and multi-admin is what lets a device hold several club memberships at once.
What exactly is a Matter fabric?
When you commission a Matter device into an ecosystem, that ecosystem issues the device a cryptographic identity — a certificate rooted in that fabric's trust chain. All devices and controllers that share that root belong to the same fabric. Within a fabric, devices can be grouped, automated, and controlled locally, and every command is authenticated against those shared credentials.
A useful way to think about it: your Wi-Fi network moves the packets, but the fabric decides who is allowed to talk to whom and proves it with certificates. Two Matter devices on the same Wi-Fi or Thread network are not automatically able to control each other — they have to be on the same fabric first. This is also why Matter can keep working on your local network even when the internet is down, a point we cover in Do Matter Devices Need the Internet to Work?
Each major platform maintains its own fabric. Add a bulb to Apple Home and it joins Apple's fabric. Add it to Google Home and it joins Google's. These fabrics are separate trust domains that happen to control the same hardware.
What multi-admin does (and why it exists)
Matter devices are built to store credentials for several fabrics at once — the specification requires a device to support multiple fabrics, and most consumer devices advertise support for around five. Multi-admin is the process of adding your device to an additional fabric after the first one, so more than one platform can administer it.
The reason this matters is practical. Before Matter, a device tied to one ecosystem's cloud usually lived in one app. If you wanted it in a second app, you often relied on a cloud-to-cloud "skill" or integration that could lag, break, or expose only a subset of controls. Multi-admin replaces that with direct, local control from each platform — no bridge account, no cloud relay between ecosystems.
This is the mechanism behind sharing a single device across ecosystems. We walk through the exact app-by-app taps in Share a Matter Device Across Alexa, Google & Apple Home.
How a device joins a second fabric
The handoff uses a fresh setup code rather than the original code printed on the device. The ecosystem that already controls the device generates a new, time-limited pairing code, and you enter that into the second ecosystem's app.
- 1In the first app (the one that already has the device), find the option to share, add to another network, or “pair with a Matter controller” and generate a code
- 2Open the second app and choose to add a Matter device
- 3Enter or scan the generated code instead of the sticker code; the device is commissioned into the second fabric while staying in the first
The wording differs by platform — in the Alexa app, the Google Home app, the Apple Home app, or SmartThings you're looking for language like "share," "add to another network/app," or "link a Matter accessory." Because menus move, look for the concept (sharing to another Matter controller) rather than a specific screen name.
Fabrics vs. multi-admin at a glance
| Concept | What it is | What it controls |
|---|---|---|
| Matter fabric | A secure trust domain with shared credentials, one per ecosystem | Which controllers can command a device, and how devices are grouped locally |
| Multi-admin | A device holding membership in more than one fabric at once | How many apps/ecosystems can independently control the same device |
| Commissioning | The onboarding that issues a device its credentials for a fabric | Getting a device onto its first (or an additional) fabric |
What each fabric can and can't see
Each fabric controls the device directly, but fabrics are otherwise independent. Some things worth knowing:
- Automations don't sync. A routine you build in Google Home stays in Google Home. Apple Home has no idea it exists. You recreate automations in each app where you want them.
- Names and rooms don't sync. Call it "Porch Light" in one app and it can be "Front Bulb" in another; each fabric keeps its own labels.
- State does sync. Turn the device off from Alexa and Apple Home reflects the new state, because both are talking to the same device — not to each other.
- Bridges pass through too. If your device actually sits behind a Matter bridge (for example, a hub exposing Zigbee devices as Matter), multi-admin shares the bridged devices, subject to how many fabrics the bridge supports.
Fabrics, Thread, and where the two overlap
Fabrics are a Matter concept and are separate from the Thread network layer, though people often conflate them. Thread carries the traffic for Matter-over-Thread devices; the fabric is the security and control layer that rides on top. A device can be on one shared Thread network yet belong to several Matter fabrics, and multiple ecosystems' border routers can cooperate on that Thread network. If you're weighing radios and standards more broadly, Matter vs Zigbee vs Z-Wave puts fabrics in context.
Frequently asked questions
How many fabrics can one Matter device join?
The Matter spec requires support for multiple fabrics, and many consumer devices advertise room for about five. The exact number is set by the device maker, so a cheap plug and a premium lock can differ. Check the manufacturer's Matter documentation if you plan to load a device into many ecosystems at once.
If I remove a device from one app, does it leave the others?
No — removing it through an app's unpair option deletes only that fabric's membership. The device keeps working in every other ecosystem. It's a full hardware factory reset that clears everything.
Do all my apps need to be online for multi-admin to work?
Each fabric controls the device on your local network, so day-to-day control doesn't route through some shared cloud between ecosystems. Adding a device to a new fabric (the pairing step) may require the internet, but ongoing local control generally does not.
Does multi-admin slow the device down or cause conflicts?
Multiple fabrics don't meaningfully compete — the device simply accepts authenticated commands from any admin. The usual pain points are network health, not the fabric count. If a shared device feels sluggish, look at Thread or Wi-Fi signal, as we describe in How to Check Your Thread Network Health.
