User, Group, and Permission Mapping

Once the authentication approach has been defined and domain integration (if applicable) is prepared, the next step is to establish how users will access and interact with visability.

This involves defining users, organizing them into groups, and aligning those groups with roles and permissions within the platform. Taking the time to plan this structure in advance ensures a smoother deployment and a more intuitive experience for operators.

At a minimum, all individuals who will interact with visability should be identified ahead of time. This includes operators, administrators, and any support personnel who may require access to the system.

In domain-integrated environments, this typically means confirming that the appropriate domain users or groups already exist. In standalone environments, users will be created directly within visability.

The goal is not to create every user individually, but to ensure that the right access structure is in place.

Rather than assigning permissions to individual users, it is best practice to organize access through groups.

Groups allow you to:

• Assign permissions once and apply them to multiple users
• Maintain consistency across roles
• Simplify onboarding and long-term user management

In domain environments, this often means leveraging existing Active Directory groups. In other cases, groups can be defined specifically for visability use.

Within visability, access is controlled through roles that define what users can see and do within the system.

Examples may include:

• Administrative access for system configuration
• Operator access for day-to-day control
• Restricted or view-only access for specific users

These roles should be mapped to the appropriate user groups before commissioning begins. This ensures that when users log in, they immediately have the correct level of access without requiring additional configuration.

It is important to clearly document how users, groups, and roles are structured.

This documentation should outline:

• Which groups have access to visability
• What roles are assigned to each group
• Any special permissions or restrictions

Having this defined ahead of time ensures alignment between the deployment team and the customer, and helps avoid confusion during and after commissioning.