Bug & Fixes

Currently it's possible to assign a license for a given course to the same user twice (on different spaces). This lead to a waste of licenses

Steps to reproduce the issue: as an organization, create a space (Boston Celtics) as an organization, invite someone (User B) to the organization Note : right now User B see no spaces (see screenshot 1) as an organization, invite UserB to all the spaces as "space-member" via IAM section (screenshot 2) login as UserB and switch context to org as UserB, view Spaces (screenshot 3) as UserB, view Chat (screenshot 4) Expected behaviour : UserB see all the space chat rooms with "No Access" Actual behaviour : UserB doesn't see any space chat room Additionally, if the organization creates another space, UserB will be automatically added to the space chat room even if it's not a member of the space (screenshot 5)

warning message disabling members selection when trying to create group needs to be fixed as the following: allow the creation of groups with group members already selected. no warning message or disabling members is needed.

let's start the installment counter from number #1 and not from 2# as in the image

Currently, selecting only one calendar is not possible. it selects all calendar and same for unselecting. https://sharing.clickup.com/clip/p/t9004002740/630a69d8-d977-4b4f-91fe-09338267e0e9/screen-recording-2025-04-09-11%3A42.webm

Working on the auth domain templates for the demo Log In template Details template Passcode template

adding connection links or maybe pop ops to the Aladia Documents so in different parts of the platform new users can access to it in order to use the platform easier, particularly for the roles and complexing flows.

-> Licenses are not being assigned even when selected in the IAM panel. https://sharing.clickup.com/clip/p/t9004002740/a7037854-b886-47bf-aa0a-6f276416b1bd/screen-recording-2025-04-04-12%3A33.webm ->We need to add a cycle selector to the courses.

The BE instantiates a cron job to perform certain operations on user profiles, such as identifying users with birthdays and sending notifications. Since we have multiple BE instances running ath the same time, and each one creates its own cron job, these operations are executed multiple times simultaneously. To prevent this, we can leverage the shared lock provided by Murlock to ensure that the required operations are executed by only one instance . Note: The cron jobs will still be instantiated on all instances, but only one will actually execute the operations.

The filter for the past dates. It shows coming soon, but we need to show no data. The scroll to load more courses is shown repeatedly. https://sharing.clickup.com/clip/p/t9004002740/76216a45-952e-4191-b7d6-7cd96e0cef00/screen-recording-2025-04-02-17%3A59.webm