Admins Configuration Guide

The Administrative Users management interface provides a centralized control plane for regulating access across the platform's graphical user interface (UI). Proper administration of these accounts is essential for maintaining a secure environment and establishing a clear operational hierarchy for system management.

Administrative Roles

To enforce security boundaries, administrative access is segmented by roles. Administrative accounts are intended exclusively for managing the platform through the user interface and do not provide access to application programming interfaces (APIs).

Additionally, standard administrative roles do not include permissions for certain system-critical areas. White Label settings, Licensing, and Audit Log configuration require separate authorization and are not available through standard administrative profiles.

The platform provides two primary global administrative roles:

Superuser

The Superuser role provides high-level authority across the platform, including read and write access to general architecture settings and operational workflows. However, access to White Label, Licensing, and Audit Log modules remains restricted.

Admin

The Admin role is designed for routine operational activities, including daily maintenance, workflow monitoring, and reporting tasks, without exposing platform-level security and configuration settings.

User Provisioning

The platform supports a granular permission structure that can scale according to the complexity of your deployment.

During the initial installation, the system includes a default administrative account:

• Username: admin
• Password: admin

For security reasons, these default credentials should be changed immediately after deployment to prevent unauthorized access.

Module-Specific Permissions

When creating a new administrative user, select Add New Row to initiate the provisioning process.

The platform provides the two global roles, Superuser and Admin, while also generating additional permissions for each active module within the system.

This approach allows administrators to assign access rights with a high degree of precision, ensuring that users can only manage the modules and functions required for their responsibilities.

By combining global roles with module-specific permissions, organizations can maintain strong security controls while providing administrators with the access required to perform their duties effectively.