Matter Multi-Admin Feature Explained: The Complete Technical Guide

One of the most persistent frustrations in the smart home world has been ecosystem lock-in. You buy a smart lock that works beautifully with Apple HomeKit, only to discover your partner’s Android phone can’t control it without jumping through hoops. Or perhaps you’ve invested heavily in Google Home, but a family member prefers Samsung SmartThings. For years, these walled gardens forced consumers into difficult choices — until the Matter protocol arrived with a solution called Multi-Admin.

Multi-Admin is arguably one of the most important — yet least understood — features within the Matter specification. It fundamentally changes how smart home devices relate to the platforms that control them, moving from a model of exclusive ownership to one of shared, simultaneous administration. In this comprehensive technical explainer, we will break down exactly how Multi-Admin works, why it matters for your smart home, and how you can take full advantage of it.

Protocol Overview: What Is Matter Multi-Admin?

At its core, Matter Multi-Admin is a capability defined within the Matter protocol specification that allows a single smart home device to be commissioned (paired) to multiple fabric networks simultaneously. In practical terms, this means a Matter-compatible smart plug, light bulb, thermostat, or any other device can be controlled by Apple Home, Google Home, Samsung SmartThings, Amazon Alexa, and any other Matter-compatible platform — all at the same time, without removing the device from one ecosystem to add it to another.

Before Matter, smart home devices typically formed a one-to-one relationship with a single controller or hub. If you wanted to switch platforms or add a second platform, you often had to perform a factory reset and re-pair the device, losing automations and settings in the process. Some proprietary bridges offered limited multi-platform support, but these were unreliable, manufacturer-dependent workarounds rather than standardized solutions.

Multi-Admin solves this at the protocol level. It is not an optional add-on or a manufacturer-specific feature — it is a mandatory requirement of the Matter specification. Every certified Matter device must support being added to at least two fabrics (administrative domains), and most implementations support significantly more. This guarantee of interoperability is what makes Multi-Admin such a transformative feature for the smart home industry.

The Connectivity Standards Alliance (CSA), the organization behind Matter, designed Multi-Admin to address a very real household scenario: modern families use a mix of devices and platforms. One person might have an iPhone and use Apple Home, while another family member uses a Samsung Galaxy phone with SmartThings. A household might have a Google Nest Hub in the living room and an Amazon Echo in the kitchen. Multi-Admin ensures that every person in the home can control shared devices through their preferred platform, without conflict or compromise.

How Multi-Admin Works: Fabrics, Nodes, and Commissioning

To understand Multi-Admin at a technical level, you need to understand three key concepts within the Matter architecture: fabrics, nodes, and the commissioning process.

Understanding Fabrics

A fabric in Matter terminology is essentially an administrative domain — a trust boundary that represents a single smart home ecosystem or controller. When you add a Matter device to Apple Home, you are adding it to the Apple Home fabric. When you add the same device to Google Home, you are adding it to the Google Home fabric. Each fabric maintains its own set of cryptographic credentials, access control rules, and operational state.

A Matter device can belong to multiple fabrics simultaneously. Internally, the device maintains a Fabric Table, which is a data structure that stores the credentials and metadata for each fabric it has been commissioned to. The Matter specification requires devices to support a minimum number of fabric entries (typically at least two to five, depending on the device class), though many devices support more.

Each fabric is identified by a unique Fabric Index, and all communication between a device and a controller is scoped to a specific fabric. This means that when Google Home sends a command to your smart light, that command is processed within the context of the Google Home fabric, with its own encryption keys and access control policies. Apple Home’s commands to the same device operate within the Apple Home fabric, completely independently.

Nodes and Device Identity

A node in Matter is any individual device or endpoint on the network — a light bulb, a sensor, a bridge, or a controller. Each node has a unique Node ID within each fabric it belongs to. Importantly, a device can have different Node IDs across different fabrics. This means the same physical smart plug might be Node 0x0003 in the Apple Home fabric and Node 0x0017 in the Google Home fabric.

