Hi,
We have a scenario. We have Client A.
Client A can log in to three different PCs (location Cutting, Packing, and Dispatch) in the same network attached to the same ignition gateway.
It required that when Client A logged in to the cutting section, he could see the selected pages (views).
But when logging in to the packing section with the same credentials, then different pages.
You will need to distinguish clients by IP address, either with Security Zones or custom scripts/expressions. If there's a NAT between your clients and the gateway, it is effectively impossible. (But Vision can do it with MAC addresses or other local identifiers.)
As Phil noted this is likely an appropriate scenario for Security Zones.
Create a Security Zone for each workstation based on the Host Name. After that, each PC now has this unique identifier as part of its Session Auth information. (There is a chance the session props already have unique identifiable information for the host)
Finally a Startup script that evaluates the Security Zone, and navigates to the appropriate URL for that workstation.