# Idea: Share Linked MVR Inputs Across Systems

**URL:** <https://community.pixelhue.com/t/idea-share-linked-mvr-inputs-across-systems/17>\
**Category:** Feedback & Suggestions\
**Tags:** link\
**Created:** [August 24, 2026, 7:34am UTC](https://community.pixelhue.com/t/idea-share-linked-mvr-inputs-across-systems/17 "2026-08-24T07:34:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hart](https://yyz1.discourse-cdn.com/flex033/user_avatar/community.pixelhue.com/hart/32/10_2.png) [@Hart](https://community.pixelhue.com/u/Hart)\
**Post date:** [August 24, 2026, 7:34am UTC](https://community.pixelhue.com/t/idea-share-linked-mvr-inputs-across-systems/17/1 "2026-08-24T07:34:59Z")

</div>

In a linked multi-system workflow, an operator may want an MVR input made available on one processing unit to be visible or selectable across the linked environment.

## Current workflow pattern

The operator manages inputs and monitoring across more than one linked processor. An MVR source can be useful locally, but the operator would benefit from a clearer, shared view of that source across the control workflow.

## Improvement to explore

- Make the availability and state of eligible MVR inputs understandable across linked systems.
- Keep model, resource, and routing limitations visible.
- Prevent ambiguous control when more than one operator is connected.
- Provide clear feedback when a source cannot be shared.

## Why this matters

A predictable monitoring workflow can reduce repeated setup and help operators understand the whole linked system from each approved control position.

This topic describes a community workflow idea. It is **not** a product commitment or roadmap statement. Please add your device models, system topology, operator roles, and desired behavior without sharing private project details.