This separation of identity across fabrics is a deliberate design choice that enhances both security and privacy. Each fabric’s controller sees the device through its own lens, without needing to know how other fabrics have configured or identified the same device.

The Commissioning Process

Commissioning is the process by which a device is added to a fabric. With Multi-Admin, there are two primary commissioning scenarios:

Initial Commissioning: This is the first time a device is paired with a controller. The device starts in a “commissioning mode” (often triggered by pressing a button or scanning a QR code), and the first controller establishes a secure channel, exchanges cryptographic credentials, and adds itself as the first fabric in the device’s Fabric Table.
Additional Commissioning (Multi-Admin): After the initial commissioning, the device can be opened for additional commissioning by any existing administrator. This is done through a process called “Open Commissioning Window,” where the device temporarily accepts new commissioning requests. A second (or third, or fourth) controller can then establish its own secure relationship with the device and add its own fabric entry.

The critical innovation here is that the device does not need to leave the first fabric to join the second. The Open Commissioning Window can be triggered either physically (through a button press on the device) or digitally (through a command from an existing administrator). This digital triggering is particularly important because it enables seamless sharing of devices between platforms without requiring physical access to every device in your home.

Under the hood, each commissioning session involves a robust cryptographic handshake based on the Certificate-Based Authentication defined in the Matter specification. Each fabric receives its own set of operational certificates, and all subsequent communication is encrypted using keys derived specifically for that fabric. This ensures that even though a device belongs to multiple fabrics, the data and commands within each fabric remain cryptographically isolated.

Operational State Synchronization

One of the most common questions about Multi-Admin is how device state is synchronized across fabrics. If you turn on a light using Apple Home, does Google Home know the light is on?

The answer lies in Matter’s subscription and reporting mechanism. Matter devices can maintain active subscriptions with controllers on multiple fabrics simultaneously. When the state of a device changes (for example, a light is turned on), the device sends state change reports to all fabrics that have active subscriptions. This means that if you turn on a light via Apple Home, the Google Home app will reflect the updated state within moments, and vice versa.

It is important to note that the synchronization is not instant — there can be slight delays depending on network conditions, subscription intervals, and how each platform’s app handles state updates. However, in typical home network conditions, the lag is usually measured in milliseconds to a few seconds, which is imperceptible in normal use.

Compatibility: Which Platforms and Devices Support Multi-Admin?

Because Multi-Admin is a mandatory part of the Matter specification, every certified Matter device and every Matter-compatible platform must support it to some degree. However, the quality of implementation and the user experience can vary between platforms. Here is a breakdown of the major ecosystems and their Multi-Admin support.

Apple Home

Apple has been one of the strongest proponents of Matter and Multi-Admin from the beginning. Within the Apple Home app, you can add any Matter device and then easily enable sharing with other platforms. Apple’s implementation allows you to initiate the Open Commissioning Window directly from the Home app, making it straightforward to add a device to a second ecosystem. Apple Home supports Multi-Admin across all its hubs, including Apple TV (4K and later models) and HomePod devices.

Google Home

Google Home fully supports Matter Multi-Admin, allowing devices to be commissioned to the Google Home fabric alongside other platforms. Google’s implementation includes support for sharing devices to other ecosystems through the Google Home app. Google Nest hubs and speakers serve as Thread border routers and Matter controllers, facilitating reliable Multi-Admin operation across the network.

Amazon Alexa

Amazon has progressively rolled out Matter support across its Alexa ecosystem. Multi-Admin functionality is supported on compatible Echo devices that serve as Matter controllers. Amazon’s approach allows devices already in Alexa to be shared with other platforms, and devices from other platforms to be added to Alexa as a secondary fabric.

Samsung SmartThings

Samsung SmartThings has been a leader in Matter adoption, with SmartThings Station and compatible Samsung Galaxy devices serving as Matter controllers and Thread border routers. SmartThings fully supports Multi-Admin, and Samsung has made the process of sharing devices to other platforms relatively seamless through its app interface.

Other Platforms

