Choosing a User Authentication Strategy

Before deploying vis|ability, it is important to determine how users will authenticate and access the system. This decision impacts system configuration, user management, and overall integration with your organization’s IT environment.

vis|ability supports multiple authentication approaches, allowing it to adapt to both standalone and domain-managed environments.

User authentication is a foundational component of the system. Establishing the correct approach early ensures that:

• Users can access the system reliably
• Permissions and roles are applied consistently
• Integration with existing IT policies is maintained
• Deployment and commissioning can proceed without delays

Changing authentication methods after deployment can introduce unnecessary complexity, so it is best to finalize this approach during the planning phase.

Native vis|ability Users

In this model, user accounts are created and managed directly within the vis|ability platform.

When This Approach is Used

• Smaller or standalone deployments
• Environments without domain integration

Key Characteristics

• User accounts are managed locally within vis|ability
• No dependency on external directory services
• Quick to configure and deploy

Domain-Based Authentication

In this model, visability integrates with your organization’s domain (e.g., Active Directory) to authenticate users.

When This Approach is Used

• Enterprise environments with centralized user management
• Deployments requiring alignment with IT security policies
• Organizations that want to leverage existing user accounts and groups

Key Characteristics

• Users authenticate using their domain credentials
• Access can be aligned with existing organizational structure
• Supports centralized identity and access management

The appropriate authentication method depends on your environment and operational requirements.

In general:

• Use native visability users when simplicity and speed are the priority
• Use domain-based authentication when integration with existing IT infrastructure is required

If your organization enforces centralized identity management, domain integration is typically the preferred approach.

Before moving forward, the following should be clearly defined:

• Which authentication method will be used
• Whether visability systems will be joined to the domain (if applicable)
• Which users or groups will require access to the system
• How roles and permissions will be assigned

Finalizing these decisions early helps avoid rework and ensures a smoother deployment process.