Users Module
Overview
The Users module is responsible for managing all users who can access the system.
Access to the platform is restricted to authorized users only. Public registration is not supported. Every user must be created or provisioned through one of the supported user provisioning methods.
The Users module enables administrators to:
- Create and manage user accounts.
- Assign administrative privileges.
- Configure user permissions.
- Provision users from external identity providers such as LDAP and Single Sign-On (SSO).
Access Requirements
To access this page, the user must have at least the GET permission for the Users module.
If you do not have the required permission, ask your administrator to grant it from one of the authorization pages below.
Authorization
Users without the required permission cannot view this page and will receive the following authorization error:
Access Denied
You don't have access to this resource.
Default Administrator
During the initial installation of the system, a default administrator account is automatically created.
| Property | Value |
|---|---|
| Username | dfladmin |
| Created Automatically | Yes |
| Can be Deleted | No |
| Can be Renamed | No |
The dfladmin account is used to perform the
initial system configuration, including creating new users and assigning
permissions.
User Roles
Every newly created user is initially created as a standard user.
Users can later be granted Administrator privileges by an existing administrator.
A newly created user does not automatically gain access to system resources. Access is determined by the permissions assigned after the account has been created.
For detailed information about the permission model, see the Permissions documentation.
User Lifecycle
A typical user lifecycle consists of the following stages:
- User account creation.
- Initial password setup (manual users only).
- Permission assignment.
- System access.
- User updates.
- User deactivation or deletion.
User deletion is performed using a soft delete mechanism, allowing historical records to remain intact.
User Creation Methods
Manual User Creation
Administrators can manually create new users.
After the account is created:
- The user receives the default namespace assignment.
- No resource permissions are granted automatically.
- The user defines their own password during their first login.
LDAP User Creation
Users can be imported from an LDAP directory.
This option is available through:
Add User → Add LDAP User
LDAP provisioning requires an LDAP configuration to be completed beforehand.
Single Sign-On (SSO)
Users can also be provisioned automatically through Single Sign-On (SSO).
When a user successfully authenticates through an external identity provider for the first time, the corresponding user account is automatically created within the system.
Default Permissions
Every newly created user receives the system's default namespace assignment.
No additional permissions are granted automatically. Before a user can access resources, the appropriate permissions must be assigned by an administrator.
For details about the permission model and authorization process, refer to the Permissions documentation.
Authentication
The system supports multiple authentication methods:
- Local authentication
- LDAP authentication
- Single Sign-On (SSO)
The authentication method depends on the system configuration.
User Management
Administrators can perform the following user management operations:
- Create users
- Update user information
- Assign administrator privileges
- Configure permissions
- Activate or deactivate users
- Delete users (soft delete)
Password Management
For manually created users, the password is defined by the user during their first successful login.
The system currently does not enforce a password policy. Users may choose their own passwords.
Limitations
-
The default administrator (
dfladmin) cannot be deleted. -
The default administrator (
dfladmin) cannot be renamed. - Public user registration is not supported.
- LDAP user creation requires a configured LDAP integration.
- SSO user provisioning requires a configured SSO integration.
- Newly created users cannot access system resources until the appropriate permissions have been assigned.