Beyond the major four, several other platforms support Matter Multi-Admin, including Home Assistant (through its Matter integration), Eve Systems’s app, and various manufacturer-specific apps. The open nature of the Matter protocol means that any platform can implement a Matter controller with Multi-Admin support, and the ecosystem continues to grow.

Device Compatibility Considerations

While Multi-Admin is mandatory in the Matter specification, the number of simultaneous fabrics a device can support varies by implementation. Most smart plugs, light bulbs, and switches support between two and five fabrics, which is sufficient for the vast majority of households. More complex devices like bridges and hubs may support additional fabrics.

It is also worth noting that some devices originally built for a single ecosystem (such as older HomeKit-only devices) may receive firmware updates that add Matter support, including Multi-Admin. However, not all legacy devices will receive such updates, and the quality of the transition can vary. For the best Multi-Admin experience, purchasing devices that are Matter-certified from the outset is recommended. Browse our recommended Matter-compatible devices for options that fully support Multi-Admin.

Performance and Reliability: What to Expect in Real-World Use

Adding a device to multiple fabrics does introduce some overhead, both on the device itself and on the network. Understanding these performance implications will help you set realistic expectations and optimize your setup.

Network Traffic

Each fabric that subscribes to a device’s state updates generates its own stream of network traffic. A device that is part of three fabrics and has active subscriptions on all three will send state change reports to three different destinations. On a typical home Wi-Fi or Thread network, this additional traffic is negligible — Matter messages are extremely compact, often just a few dozen bytes per update.

However, in networks with a very large number of Matter devices (50 or more), each belonging to multiple fabrics, the cumulative traffic can become noticeable. In such cases, using Thread (which is specifically designed for low-power, low-bandwidth IoT communication) rather than Wi-Fi for end devices can help maintain network performance. Learn more about this in our Thread vs. Wi-Fi comparison guide.

Device Resource Usage

Maintaining multiple fabric entries in the Fabric Table requires memory and processing resources on the device. Each fabric entry includes cryptographic keys, certificates, and access control lists. For resource-constrained devices (such as battery-powered sensors), this can be a consideration.

Device manufacturers must balance the number of supported fabrics against available memory and processing power. This is why some simpler devices may support only two or three fabrics, while more capable devices (like plugged-in hubs and bridges) can support many more. In practice, the number of fabrics supported by even the simplest Matter devices is sufficient for most households.

Latency and Responsiveness

One concern that users sometimes raise is whether Multi-Admin introduces latency in command execution. The answer is generally no — command processing on the device is fabric-independent. When a command arrives from any fabric, the device processes it using the same internal logic, regardless of which fabric sent it.

The only scenario where latency might be perceived is during the initial commissioning of an additional fabric. The Open Commissioning Window process involves cryptographic key exchange and certificate validation, which can take several seconds. However, this is a one-time process for each additional fabric and does not affect ongoing operation.

Conflict Resolution

What happens if two fabrics send conflicting commands simultaneously? For example, if Apple Home sends a “turn off” command and Google Home sends a “turn on” command at nearly the same instant?

Matter handles this through simple sequential processing. The device processes commands in the order they are received. The last command to arrive will determine the final state of the device. Both fabrics will then receive a state update reflecting the final state. In practice, simultaneous conflicting commands are extremely rare in residential settings, and when they do occur, the resolution is deterministic and predictable.

Security Architecture: How Multi-Admin Protects Your Smart Home

Security is a foundational pillar of the Matter protocol, and Multi-Admin was designed with security as a primary concern rather than an afterthought. The security architecture ensures that sharing a device across multiple platforms does not create vulnerabilities or expose sensitive data.

Cryptographic Isolation Between Fabrics

Each fabric maintains its own completely independent set of cryptographic credentials. This includes:

Root of Trust: Each fabric has its own root certificate authority (CA), which is typically managed by the platform provider (Apple, Google, Samsung, etc.).
Operational Certificates: Each device receives a unique operational certificate for each fabric it belongs to, signed by that fabric’s CA.
Encryption Keys: All communication between a device and a controller is encrypted using keys that are specific to that fabric. Apple Home cannot decrypt Google Home’s traffic to the same device, and vice versa.
Access Control Lists (ACLs): Each fabric maintains its own ACL, which defines which nodes and users within that fabric can perform which operations on the device.

