 Hello, I'm Emilio Othano. Hello, the workplace solutions. Can you go to the next slide please, Adrian? Okay, apologies for the amount of information I put in here, but this is the summary of our sprint. We committed 47.66% of the points we, sorry, completed 47% of the points we had committed for this sprint, but we still have one day left. And there are many tasks that will be completed today, especially everything related with upgrade to 4.1. So this velocity will change at the end of the day. And for the composition of this sprint, we again focused on backfixing. So more than a third of our issues for backfixes and not including all the tasks involving the upgrade to model workplace 4.1, to model 4.1, sorry. There are a number of pieces that are still waiting for peer review or especially in peer review or integration review that will be completed today. So as I said, this velocity will increase. Can you go to the next slide please, Adrian? So these are the goals we have for this sprint. The main goal was the advanced tenant appearance settings, which has been completed and I'll explain it shortly. And the other big topic we have for this sprint was the model workplace 4.1 release, including these new dual version approach that we're starting with 4.1. This is ongoing and I'll also update you shortly. And from the discovery point of view, we completed the short midterm feature prioritization within the PEG. So now we have everything that we need to come up with an update roadmap for the next six to eight months that we're working on right now will be published shortly. And we'll continue with the learning catalogue discovery and now we're in the user story analysis and feature and casual team prioritization with the PEG. But something that we're planning to complete during the next sprint. So for the next increment, we have a third definition of what is an MVP of the learning catalogue and we can start the prototyping. So can you go to the next slide please? So the first big thing we have, or the main big thing we have completed in this sprint is the advanced tenant appearance settings. Basically in 4.0, we simplified the tenant appearance settings just basically to reduce the reserve of non-accessible core combinations to be set by tenant admins. So we tried to simplify this primary configuration to avoid the situation while we hid some of these features. So only partners or only developers could, not really developers, but they could be changed using CSS. But partners and other stakeholders requested us to bring them back because they wanted to be able to do this. So we found a way of doing that without compromising the site accessibility. We brought them back and this is how we did. So next slide please. Again, so basically what we did is adding, so we added back two settings to the tenant branding configuration, basically the navigation bar background color and the primary root and color and also move the CSS setting to an advanced section. So basically what we did is creating a new section in the branding page which is advanced and we moved all these new features to that section. Can you go to the next slide please? And we also introduced a new capability to define who is able to edit this advanced branding. So before this capability is only the site admins have it. That site admins can run this capability to tenant admins. So in summary, these features will be available to this advanced branding configuration will be available to site admins only, but they can give this permission to tenant admins if they think it is okay. So we just add it back in a safer way. Next slide please. And of course, we take off all the upgrade strips from previous versions. So another thing we did in this spring was adding the tenant allocation rules instead. Space is a bit technical service, but I'll try to simplify it. So in workplace we have dynamic rules to allocate users to tenants. And these dynamic rules have both conditions to check if a user, whether a user is in a tenant or not, and actions to allocate users to a tenant if they need to create the dynamic rule. These conditions and actions were not available in the service space, which is like a special tenant we have in workplace to create things that are served among all tenants for some permission restrictions, basically because we couldn't show details of certain rules to users who have no permission to see all the tenants and things like that. So in order to add these tenant allocation rules to the service space, we had to implement, we have to do some changes in the dynamic rules API so conditions and actions can mask or hide some sensible information for users who cannot see that information. So by doing that, we have been able to add these tenant allocation rules, which are very useful because they allow to create, allow admin to create automations in the service space and things like if the user, if the email domain of this user is at Moodle.com, then allocate this user to the Moodle tenant. And we can do that in the service space instead of creating this rule in all tenants. So this is something we have added to this screen. There are some small bits that are still in progress, but we're planning to add that into 4.1. Next slide please, Adrienne. And the other big topic of this release of this screen is the workplace 4.1 release. So the upgrade to 4.1 is being completed in this screen. So between today and probably there's something outstanding tomorrow. We'll finish with all the upgrade tasks and we'll be in the position to start with the QA test. So in the next screen, we're going to do the QA testing for 4.1. That this week, we're going to release 4.1 beta to partners. So partners will have 4.1 features available based on Moodle LMS 4.0 instead of Moodle 4.1. And at the end of this screen, we will release both the stable and rolling final versions of workplace 4.1, just after the QA cycle. Next slide please, Adrienne. We have added a number of other improvements. This is just a highlight. So we added a department to a department filled to the user profile condition in dynamic rules. We didn't have it before because in dynamic rules, we have organization extracted department and could be confused with the profile, the user profile department. But we have added it by request. We completed the migration of core report builder, custom report. That's something that was completed the last screen, but the review was massive. Part of the review of this issue and integration has been done in this screen. And we have introduced some settings to disable the program cover page if partners don't want to use it. Next slide please. And we also fixed a number of bugs. As I mentioned at the beginning of the update, it was a third of the points we have committed for this screen. So this is just some selected bugs that we can fix that have been reported by partners because we have been focusing on bug fixing, but especially on bugs that have been reported by partners or Moodle LMS. Next slide please. And last but not least, we are working on some improvements of our development workflow. Paul Holder has been working on this from the workplace team. So basically we want to introduce some, so formalize more the integration and integration review process in the workplace. So we start to introduce some changes in our workflows so we can clarify the state of the development. And basically adding these transitions, these new statuses and transitions for waiting for integration review and integration review. So formalizing it in a way. And also we're formalizing the review process to ensure the quality of the reviews is even. And it meets the standard that we have defined with the checklist. And we're also requiring more formal testing instructions as part of the acceptance criteria. So in some way we're moving towards the direction of what Moodle LMS team is doing. But the process is a bit like, this is something we focus on quick wings in this screen. And in the next increment we will introduce some deeper changes in these workflows. And next slide, I think this was the last one. Oh no, of course discovery. And finally, from the discovery point of view, we are refining the user stories for the learning catalog. We have a list of almost 500 tasks. We're trying to summarize it in a list of user stories around 50 or 60. And then we will use that to prioritize these user stories with our partners so we can come up with a roadmap for the learning catalog feature. This is something that is ongoing. This is intentionally small, just to show the amount of user stories we have. This is just like a small portion of them. And from the discovery point of view also, we're working on the workplace roadmap for the next 6 to 80 months. We have the priorities, the partners, both in the last priority session round. And now we need to create a roadmap, taking all the things into account and adding everything into the mix. Like dependencies or things that we need to in the workplace roadmap because are related with features that we want to release after. So with these combinational features, we will play the roadmap in the next weeks and we'll say shortly with partners. And I'm public, not only with partners. And I think that's all, next slide just in case.