Android: Native: 3.0.6, JS: 3.0.11
iOS: Native: 3.0.6, JS: 3.0.11
There have been no updates to the app in the past week.
The Login screen has been improved and the 'enter a verification code' link has been removed, as users that have not entered their verification code to verify their account at the time of creation will be prompted to enter this when they login.
The sign-up process has been improved so that users will be automatically logged in once they have verified their account.
When a user joins Kura, the sign-up form required fields and validation remain the same:
Once the user has signed-up they will be prompted to enter the verification code that they receive to their email and can request that another is sent if required by selecting the 'click to resend' link:
Where a user has received an email invitation and followed the link, when they enter their code and select 'Verify', they will be logged into the Kura portal and linked to the organisation. If they belong to an Open organisation, they will be linked if an account was created on their behalf or they see an unlinked message and can follow this to enter their organisation link code.
If a user doesn't confirm their account at time of creation, when they next login to the portal, using the email and password they assigned during sign-up, they will be prompted to enter their verification code. They can also request that another is sent using the 'Click to resend' link.
The password reset process has been improved so that users will be automatically logged in once they have entered the 6 digit reset password code sent to their email.
When the select the 'Forgot you password' link on the login screen, they will be prompted to enter their email address, as normal:
They will then be asked to enter the 6 digit password rest code sent to their email and can enter a new password:
When they select the 'Submit' button the user will be logged into Kura.
Account deletion where a passenger has future bookings:
Where a passenger requests that their account is deleted, if they have future booked trips, they will be prevented from deleting their account.
A message will display confirming that the passenger has future trips booked and instructs them to remove these future bookings before they proceed with the account deletion:
Once future trip bookings are removed, the passenger can delete their account. If an observer requests that their account is deleted and their passengers have bookings in the future, they will be able to delete their account, as observer relationships can change e.g. where observers are assigned for assistance with childcare.
Open Organisations - Stripe payment element:
Where admins or Kura ops users make a booking and take payment on behalf of a passenger, for Open organisations, the Stripe element presented has been changed to match the payment element used in the app and for safeguarding organisations.
The Stripe in-line payment element is now used: