Stories of digital innovation by no-code
Discover the opportunities of the channel program
Join the Network
Leverage the resources of Jamio
We collaborate with universities
News from the world of Jamio Openwork
Stay up to date on the world of no-code and digitalization
The periodical on no-code and BPM
Events dedicated to Jamio producers, partners, and customers
Free downloadable guides
Independent Software Vendor
Join our team
Our locations
Forever part of who we are
The most notable new feature is the ability to enable two-factor authentication (Multi-Factor Authentication), making user access more secure.
The Admin Console with the introduction of account management.
Each user, after being enabled by the tenant Jamio solutions more securely by adding an OTP at each login as a second authentication factor.
The code can be sent via email , SMS , or mobile app (choosing between: Google Authenticator, Microsoft Authenticator, and many other apps) .
We have introduced a dedicated web application (MyAccount) to help users certify the channels and contact details for OTPs .
Account management has been added to organization management . It will now be possible to manage an account's lifecycle, from creation to disabling, and define access policies. Catalog .
From now on, you can preview signatures applied in Pades . Jamio will also prevent you from attaching two files with the same name to the same form.
Continuing the developments introduced in version 4.8, account management, account policies, and password policies have also moved to the Admin Console. Identity management and task assignment will remain on Jamio
The way in which identities are created remains unchanged: it is always done manually on stage Jamio
No. Account management has been moved entirely to the Admin Console.
Now everything is centralized in the Admin Console where the administrators group, by accessing the user management menu, can:
The account can only be created if an identity has first been created for that individual.
On Jamio on stage , a new field called Account appears in the Built-in Identities catalog that indicates whether an account exists for the respective identity . This information is a new identity property called HasAccount .
No, it is no longer possible to perform actions on accounts from Jamio on stage.
Two-factor authentication (2FA) adds an additional layer of security to the platform's native . After entering the password, the user will be asked for an OTP code , which can be received via the channels defined during configuration by the administrator, i.e., via email , SMS, or via market authentication app .
Only the administrator group can enable 2FA for an account. To do so, you need to define an account policy that includes this feature. This policy can be assigned to end accounts.
In the account policy definition form , simultaneously whether 2FA should be configured and the channel for sending the OTP code ( email , SMS, market app
Yes. When accessing the system for the first time, the user will be guided through the configuration of the channels enabled for receiving the OTP ( email and/ or SMS , market apps). These operations are carried out on a dedicated application called " MyAccount" .
MyAccount application each user can:
It can be reached at: https://paas.jamio.com/myaccount .
Each user can Jamio credentials .
Yes! Now an administrator can disable internal authentication for specific accounts, forcing them to use external methods (e.g. Single Sign -On – SSO) , by setting this characterization in the account policies, selecting the “Disable internal authentication” value .