# Client Authentication (Perspective)

**URL:** <https://forum.inductiveautomation.com/t/client-authentication-perspective/105510>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 24, 2025, 12:31pm UTC](https://forum.inductiveautomation.com/t/client-authentication-perspective/105510 "2025-04-24T12:31:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\
**Post date:** [April 24, 2025, 12:31pm UTC](https://forum.inductiveautomation.com/t/client-authentication-perspective/105510/1 "2025-04-24T12:31:53Z")

</div>

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.

Thanks.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 24, 2025, 12:39pm UTC](https://forum.inductiveautomation.com/t/client-authentication-perspective/105510/2 "2025-04-24T12:39:21Z")

</div>

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.)

---

<div class="post-metadata">

**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\
**Post date:** [April 24, 2025, 12:40pm UTC](https://forum.inductiveautomation.com/t/client-authentication-perspective/105510/3 "2025-04-24T12:40:21Z")

</div>

As Phil noted this is likely an appropriate scenario for Security Zones.

> **[Security Zones | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/security/security-zones)**
>
> A Security Zone is a list of Gateways, Computers, or IP addresses that are defined and grouped together. This group now becomes a zone on the Gateway Network, which can have additional policies and restrictions placed on it. While Users and Roles...

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](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/perspective-sessions/session-properties) Auth information. (There is a chance the session props already have unique identifiable information for the host)

Finally a [Startup](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/scripting-in-perspective/perspective-session-events-scripts#startup-and-shutdown-event-scripts) script that evaluates the Security Zone, and navigates to the appropriate URL for that workstation.