This cryptographic isolation means that even though a device belongs to multiple fabrics, there is no data leakage between them. A vulnerability or compromise in one fabric does not affect the security of other fabrics on the same device.

The Role of the Administrator

In the Multi-Admin model, the controller that initially commissions a device becomes its Administrator. The Administrator has special privileges, including the ability to:

Open the Commissioning Window to allow additional fabrics to be added
Remove other fabrics from the device (effectively revoking their access)
Update the device’s access control lists
Initiate firmware updates (in most implementations)

This hierarchical model ensures that there is always a clear chain of authority over the device. If you add a device to Apple Home first, Apple Home becomes the Administrator, and you control when and how other platforms are granted access. This prevents unauthorized platforms from adding themselves to your devices without your knowledge.

It is worth noting that some implementations allow for “co-administrator” models, where multiple fabrics share administrative privileges. However, the default model in most consumer implementations is a single primary administrator with the ability to grant and revoke access to secondary fabrics.

Revoking Access

One of the most important security features of Multi-Admin is the ability to revoke access. If you no longer want a particular platform to control a device, the Administrator can remove that platform’s fabric from the device’s Fabric Table. This immediately invalidates all of that fabric’s cryptographic credentials, and the platform loses all access to the device.

This is particularly useful in scenarios such as:

Removing a former housemate’s platform access when they move out
Decommissioning an old hub or controller
Switching a device entirely from one ecosystem to another
Responding to a suspected security compromise on one platform

The ability to surgically remove individual fabrics without affecting others is a significant advantage over the old model of factory-resetting devices and starting over.

Privacy Implications

Multi-Admin also has positive privacy implications. Because each fabric’s data is cryptographically isolated, platforms cannot see how you are using the device through other platforms. Google cannot see the automations you have set up in Apple Home, and Apple cannot see the routines you have created in SmartThings. Each platform only has visibility into its own fabric’s interactions with the device.

Additionally, Matter’s local-first architecture means that most device communication happens over your local network, without routing through cloud servers. This reduces the amount of data that is transmitted to platform providers and keeps your smart home activity more private. For more on how Matter handles data, see our guide on Matter privacy and security.

Best Devices for Leveraging Multi-Admin

While Multi-Admin works with all Matter-certified devices, some device categories benefit more from multi-platform support than others. Here are the categories where Multi-Admin provides the most significant value.

Smart Locks

Smart locks are perhaps the most compelling use case for Multi-Admin. In a household where different family members use different phone platforms, a smart lock that only works with one ecosystem creates real friction. With Multi-Admin, everyone in the household can lock and unlock the door, receive notifications, and manage access codes through their preferred platform. The security implications of locks make the cryptographic isolation between fabrics particularly important — you want to ensure that a compromise in one platform does not affect the lock’s security on another.

Smart Thermostats

Thermostats are shared devices that everyone in a household interacts with. Multi-Admin ensures that all family members can adjust the temperature, view schedules, and receive comfort alerts regardless of their preferred smart home platform. This is especially valuable in households where some members use Apple devices and others use Android, as thermostat control is something that should be universally accessible.

Lighting

Smart lighting is one of the most popular smart home categories, and Multi-Admin makes it significantly more practical. When every light in your home can be controlled from any platform, you eliminate the frustration of “I can’t turn off the lights because the app is on someone else’s phone.” Multi-Admin also enables scenarios where different family members can create their own automations and scenes within their preferred platform, all controlling the same physical lights.

Sensors and Safety Devices

Motion sensors, contact sensors, smoke detectors, and water leak sensors are critical safety and security devices that everyone in a household should have access to. Multi-Admin ensures that alerts from these devices reach all family members, regardless of which platform they use. A water leak detected at 2 AM should notify everyone, not just the person whose phone is paired with the sensor.

