I have questions about best practices for structuring user management in Ignition as systems scale. At a high level, users fall into two groups: Gateway/Designer users, who configure and edit projects, and runtime users, who access the system via Perspective. These groups have different responsibilities and must be clearly separated.
In multi-factory or enterprise environments, the same project is often reused with different parameters, but users should remain isolated per factory. Relying only on User Sources and Roles becomes hard to scale, leading to role explosion, complex permissions, and difficulty adding context like factory or unit.
I’m looking for guidance on how to:
- Separate Designer/Gateway users from runtime users
- Scale user management across multiple factories
- Add contextual information to users
- Keep permissions clear without excessive roles
Any recommended patterns or best practices would be appreciated.