With our product roadmap we share our vision of the future of Adaxes and reveal the main features we are planning to implement. We would love to see your contributions, which you can provide by upvoting the features in the list and by submitting new suggestions via this form.
Please note that the Adaxes roadmap is just a preliminary plan, so the order of implementation might change and not all the features listed below may make it into the final product.
Add support for SAML 2.0 protocol to provide Single-Sign-On to the Web Interface using SAML-enabled identity providers.
Add support for resource mailboxes in Exchange, such as room, equipment and shared mailboxes, i.e. allow viewing and managing them from the UI and using in automation workflows.
Allow granting rights for user calendars in Exchange via Administration Console and Web Interface and setting it in automated workflows, e.g. during user provisioning.
Hide default delegates, such as Exchange Servers, Exchange Trusted Subsystem and others from the Delegation tab of Exchange mailboxes in the Web Interface.
Add an option to enable or disable the auto-mapping feature in Outlook when granting full access to a mailbox.
Add support for Exchange ActiveSync Mobile Devices for actions like triggering device wipe, adding devices to the ActiveSync blocklist or whitelist, quarantine and un-quarantine devices, etc.
Allow dynamic updates of forms in Web Interface. For example, change which fields are displayed on the user creation form based on the Employee Type property or depending on which Department is selected, alter the values in the drop-down list for the Job Title field.
Allow approvers to approve or deny approval requests using just a link in the received email notification without the need of opening the Web Interface.
Add support for query-based groups, i.e. allow managing them from the Administration Console and the Web Interface and use them in automated workflows.
Add a possibility to add members to groups for a limited amount of time.
Allow users to bulk import Active Directory objects from CSV files via the Web Interface.
When entering a new password in the Web Interface, display additional information, e.g. if the entered password is weak or strong, whether all requirements are met, etc.
Allow specifying properties that need to have unique values with the help of Property Patterns and define what needs to be done if a value is not unique. For example, automatically add a digit at the end of an entered username if such a value already exists.
Add an option to Property Patterns which allows generating property values with the help of scripts. For example, automatically generate a custom username on the user creation form using a PowerShell script.
Add more options for drop-down lists. For example, automatically put in all the existing values of the Department property as values of the drop-down list when creating or editing user accounts.
Allow filtering AD structure in tree views, e.g. in the browsing drop-down, similarly to how it’s done in list views.
Allow replacing and removing specific characters when generating values with the help of Property Patterns, e.g. always replace ä, ö, ü with a, o, u.
Similarly to cutting a certain number of symbols from the beginning of a property value, like getting the first letter of the First Name with %firstname, 1%, also allow cutting a number of symbols from property values from the end.
Add support for displaying images in approval requests. For example, if a user updates a profile picture, the approver should be able to see the image straight in the approval request.
Notify users if an operation that was sent for approval fails after it was approved.
Allow specifying From, CC, BCC fields, setting Sender Name and adding attachments for the ‘Send e-mail notification’ action in Business Rules, Custom Commands and Scheduled Tasks.
Allow updating the operations that were already sent for approval. For example, if an approver notices a mistake or needs to provide additional information for the operation, let them introduce the edits before approving.
When an operation is sent for approval, allow the initiator to specify the reason for why the operation needs to be executed.
In addition to the reason for denying an approval request, add the possibility to similarly specify a reason for approving the request.
Add unique identifiers to be associated with each approval request, so that it’s possible to easily find specific requests and refer to them using their IDs.
Store the date when the approval request was processed for better tracking.
Allow creating AD objects in automated workflows by adding corresponding actions to Business Rules, Scheduled Tasks and Custom Commands.
Allow adding images to emails that are sent when an operation requires an approval. For example, to add your company’s logo to the header or footer of the emails.
In addition to object owners specified in Active Directory, also allow specifying co-owners for AD objects.
Add support for HTML-formatting of emails, such as Enrollment Invitations and Reset Password notifications.
Send notifications about already existing approval requests when new approvers are added. For example, if users are added to a group which allows them to approve or deny requests that are awaiting approval, send a corresponding email notification to them.
Similarly to sending actions for approval to group owners, also allow sending approval requests to co-owners who are specified via ms-Exch-Co-Managed-By-Link.
Add options to authenticate Adaxes in Office 365 with a client certificate or App password in place of using credentials of an Office 365 account.
Note that in order for us to implement this feature, we need Microsoft to support the authentication types in their PowerShell module for Exchange Online. To speed up the process, you can upvote the respective suggestion to Microsoft here.
Add virtual properties to simplify getting information about owners of Active Directory objects. For example, allow using value reference %adm-ManagedByEmail% to send an email notification to the owner of a group.
New virtual properties should include adm-ManagedByEmail, adm-ManagedByFirstName, adm-ManagedByLastName, adm-ManagedByFullName, adm-ManagedByMobile, adm-ManagedByTelephoneNumber, adm-ManagedByUsername, adm-ManagedByParentDN, adm-ManagedByParentName.
Allow users to modify objects in bulk in the Web Interface, for example, to set a manager, change account expiration date or enable smartcard authentication for multiple users in one go.
Allow storing AD objects in Adaxes virtual properties the same way data is stored in properties like CustomAttributeText1 or CustomAttributeBoolean1.