 Okay. So my name is Lauren. I am a learning designer with Moodle HQ and I want to share with you today the top 10 tips, tricks, hacks that we're doing with clients all of the time on the learning design team over at Moodle US. So I am going to go really fast today because I'm sharing 10 things, but I'll put this slide up at the end. I have a document that has all of these with chip, you know, documentation links and things. So follow up documentation for you. So as a learning designer, as a lot of you are doing, I'm constantly listening to challenges and problems that clients have and then suggesting solutions to those challenges and problems. So that is how I have structured these top 10. So first problem. I want users from different tenants to be able to share courses. Usually this is because I want to create one course and then use it in lots of different tenants. So I want shared courses, but of course I don't want users to see each other, et cetera. Many of you are probably already using this one, but you know, our solution here is usually to create a category with those shared courses, alter the permissions on that category, allow authenticated user, add authenticated user to that category, and then you can use courses from that category across tenants. So you can have shared courses, updating a course in one space, having those updates appear all over for all users is usually the way that the client presents that to me. Some tips on this one. Use separate groups in your courses so that the users are truly separate from one another. Also, removing the permission to view participants from the student role at the course level, another really good way to make sure that no one ever sees anyone that they should not be seeing. So there's your tips for that one. Next problem. I want to send users direct links to courses, but I want to make sure they're routed through their tenant. This is very important to one of my clients. So for this one, and again, there's a document for you with this, but it's just adding this and tenant equals to the end of your course URL. So if you're sending an email communication or some reason you are sending this direct course URL to the client, adding the and tenant equals and then the tenant ID will be sure that they are routed through their tenant. So again, you go to the document for that one, but there's that tip. Just add that on to the end of your URL. No, nothing more for that. Next problem. The messages that my site sends out don't seem like they come from me. They're just the automated messages. Those can obviously be customized in the language pack. However, I think that when you are creating a dynamic rule, so this one, for example, dynamic rule to allocate users to programs, adding a notification to that dynamic rule and habitually doing this is a really, really, really wonderful and easy way to make sure you're personalizing the messages and even branding the messages that go out from your site. So some tips. Use those place holders that are right there in notifications to further customize and then also know that the multi-language content filter works for these notifications so you can even send communications to users in their own language that they have selected on the site. It's just using dynamic rule action include a notification. You probably want to disable some of those default system notifications that go out so you're not spamming users. Okay. Next problem. It takes me, so this is a site admin or a manager problem. It takes me so long to go where I want to go on the site. I have to click site administration. I have to go to users. It takes me a long time to get to the places that I always need to go to on the site. I am a huge fan of what I have come to call usable reports. Creating a usable report. So you know when you're building a report in report builder, you can have the courseful name or the courseful name with a link. If you create reports for yourself, you know, as a site admin or for your managers and you're using these link columns for the data, then when you're accessing this report, you're able to go directly to that place. So this is just a little trick, but to think about creating a report that is usable for you as a site admin or for those of you, you know, you have working on your site. Some tips on that one. Of course, just be sure to specify the correct report audience for that, because that's a very specific report that you're making. It is probably not for all. And then using the report block for easy access. So you know, maybe putting this as a report block on the dashboard, but that that report block has permissions where only site administrators or only managers, whoever it is you're building this for can access it or see it. Okay. Problem. I want data dashboards. We hear this all the time. Obviously, there's a lot of follow-up questions. What data? What do you mean by data dashboards? This can mean a lot of things to a lot of different people. And I was really excited by a lot of the things Emilio was talking about earlier. So, and Emilio mentioned this as well. I really love using a custom page with a series of usually report blocks to put a series of reports on that page for users to use as their data dashboard. Whether this is something that is for stakeholders who need to come in and look at data about users across the site or as we'll talk about in a second, whether this is for an individual learner to go in and see reports about themselves all in one spot. Some tips on this one. You can use a text block, of course, to bring in anything else that you want. So if a report block alone is not enough or you're integrating with something else or want to bring in some other information, text blocks give you that power. Depending on your site configuration, many different factors here, your reports may need to be created in the shared space. So be sure that you're testing this. If you are doing this and creating these custom pages with custom reports, just make sure you're testing with actual test users to make sure that you have the visibility configured as you need to. And make sure that your custom page audience and your report audiences are in alignment. This is obviously all just workplace-backed practice, but keep this in mind and test with an actual test user. Because sometimes this can be tricky. We have multiple layers of permissions with this one. Okay. Problem. I want a report that shows user their own information. And this is usually something like, this is usually said in a way, I want a transcript. I really want to show users a transcript. That's usually how I hear this one. This is my absolute favorite thing about report builder. So in report builder, there is a condition under users, and the condition is relation to the report viewer. And if you set this condition to themselves, then you are setting up this report so that when the user sees this report, they are seeing it as themselves. It is a simple and complicated concept. But this is so powerful in creating the reports that you are looking for if you are trying to create a data dashboard that is user facing and shows something like a learning transcript or learning progress. Tips on this one. When you are building your report, really think about it from the perspective of the user you are building it for. The default configuration of the report for this type of report is probably not going to work great for you. Enrollment type? That doesn't even make sense to most of our users. So don't include that on the report. It will just be confusing access information. So just kind of put on that hat of the user. What do they want to see on this report and how do they want to see it? Do you want this report to be those live links with the link or do you want it to be static? Consider all of those as you are building the report. Make sure your report audience for this is set to all users because this is a report that you would want all users to have access to so they are seeing their own information. Next problem. I want to easily give users access to lots of courses and I don't want to do a lot of manual work. I don't want to go in course by course and configure self-enrollment or whatever it is. I want this to be easy and fast. I think a program is a really, really excellent solution for this and works really well for some organizations. So for example, I have a lot of organizations that have webinars. They have courses. They have 100 courses of every, you know, webinars that they did all of that year. They want to easily give all users on their site access to those webinars. And so I have them create a program, toss all of those courses into that program, and then we have a dynamic rule that says if you're not allocated into this program, allocate users into that program. It means that when those users log in, they see, you know, 2023 webinars, they see all of those courses, they can access whatever they want, but it was very little work on the client's part. I love that a program does not actually enroll a user into the course until they click into the course. And when I talk with clients about that, I say, you know, it keeps your data clean because if you want to see how many users are actually accessing the courses, you can see that. I mess this up all the time. Make sure your program completion is set for main completion all in any order, right? Because there's no sequence to this type of program. This one's really simple, but related. You know, my programs are just a mess. I just dumped 100 courses into them, and now it's a mess. This illusion here is obviously sets. Sets are really powerful, so you could have 2023 webinars, but then you could organize those thematically in sets. And I have clients doing this with hundreds and hundreds of courses in a program and then many, many sets of courses. Tips there, you can have, you know, each set can have its own completion logic, so you can get really complex when you're using sets within programs. This one, I'll go really fast because it's on the roadmap, but it's not there yet. I want users to be able to self-enroll into programs. That is such a common request. I'm so excited that it's coming. The way that we're usually doing this right now, okay, he want to know. So let's say you have a Moodle basics program that you want users to self-enroll into. Create what I call a portal course. Just create a course called Moodle basics program enrollment course and make sure self-enrollment is enabled on that course. Then create a dynamic rule that says if the user's enrolled in the Moodle basics program course, allocate them to the program. Woo! Portal course. Okay. Don't worry. I have this in the document for you with even more steps. So you need a way to display the self-enrollment course, the portal course, obviously. However, you're kind of displaying courses. You might be on the dashboard or filter codes, whatever it is. We can talk more about that. And then here's a really important tip. Consider a dynamic rule that will then unenroll the user from the portal course because you don't need it anymore after that and it will clutter up their My Courses page. Okay. So this is our last one. Problem. I just want to automate so many things. I don't want to do manual work. I need the system to be doing a lot of work for me. This is just sort of my catch-all, if you will. But between these two pieces, custom profile fields and dynamic rules, you can automate so many things on your Moodle site. So if you have users somehow selecting information about themselves, preferences, whatever it might be, you can then put them into things and places or assign them things that you need to assign them. I know that one is vague, but I wanted to end with it because I think that it is just the biggest net and has the most potential for letting you shortcut and automate processes on your site. So dynamic rules and custom profile fields. So that's it, 10. I hope at least one of those is something that you could use. I have that back up there for you. The document goes into some more detail, links to Moodle docs, where needed, and then would love to answer any questions you have about this or anything else. So thank you all very much.