Hi @ta-aoki,
Thanks for the question. I just create a post with more details on this topic.
This section from the post explains why we’re making this change:
Why are we making this change?
In Tulip, permissions for which Display Devices can run which Tulip Apps are managed by Station assignment. However, the current behavior allows unassigned Display Devices (unassigned with respect to a Station) to run any Tulip App that exists in an Instance/Workspace. This breaks the intended permission model that is supposed to be managed by the Station. Tulip has decided to change this behavior. Going forward, Tulip will be preventing all apps from running on unassigned Display Devices.
There’s nothing wrong with having unassigned display devices. You and your team will likely work with assign/unassigned display devices when setting up or breaking down workstations. Going forward, any display devices left in an unassigned state won’t be able to run Tulip Apps without first being assigned to a Station.
Let me know if you have any other questions.