Bridges and Hubs

Matter bridges — devices that translate between Matter and other protocols like Zigbee or Z-Wave — are particularly powerful with Multi-Admin. A single bridge can expose dozens of connected devices to multiple fabrics simultaneously, effectively multiplying the value of your existing device investments. If you have a collection of Zigbee sensors connected to a Matter bridge, Multi-Admin ensures that all of those sensors are accessible from every platform in your household. Explore our recommended Matter bridges for top options.

Frequently Asked Questions

Can I add a Matter device to unlimited platforms with Multi-Admin?

Not exactly unlimited, but practically sufficient. The Matter specification requires devices to support a minimum number of fabrics (typically two to five), but the exact number depends on the device manufacturer and the device’s available memory. Most consumer devices support between three and five simultaneous fabrics, which is more than enough for typical household scenarios. If you attempt to add more fabrics than the device supports, you will need to remove an existing fabric first. Higher-end devices and bridges may support significantly more fabrics.

Does Multi-Admin work with non-Matter devices?

Multi-Admin is a feature specific to the Matter protocol, so it only applies to Matter-certified devices. However, Matter bridges can expose non-Matter devices (such as Zigbee, Z-Wave, or proprietary protocol devices) to multiple Matter fabrics simultaneously. In this scenario, the bridge itself uses Multi-Admin to connect to multiple platforms, and the devices behind the bridge become accessible across all those platforms. This is one of the most powerful ways to bring legacy smart home devices into a multi-platform environment.

Will using Multi-Admin drain the battery of my wireless sensors faster?

The impact on battery life is minimal but not zero. Each additional fabric that maintains an active subscription to a battery-powered device will cause the device to send additional state update messages. However, Matter is designed with extreme power efficiency in mind, and these messages are very small. The Thread protocol, which many battery-powered Matter devices use, is specifically optimized for low-power operation. In practice, the difference in battery life between a device on one fabric versus three fabrics is typically measured in weeks or months over a multi-year battery lifespan, not in hours or days.

What happens to my automations if I remove a fabric from a device?

When you remove a fabric from a device using Multi-Admin, only the automations and configurations associated with that specific fabric are affected. The device itself continues to operate normally, and automations on other fabrics remain intact. For example, if you remove the Google Home fabric from a smart light, any Google Home routines involving that light will stop working, but your Apple Home automations for the same light will continue unaffected. This surgical removal capability is one of the key advantages of Multi-Admin over factory-resetting devices.

Is Multi-Admin supported over both Wi-Fi and Thread?

Yes, Multi-Admin is a feature of the Matter application layer, which is independent of the underlying network transport. Whether a device communicates over Wi-Fi, Thread, or Ethernet, Multi-Admin works the same way. The choice between Thread and Wi-Fi affects network performance, power consumption, and range, but it does not affect Multi-Admin functionality. This transport-layer independence is one of the elegant aspects of Matter’s architecture — features like Multi-Admin work consistently regardless of how the device connects to your network.

Conclusion

Matter Multi-Admin represents a fundamental shift in how smart home devices relate to the platforms that control them. By allowing a single device to belong to multiple administrative domains simultaneously, Multi-Admin eliminates the ecosystem lock-in that has plagued the smart home industry for years. It enables mixed-platform households to function harmoniously, gives consumers the freedom to choose and change platforms without replacing hardware, and does so while maintaining robust security through cryptographic isolation between fabrics.

As the Matter ecosystem continues to mature and more devices receive certification, Multi-Admin will become an increasingly important feature that consumers expect as standard. Understanding how it works, how to use it, and how to troubleshoot common issues will help you build a smart home that is flexible, secure, and truly interoperable. Whether you are setting up your first Matter device or managing a whole-home installation with dozens of devices across multiple platforms, Multi-Admin is the feature that makes it all work together seamlessly.

Ready to build a multi-platform smart home? Start by exploring our complete Matter protocol guide and browse our curated selection of Matter-compatible devices to find the best options for your setup.