- User Creation with AD Login without Invitation:
AD users can now access Prepare by logging in with their AD email instead of receiving or using an invitation. The correction is not automatically enabled for all AD organizations but is being rolled out gradually. This is because there are various AD configurations among your organizations. To ensure it functions as expected, we are gradually granting access to organizations.
- If you would like your organization to have access as soon as possible, please contact our support at support@firstagenda.dk, and they will assist in enabling it for you. Once the correction is rolled out to all, we will notify you through operational information.
As part of the work on AD login and user creation, we have also addressed a few other issues applicable to all organizations:
- No More @temp-mails and Guid Names
With this release, we expect to have eliminated scenarios where unreadable Guid names and @temp-mails occur. There might be a few edge cases that our tests did not cover, so if you experience anything different, please reach out to our support.
- Inviting "External Users" in an AD Organization
Previously, if you invited an external user to an AD organization, the user could successfully log in after confirming the invitation. However, upon subsequent logins, the external user encountered an error. This has now been fixed.
Automatic Activation of Disabled Users
Previously, when a user admin created an invitation for a disabled user in Prepare, the user would end up with a completely new user account instead of reactivating the existing disabled account. This has now been resolved, so when the user utilizes their invitation, the disabled account will be reactivated instead of creating a new one.Currently, the invitation does not disappear after the user accepts it. However, you can find the user among the active users. This will be addressed so that the invitation disappears once the user reactivates their login through the invitation.
Other Bug Fixes:
- Meeting Start Time in the email received when selecting "Download Content" from the meeting homepage was incorrect relative to the user's time zone. This has now been fixed.
- The timestamp in the "Download Access to Confidential Material" log was incorrect in relation to UTC time. The timestamp had an incorrect time difference of -4 hours instead of the correct -2 hours (taking Danish summer time and UTC into account). This has also been fixed. Please note that the correction only applies to agendas loaded after this release.
- The log file "Download Access to Confidential Material" has been renamed to "Download Access to Material."
This name change reflects that the log file includes information about access to both open and closed material. Organizational administrators can now see who has accessed an open document, rather than only seeing access to closed documents.
- The log list "Download Administrator List"
Now includes information about both administrator roles (user administrator and organizational administrator).