 So well, bit of context here. So in this page, my team's page, we are displaying the subordinates of this user. So we can share this information here. And the most important thing in here is that behind the scenes, this is a report builder system report. So we are making some tweaks here. So for example, instead of printing itself, we are rendering it template here. And another important thing is that any plugin can extend this information. For example, here, full program component is adding some information here. For example, the program name and the process of completion. Also, if this is an ever due item for this user and same for courses, jobs and et cetera. Also any component can extend and can add some extra links here to the full reports. And last but not least, the components can also add some warnings. For example, here we are seeing that some team members have overdue programs. Apart from this, the other thing I want to show is that we are replacing here the default filtering that comes from a report builder, standard report builder. So we are printing here this quick filtering. We are using report builder web services and also a dynamic table API. So we are doing the same thing, but replacing with our custom UI. And we can filter here only my direct reports. Also only I want to show items with new learning or not. We can basic searching and last thing where we can sort instead of using this column sorting because we are not printing the column headers. Here we can sort this dropdown. And yeah, apart from that, we are printing these links. For example, here we can go to this report and we are sending the user to the full report so they can play a bit more with all the information. The main goal is to show that we can, with report builder API, we can do cool stuff if needed. And not only so in the sometimes boring tables the other time. So yeah, that's me. So back to you, Emilio. Okay, so the next big feature we want to demo is the tenant colors that we generate automatically on tenant branding. So how about you, Andres? Hi everyone. So I'll start sharing my screen. Okay, so basically, we, before workplace four, we have this problem where all tenants currently will, basically they will identify tenants with coloring the entire navigation bar. And we end up having this like chance of color taking the majority of a screen view. In some cases if tenant means for some case, it's an area they choose and not appropriate color. This will take them basically a toll on the overall end user experience, stressing the user with probably with an accessible color palette. So in mortal workplace, we went for a much cleaner approach without these chance of colors and the option to set the entire navigation background color was removed and we're introducing now an algorithm that generates great skills and improves the selected color in some cases. So I'm gonna demo that in here. So first I'm gonna log in as an admin. I'll go to appearance and then let's pick a very light color. Light color, for example, a very light blue. And then let's go to my color. Even though this is a very light blue, you'll see that this option is selected. Let's go back and change maybe a darker. Here you go. So you will have this basically highlighted color in here and selected. And in order to sort of like highlight this more, I'm gonna share my this other second. Just to clarify this example and this is showing it's not applying the the saves of great that we automatically generate just by changing the color. I'm gonna share this example here taking in account some popular brands so you can see how it works. So here we have Starbucks with green, the branding color for Starbucks is highlighted in here and then the shades of gray are applied in the background with a greenish, more accent color and then Coca-Cola with red, the bright red. You'll see that the gray in the background is changed as well. And then for Samsung, they have this bright blue and the greenish background for the blue is also taken in account and it gets applied to everywhere. Not only the side navigation, but also all gray elements across the view. So yeah. This will be very short. So this is something we implemented in workplace team but for LMS. So we are planning to open source the report, build a block and it's all about configuration and using configuration in blocks is could use some improvements. So basically it doesn't matter which user I am even though I'm showing it as an admin when you change the block configuration it appears in a pop up instead of on the separate page. So you can modify something and it refreshes the page. It cannot refresh the one region yet. And another improvement is that when you add a block some blocks can say we require configurations. In this case, there will be like a little three dots appearing ellipses of things called in the end of the block name and for example, when you click on the block like this the configuration form appears before you even add the block and it has all the required fields that it's supposed to have and you edit and you edit immediately with the text. So as I said, we added it because we want to have open source the report to build a block and it's all about configuration without configuration doesn't make any sense. And it will just make it easier for both workplace and all of us users. So that was me thank you. And it has a question about this Marina. Okay, well, by the way, this hasn't been integrated yet. It's an integration. So maybe there is a chance that integrate to say no way and never let it through. So another feature we have added to this spring is the ability to lock departments and position frameworks from the site of space. This was a request from the community team for the MEC site and this is with this feature you can basically mark a department or a position as locked. So users without this permission with permissions to assign jobs on the locked departments they will not be able to use them. So basically if you want to create departments and position just for admins to use them this is the feature you need. So can you go to the next slide, please? Okay, another feature we have added this is the workplace part is actually in review but if we cannot make it for this opinion it will be available shortly. So even in the next spring. So we have added a feature on a new setting on Mural LMS to configure the services as support link. Now on one start plan we have another feature in workplace to make that setting multi-tenor. So you can define different service and support links for tenants. And the MDL parties are really a match and we're working on the workplace side. And the next slide please. So we have also added a new dynamic rules to assign users to learning plans that wasn't available. So this is the new action and as you can see you just need to pick a learning plan and the users matching the conditions will be added to that will be assigned to that learning plan. Next slide, please. And we have done all the improvements a lot more but just to mention some we have fixed about importing position frameworks added filters to appointments and also in Mural LMS ready to date filters option to select dates before a given period and we fixed all the bugs with organization structure. So next slide please. I think it's the last one, Adrián. Okay, so from the discovery point of view we have almost really the dynamic feature. I don't know if we'll be able to start with the implementation in the next spring but if not it will be in the spring after that. And from the learning catalog point of view we have finally a user story mapping that we have used to define the scope for the very first two releases of the catalog. We're trying to keep it small and release something that we can start learning from and measure it and that's the intention. So in the very first release we're basically replacing the functionality of the course catalog in Mural, the slash course page with our new catalog. And this is what we are going to add in this submission, I'm learning from.