Having the ability to create content in Google Docs, Google Sheets or Google Slides, embed it in an iFrame and have it always up to date in the training material would be fantastic.
It would mean no more copy pasting, since any updates would be reflected in the training material instantly it would NEVER be out of date.
This means we can have our content in a file structure that makes sense for us, have it backed up, editable by people who do not have or need access to TalentLMS AND we do not need to either copy it into TalenLMS (outdated as soon as its copied), or export to PDF (ANY change > re-export > re-upload (if you remember WHERE it was attached in the first place) > delete the old version > etc.

Alternatively, just let us upload those via Web Content!

I've started using the main domain and now I have the necessity to use branches.
It would be really nice to have an auto-redirect when the user has access to only 1 branch. In the user experience point of view, it would be much better then the current solution that appears like an error to user.

Additionally, it will be possible to use the same communication about the portal using always the same URL when we are using the branches with different users in each one.

The solution could consider a configuration in USERS section of the Branch Info. After select "Disallow members of this branch to login from main domain URL", it could give to admin the option to enable the auto-redirect when the user has only this branch.

As it stands, users are expected to include their own Unique ID to questions, however, it is very difficult to enforce any kind of standard method of creating the UIDs. One person will use one method, someone else will use another and there is often no logic.
When there is already a backend UID on the system it seems odd that we don't have access to it. There would be no need to edit it, as it would only be required for reference/support purposes. This would remove poor UID discipline form the equation, ensuring a sequential logical naming convention is used throughout.
It would also look a bit more professional than having a random string at the beginning that had no relevance to the question being asked.
Presumable it would only require a read only lookup value placed before the question which would be visible to everyone.

With this in place, anyone with an issue with a question, would just need to UID rather than having the following scenario:
User - 'It's The question about derivatives',
Support - 'There's 66 of those'
User - 'The one about Derivatives in France'
Support - 'Ummmm' I'm searching for that but not seeing anything'
User - 'It's got something about boats?'

With the backend UIDs, this conversation would look more like:
User - 'I have a problem with the wording of question AD00475'
Support - 'Yes, i can see that question, how can i help?'

Please consider this request as it will very much help the management of our questions.

Many thanks

For now, the unenroll must be done after
- you remove a user from a group using API
- you request a group using API to search every single course
- for each course, you should unenroll the user

Why don't you just add a parameter on user removal from a group (false by default and not required, so you will not break the existent API) where we can specify if we want that user to be unenrolled from all courses of that specific group?
The same discourse is applied on group assignement to a single user, where we could enroll all courses of a group with a single call.

It would be extremely helpful if you could set a course to release on a specific date and time. The current automations are limited and require a lot of manual calculation of hours. For example, our training program is 7 weeks long, we release a new course every week on Friday at 8am, the courses are sequential. We do not want the learner to start working on a course until it is released on Friday. We also run multiple cohorts at a time. The current options to automate when a course is released does not work for our program and requires we release courses manually. It is just not efficient and this is a very simple automation - it just involves adding a calendaring system - I can't believe this was overlooked as an option.