UI feature configuration
You can customize the 10Duke Login Application and 10Duke OrgAdmin by configuring whether features are enabled or disabled and what information is displayed.
The configuration work is done by 10Duke based on your requirements. Contact the 10Duke Integration Support team to discuss the changes you want.
See also the configurations related to localization.
Login Application feature configuration
The following feature configurations are available for the Login Application.
Registration page
-
Send an email after a user has registered to request them to verify their email address.
Email address verification is by default required in the system. This configuration option is provided to support custom implementations where email sending from the Login Application is not in use.
Default: Enabled
-
Which fields are displayed and in what order, and which of them are required fields.
If the system configuration defines required fields that are not included in this configuration, those fields are still displayed after the fields defined here.
If you want to use custom fields, contact the 10Duke Integration Support team.
The default configuration for the supported fields on the registration page:
| Field | Displayed | Required |
|---|---|---|
| First name | x | x |
| Last name | x | x |
| Professional title | - | - |
| Nickname | - | - |
| Preferred username | - | - |
| Email address | x | x |
| Password | x | x |
| Password confirmation | x | x |
| Phone number | - | - |
| Freeform address | - | - |
| Street address | - | - |
| Postal code | - | - |
| Locality | - | - |
| Region | - | - |
| Country | x | x |
| User agreements | x | x |
Regarding user agreements:
-
This configuration in practice only determines whether they’re displayed, and the system configuration determines whether an individual user agreement is required and optional.
-
If user agreement fields are enabled here but no user agreements have been defined in the system, a legacy “accept terms and conditions” checkbox is displayed as a required field.
Account activation
-
Show an input field where the user can enter the account activation code they received by email.
This can be used as backup for cases where the code couldn’t be automatically read from the URL provided in the email (for example, due to a broken link), so that the user is able to enter the code manually on the account activation page.
For reference, see example usage of account activation when creating a new consumer customer.
Default: Shown
Device client activation
-
Define the list of allowed regex patterns for redirecting the end user after the activation of a device client.
A regex pattern could allow, for example, opening an application on the end user’s device using a custom URL scheme.
For reference, see information on handling a device client invitation for activating a device client.
Login page
-
Place the secondary login options (such as single sign-on options) in the footer of the login page instead of below the username and password input fields.
Default: Enabled
-
Define the list of allowed domains for pages that are provided in the
nextparameter in the login URL, used for redirecting the user after a successful login.Not needed for pages that are in the same domain as the Login Application.
Example value:
https://www.externaldomain1.com, https://www.externaldomain2.com
Password reset
-
Show an input field where the user can enter the password reset code they received by email.
This can be used as backup for cases where the code couldn’t be automatically read from the URL provided in the email (for example, due to a broken link), so that the user is able to enter the code manually on the password reset page.
Default: Shown
-
Show the password input fields on the password reset page even if the reset password code couldn’t be read from the URL.
Default: Shown
Profile page
-
Which fields are displayed on the personal details and contact details pages and in what order, and which of them are required fields.
If the system configuration defines required fields that are not included in this configuration, those fields are still displayed after the fields defined here.
If you want to use custom fields, contact the 10Duke Integration Support team.
The default configuration for the supported fields in personal details:
| Field | Displayed | Required |
|---|---|---|
| First name | x | x |
| Last name | x | x |
| Professional title | x | - |
| Nickname | x | - |
| Preferred username | x | - |
The default configuration for the supported fields in contact details:
| Field | Displayed | Required |
|---|---|---|
| Phone number | - | - |
| Freeform address | - | - |
| Street address | x | - |
| Postal code | x | - |
| Locality | x | - |
| Region | x | - |
| Country | x | x |
Logout
-
Set an automatic logout after a timeout for idle users (users who are not interacting with the UI).
A timeout triggers a single logout (SLO). See more information on logout implementation using OIDC or SAML.
Default: 31 minutes
-
Display a warning to an idle user informing them that they will be logged out soon.
Default: 30 minutes
Other configurations
-
Enable the feature for managing alternative email addresses, for example, for account recovery.
Default: Enabled
-
Enable or disable transition animations, such as flipping the page content when navigating profile pages or applying the slide-down effect for notifications.
This configuration doesn’t affect the CSS-based animations used by the Login Application. Those can be overridden with a custom SCSS if needed.
Default: Enabled
-
Show a floating “log in to continue” message above the login screen in cases where the user is prompted to first log in before they can access the page that they were trying to access.
Default: Enabled
-
Show a floating message about a pending action in cases where the user must first complete authentication before they can continue the task they were trying to perform.
Default: Enabled
OrgAdmin feature configuration
The following feature configurations are available for OrgAdmin.
General configurations
-
Which sections are available in OrgAdmin. The sections are by default accessed from the sidebar, and the configuration also controls whether the corresponding data is shown as cards on the Dashboard.
Available by default: User groups, Users, Invitations, Licenses
Not available by default: Device client groups, Device clients, Roles
-
Configurations for each table view, such as the user table and license table:
-
Which columns are available in a particular table and in which order. You can define which columns are hidden by default (the user can show and hide columns from a menu) and disable any columns that should not be available at all.
-
In views that have filters for filtering the content in the table, which filters are available in a particular table and in which order. You can define which filters are applied to the table by default (the user can apply and clear filters from a menu) and disable any filters that should not be available at all.
-
-
Configurations on the following features that are available in multiple places in OrgAdmin:
-
Enable specifying the allowed software version when downloading a license.
Default: Disabled
-
Enable releasing a license lease that a user or device client is consuming.
Default: Disabled
-
Features on Dashboard
Configurations for defining which features are available on the OrgAdmin Dashboard:
| Feature | Enabled by default |
|---|---|
| Editing the organization’s details from the Dashboard title. | x |
| Viewing a summary card with the organization’s details on the Dashboard. (The other cards are included automatically based on which sections are enabled in OrgAdmin.) | - |
Features in User groups
Configurations for defining which features are available in OrgAdmin’s User groups section:
| Feature | Enabled by default |
|---|---|
| Viewing a user group’s details. | x |
| Creating a user group. | x |
| Editing a user group. | x |
| Deleting a user group. | x |
| Viewing the details of an entitlement that a user group is authorized to access. | x |
| Inviting users to a user group. | x |
| Managing the members of user groups: adding users to groups and removing users from them. | x |
Features in Users
Configurations for defining which features are available in OrgAdmin’s Users section:
| Feature | Enabled by default |
|---|---|
| Viewing a user’s details. | x |
| Inviting users to one or more user groups. | x |
| Importing users without an invitation. | - |
| Adding users to groups when importing. | x |
| Granting and removing administrator access from the Tools menu. | x |
| Viewing the organization’s licenses that a user can access. | x |
| Viewing the user groups that a user belongs to. | x |
| Viewing the roles assigned to a user. | - |
| Suspending and reactivating a user. | - |
| Downloading licenses (license tokens) for a user. | x |
| Removing a user from the organization. | x |
Features in Device client groups
Configurations for defining which features are available in OrgAdmin’s Device client groups section:
| Feature | Enabled by default |
|---|---|
| Viewing a device client group’s details. | x |
| Creating a device client group. | x |
| Editing a device client group. | x |
| Deleting a device client group. | x |
| Viewing the details of an entitlement that a device client group is authorized to access. | x |
| Inviting device clients to a device client group. | x |
| Managing the members of device client groups: adding device clients to groups and removing device clients from them. | x |
Features in Device clients
Configurations for defining which features are available in OrgAdmin’s Device clients section:
| Feature | Enabled by default |
|---|---|
| Viewing a device client’s details. | x |
| Editing a device client. | x |
| Deleting a device client. | x |
| Inviting device clients to one or more device client groups. | x |
| Viewing the organization’s licenses that a device client can access. | x |
| Viewing the device client groups that a device client belongs to. | x |
Features in Invitations
Configurations for defining which features are available in OrgAdmin’s Invitations section:
| Feature | Enabled by default |
|---|---|
| Viewing an invitation’s details. | x |
| Inviting users to groups. | x |
| Inviting device clients to groups. | - |
| Viewing the details of an invitation’s group from the invitation table. | x |
| Resending invitations. | x |
| Revoking invitations. | - |
| Deleting invitations. | x |
Features in Licenses
Configurations for defining which features are available in OrgAdmin’s Licenses section:
| Feature | Enabled by default |
|---|---|
| Viewing a license’s details. | x |
| Viewing the details of the entitlement where a license is stored from the license table and from the license’s details. | x |
| Using the license usage dialog for managing seat reservations, blocking and unblocking license usage, and viewing active leases for a license. Configure separately whether the features are available for users or device clients, or both. | x |
| Using the license usage dialog features for users. | x |
| Using the license usage dialog features for device clients. | - |
| Downloading a license (a license token) for users. | x |
Features in Roles
Configurations for defining which features are available in OrgAdmin’s Roles section:
| Feature | Enabled by default |
|---|---|
| Viewing a role’s details. | x |
| Creating a role. | x |
| Editing a role. | x |
| Deleting a role. | x |
| Managing the members of a role: assigning roles to users and removing roles from them. | x |