Alright. We'll get moving. But first, some introduction. My name is Beth Carey. I am the membership lead for Asia Pacific. I work with some of our biggest clients, sometimes over years, to help them succeed in their data journey. With me is Roger Garcia, who's a solutions engineer also based in Asia Pacific. Roger's job is to understand our clients' environments end to end, how that aligns with their data desires, and to stitch it all together to get a great result. I'll be doing a general introduction to Interworks and to Curator, which is our out of the box solution for an analytics hub. And Roger will be taking you through the Curator product, showing you how it might be used to spin up an analytics hub in a fraction of the time it might take to do one yourself. Some housekeeping. Please use the q and a on your screen to ask questions as we go. We'll answer some as we go through, and then hopefully we'll also have some time at the end. If you do have questions today that we don't get to, don't worry, we'll follow-up with you. We will use the chat throughout to post links and things of general interest. We do ask that you use the q and a though, because that helps us manage questions as they come in, and that way we know what's still outstanding. If you get disconnected from this session, or we do, don't panic. We'll be back straight away, and you can use the same link as the one you used to join initially. Now there is a poll in your Zoom controls right now, which I think most of you have filled in, so thank you for that. If you have yet filled it in, please have a quick look at that one. It gives us a steer as to where you're all sitting and will help inform today's session. Okay. So, this webinar is being brought to you by Interworks. But who is Interworks? We're a global tech consultancy. We work across the data journey to bring a great result for our clients. We started in nineteen ninety six in the US, focusing on IT hardware think running wires through ceilings and since then have expanded into analytics, solutions, experience, enablement and strategy. We were actually Tableau's very first partner ever, which I think is pretty cool, and we now have offices all over the globe. These are some of the things that we do. As I mentioned, we span the whole data journey. You can see on here data, analytics, experience, platforms, enablement, IT, solution. So wherever you are in your data journey, we can help. And these are just some of our clients. We span verticals, whether you be in mining, toll roads, energy, fast food, or printers, we've got friends in those spaces. And we've got some big names in here that you'll probably recognize. Groups like Netflix, Nike, Hungry Jacks, and Twitter. These are just some. We have everything from the smallest of small to the biggest of big. And from a partnership perspective, we're a best of breed shop. I'm gonna discuss more of that today, but it means we have partners across the span of your data journey. From the hardware that you use, to where your data is hosted, to your analytics and your data science, we choose the best tool for the job. And we pride ourselves on doing the best work for the best clients with the best people. These are our guiding principles and they sit underneath everything that we do. So that's a little bit on us. But what are we going to talk to you about today? Our topic for today is DIY Analytics Hub. Specifically, we'll be talking about what an Analytics Hub is, why an Analytics Hub is important, and why you should use Curator from Interworks rather than building your own. So some context here. BI is a mature market. What started small is now a massive industry. You've got groups like Tableau, Power BI, Qlik, ThoughtSpot, Looker, and more. And some of these are worth a lot. It is not going anywhere anytime soon. But despite this, BI has a really high failure rate. Gartner estimates that only twenty percent of analytics insights deliver business outcomes. Twenty percent. That means that eighty percent of them fail. Now there are many reasons this happens. I work with some of our biggest clients over many years, and I see issues from enablement to user adoption to platform stability. But one of the biggies, which we'll be focusing on today, is inconsistent locations for analytics products. This breeds confusion and annoyance for end users, frustration for IT and BI analysts, and it undermines your return on investment for your analytics spend. So I'm going to go to an old quote, and I promise you this will make sense in a minute. If you're given a hammer, everything starts to look a lot like a nail. In a BI context, you invest in a tool and then you wanna solve everything with that tool. What's the question? Doesn't matter. We've chosen the tool. This is the tool we use. Now that's absolutely fantastic if your problem happens to be a nail. Fantastic. I have an hammer, a hammer, my problem is a nail. But what about when it's not? What if it's something else entirely or you need to build something more complicated, like a whole house? If you wanna build a house, you're gonna need more tools. So in comes some additional tools, each with their own person to drive them, their own specialized tool with its own specialized person to solve the problem. And these guys are great. They paint the walls, they fix the sink, they've all got their own job. So what's the problem? Well, it's the problem of how you maintain it. How do you manage? And how do you grow from here? So I'm just gonna check out the results for your poll, and I can share the results with you. So what have we got here? We've got Tableau being used in seventy nine percent of instances. Got it up here on the screen, so hopefully you can see that. ThoughtSpot, we've got three ThoughtSpot people. Thank you very much for that. They're no signers, good chunk of Power BI, a looker, and some other people making some comments in the chat. So you've got a wide variety of tools. Now I'm gonna bet that some of you also have more than one. Now at Interworks, we have a best of breed approach. That means that we choose best tool for the job. Oh, here we go. I'm looking in here. Someone's got Cognos. Yep. And Cans Insight. I haven't come across that one before. There you go. New one. So a wide variety and probably multiple within the same organization. Feel free to comment in the chat if your organization is using more than one, maybe more than two, maybe more than three or four or five. Maybe you don't even know what everyone is using. That's always my favourite combo. Now, this isn't unusual. And in some ways, it's not a problem. So at IntuWorks, we choose a best of breed approach. Now that means we choose the best tool for the situation. Some of that, though, is gonna be personal preference. I love Tableau. It's my favorite BI tool. I have a lot of fun building things. But just because that's my preference doesn't mean it's yours. For some people, it's Power BI. For some, ThoughtSpot. It depends on the problem you're solving, your business, and your unique preferences. Or generally the unique preferences of the one holding the money. Some people want to paint an artwork on the wall. Some people want to grab a wrench and work on the sink, and that's fine. There's an almost Darwinian situation here. No matter what, if someone wants a tool and they are important enough to organise the money to buy it, then they will find the budget. And so over time you end up with a lot of different tools. The vast majority of clients I work with have multiple tools. It just happens. Now this isn't an issue in and of itself, but it does create a new problem. Now I have to support a bunch of tools. And if I have to make a new thing, or worse, find something, where is it? What tool was it in? How do I find it? And now my users are confused. This gets even worse if you're a non technical person and you just want your question answered. You don't care what tool it's in and you're getting frustrated when you can't find it. So how can we make it simple for an end user who needs to be able to find the answers to their questions across the range of tools in your organisation? Well, we've hit a problem with volume and flexibility. Consider how we respond to Netflix. You wanna watch something, but you don't know what. At the end of the day, you're exhausted. I've got two kids under five. I know I'm exhausted by the end of the day, and I assume some of you are as well. So what happens? You sit down, not sure what you wanna watch. You start scrolling. You keep scrolling. Your eyes glaze over. Or worse, you have multiple platforms. Even if you know what you want to watch, you can't remember what platform it was in. Where was that show? You scan one platform, you scan another platform, you get frustrated, and then you can decide to continue watching the same series you started last week, but which you don't even like. The point is people don't respond to get well to getting heaps of options or to disorganized content. In the context of BI tools, watching the show I started last week that I don't even like, I've taken the Excel route. Duff this. I'm doing it the way I know how, even though I know there's problems with it. Now this is not an unknown issue. Usually, clients try and do something like draw a box around all their tools, summarise them in some way, and list it in something. And you end up with a list of where things are. Maybe you want finance stuff, well, that's in Power BI. You want marketing stuff, that's in Tableau. You might make this list in SharePoint or distribute information in Teams. Or worse, some poor IT admin has a OneNote file of where everything lives. And then that IT admin leaves and you've lost the OneNote file. Your BI team is frustrated. They're spending their time in content moderation and mapping. And this has a real world cost. It costs time. It costs money. And as people get frustrated, they stop using your tools and adoption punnets. And you don't get your return on investment. So, Curator. Why did we invent this product? Curator is our attempt to solve this problem. It actually started as a solve for a few things, like all great ideas. For example, a front end for Tableau Server. If you spend a lot of your time in Tableau Server, you know it isn't easy to find your way around. It's a bit like the Wild West over time. You can find yourself hunting for a production report and you find yourself in the sandbox, grabbing old and incorrect numbers and sending them to the CEO. You might also want things sitting alongside your dashboards and reports, like data dictionaries or Excel files, PDFs, or a video explaining how to drive a dashboard, use the data it provides, or which data you should send to your CEO. Or maybe you just want a frontend that looks and feels like your organisation or your client's organisation so it looks like them and feels like them rather than you. Curator was developed to give us control over the whole experience. We were building ad hoc ways of doing this over and over again, and so we created a product for it. And one of the big things Curator can solve is bringing together your BI tools into a coherent single location. So when we talk about building out a hub, it's a build versus buy situation. Either you have a team of dedicated web developers building this central tool and maintaining it with APIs over time, or you get a trust and you use Curator. Now the typical runway, to put some perspective on this, that we see for a build it yourself option is about six months. And that's not because there's no talent or appetite for it from the developers or the IT team. Just hard. And it's ongoing. If something in that product changes, you need to adjust how you brought it all together. You need a dedicated team and resources. Curator is a way to say, you know what? My dev time is scarce. I will use an existing off the shelf product and focus my development time on something else. So in a minute, I'm gonna show you, or Roger is how easy it is to build an analytics hub in Curator. Now, importantly, that's not to say that if you buy Curator, you have to do all this yourself. We definitely help you set it up as part of purchase. But seeing how easy it is can show you just how amazing this off the shelf product is and how quickly you can use it for your business. I'm gonna pass you over to Roger, who's going to lift the hood a bit and step us through. Thanks, Roger. Thanks, Beth. I'm just gonna screen share. Let me see if you could please confirm that you see the Interworks side. I do. Wonderful. Cool. So let's shall let's go and build an analytics app, shall we? So let me first step you through the classic journey that our clients have gone through when deciding to build an analytics app. First off, that would have, for example, dashboard in Tableau, for their customers, they know that if they want to understand the Salesforce customers, they would find that dashboard in that specific folder project right, they can effectively see the insight that thereafter, they know how to render and slice the dice data, as they see fit right now, you'll have another team that will say. Instead of using Tableau some of them might actually be using say, for example, your executive team may be using thoughts for. Right what again they've got the KPIs they're able to search the data without any sequel and just be able to just see the same insights right. And conversely, you might have your it team that says listen, we need to monitor our cloud infrastructure cost we've built this dashboard in power bi right What again, they've got the analysis that they need. They've got the answers that they're after, etc. Right? A couple of things pop up as a result of this transition. Right? First of all, you'll notice that all of these tools have a lot of options that are very useful, right, and are very useful, in particular, in the context of BI. So if you need to effectively edit the view, or you need to do some configuration, change the data that you see, subscribe to it, etc. Right? But those elements are less relevant. What when you're trying to do is to effectively generate consistency across all dashboards. And in particular, when you want to present your analytics as part of brand exercise as a way for you to signal your corporate identity. Right. So, for example, if you see here all these interfaces, as I mentioned, they're very slick. They're very good, but they're good for BI purposes. Right. Now, the second thing that stems from just going through these interfaces is that obviously you can tell that they're Power BI or that it's ThoughtSpot, right? You see the logos, you see that it's Tableau, etc. Right? How can we create that consistency across all platforms, as Beth Rattley mentioned earlier, curate is here to precisely generate that to break to become that one stop shop for all your BI tools. And at the same time, to generate that consistency. Now, when we talk about consistency, from an interface perspective, don't think of it only from a branding perspective, it's just not that we want all buttons to look alike only. It's also that a well established fact within the BI industry is that users will feel more comfortable when they are acquainted with the interface, that there's higher adoption of BI tools when users just know the lay off the ground. Right. So all these different interfaces might be a bit of a showstopper for some people when it comes to using BI or adopting a new BI tool. Okay. So with that being said, let me first show you what happens if I just go ahead and spin up a new curator. The site that you're looking at is exactly an off the shelf Curator instance. Right? And this is the instance that we'll use to create our analytics hub. Okay. Now, as Beth mentioned earlier, when you go ahead with Curator, you will have a team behind you. Right? What I'll do today is not necessarily a training, I teach a lot of training. It's more a demonstration, a step through. I'll walk through, but I'll step you through the key sections. Okay. Also note that this is being recorded. So you'll be able to just watch these steps later at a slower speed, or if you want to watch it again, by all means. Okay. So let's start with we will divide today's setup in two main blocks. First, we'll make the front end, the branding look like your company. In this instance, it will be Interworks. Right? And secondly, I will have the dashboards that I just step you through effectively connected to it. So you can see, and you can see for yourself how Curator integrates that, and there is with which you can achieve that result. All right. Now, let's start with the first step. My company will be Interbox, right? This is the website that we have our landing page. And what I'll do is I'll just simply want to stick to having a header similar to the one I have here with a hero image, and effectively try to reflect the logos, etc. Just so the look and feel of my instance looks like Interworks. Right? But obviously, this could be done for any company or any brand identity. Right? I will not have this carousel. I just simply have the static image to keep things simple. Alright, so let's start with that. What I first do is I look at my curator instance. So this is my curator instance. Right? But I look at it from the back end, right, from the kitchen, so to speak. Right? That's the back end of my curator instance. Right? Now there's a few things that pop up here. But let me step you through how we can achieve the result that we want, which is let's make our instance look like in this case, Intubox. Right? How do we do it? First, we will adjust and configure the theme of this curator instance. The theme is something similar to you know when you use PowerPoint and you create a master slide that has the right font size and whatnot and then that applies to all slides. So the theme of curator is pretty much that right. It's an oversimplification, but just for for for this for the purpose of this conversation today. So to do so, I'll just go to settings curator themes. I'll click there. And then I have the main theme, the theme that has been used at the moment to render the look and feel of my incident. First things first, something really cool about curator is that I've got this preview at all times. So any changes that I make here, I will be able to preview it before releasing that to production. Right. And you'll notice that none of the changes that will do will require any front end capabilities whatsoever. So forget about CSS and JavaScript and HTML, etc. Right? So let's start with that. First things first, I've got brand option selected. Right? And then I'm just going to go ahead and adjust my logo and my favicon. Now, what's the favicon? Favicon is just this little icon that you see here in the in the tabs. So we'll adjust that. And we'll also adjust the logo that is displayed in my instance. To do so, I can just upload files. I've already prepared my files. I've got them right here. So what I'll do is I'll just take my fabric and I'll load it. And then I'll do the same with my logo. And I'll just simply load it right. Now notice first off that here I have already the fabric on adjusted. Then once I save, this will effectively be displayed. Secondly, you notice that my logo, the one that I highlighted has disappeared. It doesn't have this. It hasn't not disappeared. It's just that the logo I rendered is black and the and the background is black. Right? So what I need to do, and remember, I'm trying to replicate this section here. I need to make this menu head up wide. How do I do that? You probably can guess. I just go to menu, navigation background color to be white click away. And sure enough, it appears now and then I'm going to make the text because in the future I'll create this menu so I'll just going to make the text black but that will make no difference now, but it will do so when we do it later. Now, one thing I want to adjust is the size of this logo. Now I have because I looked into that earlier, or what I'll do for now is I'm just going to add some padding. Right? Padding is just simply some pixels between the between the actual element and its container. Right? So I'll just go ahead and put here some padding. And that will just adjust a bit more. Sure enough. Here we have a second. Just give a second. There you go. Right. Now that's already there, and it's in my preview. Right. So how do I go and implement that? Just click save. And from that one, that header will effectively apply to all pages that I create. Right? Don't take my word for it. Let's check it out. This is my curator instance before. And this is my curator instance after. Right? Logo, background, fabric, literally six clicks. Right? Now, let's do a few more things. I mentioned earlier, I wanted to change this image. This is what's called the hero image, right in web development terms. And what we'll do here is we'll effectively replace it with one that just signals precisely, but we'll be using this image right here. Right? So there's that consistency. Right. So let's do that. What I'll need to do, though, is I'm going to create a page, think again, using the metaphor of PowerPoint thing, a slide. Right? Right now, my theme is using the sample homepage. So there's a page that is actually being rendered. Right? So what I need to do is I need to create one page for that purpose. I need to create some content. So let's do that. How do I do that? Pretty simple. I go to content pages. Right? That's the page that I have rendered now by default. And as the interface can just tell you, I simply go ahead and create, a new page. I'm gonna call this into works analytics hub. And again, as per curator, you see that I get the preview down here. Right. I'm going to show the title because I don't I'm I'm going to hide the title because I don't want to display it. So toggle that. And now from here, think of it as we put contents blocks of content in this page. Right? This is a blank page. We see that the interface or the look and feel looks like the theme that we designed. But now I want to start element, adding elements of content, blocks of content. Right? How do I do that? There's one by default that I just click on it. Okay. And then I can just go and change that element. Now, as Beth mentioned earlier, BI is typically presented alongside other content. In other words, your analytics app will not just be analytics content, it can be images, it can be videos, it can be text, etc. Right. So what sort of elements can we add? Pretty much the limit is the sky. I can add any element in terms of web elements, right? Think of it lists, tiles, hero images, etc. Right? I can add analytic elements that is I can embed a dashboard within a page or additional elements, like cloud, YouTube, etc. Right? For now, I'll just go and add a hero image. That's the placeholder. Let me just go now and add the image as such. So I can just simply trigger that menu, and it will allow me to just choose a file. Right? So from choose a file, I will just go and obviously load it from your machine. In my case, I've already done that earlier. So I've got the image here, temporarily stored. Right? So I'll just go and click that. And you should know that's my. Right? Let's just tweak it a bit. Or what I'll do is I'll just give it a height of, say, six hundred pixels. So it looks there you go. Not its glory. And now let me just make it full width. So instead of just ending what it does, let me just do full width. Right? And there you go. I've got my image now up and running. Okay? I'm gonna create that page. Remember, we're just creating a new page and slide, if you will. Right? And that page is now created. Right? We can see it right here. Right? Now the last thing we need to do is we need to make sure that that theme picks up that page. Right? So we'll just go back to the theme, what we went earlier, what we're doing the configuration earlier. Right? And simply say to this theme home, we'll say don't render the sample page that comes with it. Render the one that I just created analytics. We'll give it a second. We'll save that. Curator will update the preview. Right? So here we go. And now if I just go ahead to my page, to my Curator instance, I render it, refresh, and sure enough, there we have it. Right? So this is just to give you a glimpse of how we can customize front end. Right? There's a whole bunch of things we can do to customize it further. Hopefully, that starts to give you something to think about. Now that gives us power of what we wanted to do. The other half is, okay, we get it. The look and feel is it's awesome. Now let's actually start bringing some analytics content, BI content in it. Right? What I will want to do is I will want to create links here, Currently, three links, each of which will effectively just render the dashboards that I've shown in Tableau in in ThoughtSpot and in Power BI. So this is effectively just a way for us to create a navigation, right, a navigation where the user clicks, and that will render that. So what do I need to do first to be able to have curator speak to this BI tools? Right. First thing we need to do is actually establish a connection. That is we need to get curator read access onto these platforms. This is a one off task is fairly straightforward, but I've done it already for the purposes of this demo. How do you do it? It's very simple. You go to integrations connection. And here you'll see Power BI, ThoughtSpot and Tableau server. What I've done here, as I said, is think of it as just establishing a link for the first time. Curator is now watching these BI tools right so let's just take a look at what that means the case of Tableau server it's pretty straightforward you just give it some name and a slug. You choose what platform, it is curator provides a drop down then depending on the platform you choose, you need to provide some details around. But typically, you will need to provide your URL, the primary side, some credentials, etc. Right. Your administrator of the BI tool can help you with that. And certainly, our team can help you just speed up that process. But trust me, it's just punch pushing a few buttons, inputting a few credentials and job doc. Right. And the same is true for the others. I'm not going to step you through in detail. But just so you see, ThoughtSpot, same story. So again, just choose the platform, choose the URL, a few credentials, and off you go. Right? And the same is true, of course, for Power BI. Again, this is a relatively straightforward process once you've got the right details. Right. So again, and you see here, we've got exactly the application ID, etc. Okay, so that effectively says, Okay, this is my curator instance. And these are each of my BI tools, right? I establish a one off, I do a one off exercise when I establish that connection. Right? That's the first step. That's done. From there, what I can ask you later is, okay, creator, I want you to specifically start now looking at a specific live boards or dashboards within these BI tools. Right? So how do I do that? Well, we've got these sections here, where all what they do is effectively they allow you to configure or to choose what sort of content that you want to pull from each of these platforms. Right. Now, a couple of things to mention when it comes to these pooling data and reading data. First of all, Curator operates on an API basis. So what it does under the hood is just an API goal. Right. Secondly. Curator does not clone does not copy does not store any of these dashboards what curator is doing is effectively reading them right. Content creators your tablet developers your Pavia developers your thoughts for users can continue to create content in the same way they did. Don't need to change anything. Curator is just simply that read, right? So the moment you publish a dashboard on Tableau, if you've configured it correctly, Curator will be able to just pick it up. So creation remains how it was. Created just reads. And thirdly, curator inherits the permissions on those BI tools and the security. That is, if I Roger cannot see dashboard x in Tableau, when I log into curator, curator will not override that. That is, it will continue to not allow me to see that, right, because curator inherits that security. Okay. Now, let's have a look as to how we can ask curator to start now pointing at specific dashboards. So if I go to Tableau, go to dashboards, right here, I've got a couple of dashboards, right? And remember, I'm not creating dashboards. I'm simply asking curator to just start looking into it. So I'll do a new dashboard. Right. And then I have Tableau Server, Tableau side project, and then workbook and dashboard. Now, for those of you that use Tableau, this will sound pretty familiar, right? Because these options right here are effectively the same options that I see up here. Right. So it's exactly the same. So I simply choose the workbook that I want. And then within that workbook, I just simply choose that dashboard. So let's say overview. Right? Then here, that's pretty much done. I could just give these customer sales overview. But again, that does an internal title, and the rest is pretty much good to go. That's it. From now on, curator can start rendering the slash one. Let me just do one little tweak here. I'll explain what does that a bit later. I'll just do miscellaneous. And then here in discovery, I'll just choose featured. Alright. I'll explain what does that after. Let me just go and create that link. Right? So we'll just give it a second. I know if you go, that dashboard is now connected. Right? We don't need to if we want to use this dashboard in multiple pages, that's done. We don't need to do it again. Right? I'll do the same with thoughts, but just so you see how it is it is. So I'll just create a connection to a new live board. Again, I'll just choose, let's say, executive dashboard, right, And show visualization. That's it. And I'll just simply mark featured. Again, I'll explain what does that have. Done. Creator can now start rendering or embedding these live in particular. Okay. And we'll do the same. Let me just show you. And here we have it in all its glory. Right? And then let me now do Power BI. Again, same story. Create a new link. Choose the workspace. Choose the dashboard. Mark featured. Done. Right? So now Curator is pointing to each of these dashboards. Right? So we're good to go. Now let me step back for a second. Roger, why did we establish these connections? Well, because what we want is, in our instance, to have three links up here, three navigation links. And then when I click on any of these, it will effectively take me to that dashboard in particular. Right? So let's go and do that. We've done the heavy lifting. We've pretty much done. How do I create that navigation? Under content, navigation. You notice that I have here just delete that. It doesn't get in the way. I have the main menu right and what I'll do now is I'll just create three menu links, how do I do it again pretty straightforward new menu link. And here, a menu link can effectively point your users to a page to a file to a dashboard to an external or custom URL, etcetera. So it's effectively just a navigation option. In this instance, we'll ask Tableau, excuse me, curator to point to a Power BI dashboard. Right? We'll give this a title called IT spend. Right? And then from there, that's job done. Again, because it's a Power BI dashboard, Curator knows what dashboards I'm pointing to. So it just allows me to select the one that I'm after. I give it a title and job done. Sure enough, we have the first dashboard point. Let's do the same with Tableau. So again, Tableau dashboard. Here, what I'll do is I'll select the customer sales. Remember, that's the one that I connected to earlier. I'll just create that link. And the same for ThoughtSpot. So, again, here, I'll choose ThoughtSpot, Livebot. I'll just choose the livebot in question, executive dashboard, and here we'll just call this executive dashboard. Right. And then I click create. Right? Now I have these three links. I can move them around. I can just matter. I can just move them around and just say I can nest them as well if I want, so it creates drop down. So that's pretty much done. And from here, we've got our navigation up and running. Let's check it out. So if I go to my create instance and I simply refresh, we'll just give it a second. Sure enough, I've got at the top the three sections that I wanted. And when I click on customer sales overview, it will just report me to the customer sales overview dashboard. Again, this, and there you go. You've got Tableau in all its glory. Why do I say knowledge glory? Because this is not static. This is live functionality. Remember the instructions that you had earlier with the dashboards? So here now, sure enough, I can see exactly the same level of insight. I can filter exactly in the same way that I could, etcetera. Right? We natively pulling the functionality from Tableau in this case. Right? Let's try now, say, ThoughtSpot in the executive dashboard. Again, this screen that you see here can obviously be customized. And here we have the executive dashboard on the ThoughtSpot rendering, right, and exactly with the same functionality. I've got right here the filters, right, if I want to, and I've got exactly the same functionality that I would have in ThoughtSpot. Right? This dashboards might be a bit slow, because I'm actually connecting from Sydney in Australia, and some of these are hosted in the US. So there's a bit of lack in that front. But other than that, we should get exactly the same results, exactly the same functionality. And lastly, Power BI, same story. The IT spend analysis dashboard that your IT team for using. They go, I have it there in all its glory. Right? So that just effectively to show you how easy it is for you to just point curator to start rendering these dashboards. Right? Now there's a whole lot a whole bunch we could do. And there's a whole a whole lot functionality that curator can provide. For example, if I go back to the case of Tableau, you will notice and some of the some of you have mentioned that you use Tableau. Some of you might find that this functionality sounds familiar, the download functionality that is when you want to download a dashboard. Right. So if I go to Tableau, this would be effectively an equivalent. Right. Now, that what what curator is doing here is effectively in editing that functionality will leverage all the existing functionality of Tableau, so I can go ahead and download it, but I can configure the front end, I can give it a better user experience. For my users right so on the one side we're effectively enhancing the existing functionality of Tableau or other BI tools right On the flip side, we also include additional features that is we add additional functionality that you can use to interact with your dashboards. For example, a very popular one is what we call the report builder. In two minutes, you've got a meeting and you need to present a few screenshots of your dashboards. So what I do is I just apply the right filters. Select the right region, for example. And once this is rendered, what I can do is I can just use report builder. Right. And effectively take a snapshot of that. Right? I take a snapshot. If I configure this in the back end, I can add comments to it. And then from there, what I can do is I can export that image as a PDF or as a PowerPoint. Right? So now then it's ready to go. Right. This is in particular very exciting. If you feed curator your template, you can use a specific template of, say, a PowerPoint template, for example, you can feed that to curator and then do that screenshotting and report preparation in a few seconds and having a very good product from a look and feel perspective. Right. Now, this shows you should give you hopefully some understanding of the functionality that we can do. But as Deb mentioned earlier, Curator is not only BI content, you can also add other type of content. So for example, let's add a new menu link, right? This instance, instead of pointing to a dashboard, what we'll do is we'll point to a specific file, Right? So if I find here the option of file, right, what I can do is I can effectively upload a file. This is the file that I uploaded, a PDF. Right? I've already done that. Simply choose it from the drop down, and then I go ahead and click create. Now what's this file? Okay, here's a scenario that many of our clients face, which is that when they start driving traffic onto this instance, their BI experts and developers start, obviously, accessing that site. Right? So what it might be useful, for example, is across all your BI tools, you want to generate a set of style guides, that is instructions that from a branding perspective, your developers, whether it's VaRBI, Tableau, etc, need to follow to have that branding consistency. So with that example excuse me. With that, for example, I'll just go ahead and refresh here, and we should have the file. Just a second. So here is the style guide. If I click on it, notice that now I have the style guide for my developers to follow, right, across all platforms. Right? So it's just an example of some static content you can also create. Right? That's pretty much what I wanted to cover. That doesn't mean that that's what Curator can do. There's a whole bunch of functionality that we will need several hours for me to step you through what Curator can do. But fear not, because we do have examples of that up and running. If you go to the Curator side, Curator Interbox, you'll find in this page, you'll find pretty much everything you'll find documentation examples, features that you can include, etc. Right. But one area in particular that will be relevant is that the sites, the demo sites that we have up and running. And I would strongly recommend for you to go through it so you can effectively familiarise yourself with Curator a bit more. And also, if you decide to run a trial, request a trial for Curator, you can see what examples of what can be done. So in all of these, you'll find different functionality, examples off the top of my head, right, right back functionality, integrating forms, and the list goes on. Right. So there's a whole bunch of additional functionality that you can see, and don't take my word for it, just simply check those demos to for you to see it in all its glory. Right. Now, from from a front end perspective, there's obviously a bit more that we could do. Let me just show you now briefly how we could add, for example, another element in our page. This instance, instead of just adding a. Instead of just adding an image, what we'll do is we'll add an interactive element. So I'll just go back to the page that I had. And right underneath the image, I'm going to add another element. So I just click. And I'll just select tiles. Now, what is tiles? Tiles is effectively a way for you to personalize a list of dashboards across platforms that your users can see. So imagine you've got dashboards in Power BI, Tableau and ThoughtSpot. And for some reason, you want to call out that certain dashboards have been released, for example, right across all platforms. So what do you styles? And from here, that's the section that is rendering. See how I get one, I get three tiles, can customize that. Right. Now remember earlier when I mentioned that when creating the dashboard, I was clicking on that toggle to be featured. That's what I meant earlier. Featured in this instance was just like attack. Right? And so what I'm telling curator is display in this list, those that have intact with feature. But I can also do something like most favorite most visited recently viewed etc. See how you can start making the in your pages to be much more interactive across platforms. Let's just try this out. I'm going to save it. And now, just so you see a bit how it works. We'll just have it down here, obviously, would customize that we could change the thumbnail, we can make it rounded, etc. Right. But just so you can start getting a sense of the different options that you have in terms of in terms of customizing. And also, you'll notice that I have here a search functionality, right? This search applies to all dashboards that I have. So what I did is the customer sales overview dashboard. I targeted it with the sales doc. Now what I could do is your users from this search can just go ahead and type sales. And they could just go straight onto the dashboard that thereafter. No more clicking through is that Power BI, ThoughtSpot, etc. It's all centralized from a given, from a central search function. That's pretty much what I wanted to cover. Beth, I'll pass it back to you. Hopefully, gives you some foundation on the possibilities of Curator. And of course, if you have questions, just fire away. Perfect. Thank you so much, Roger. We had some questions flying in through that as well, so thank you so much for your interest and involvement, guys. I particularly loved how there tended to be a question about the thing we were going to show next, which is always a great segue, so thank you for that. So some of the questions that were coming in, I think, were the use cases we see a lot. You want to show those three reports right next to each other, for example, and Roger showed you that. One big call out there is that you can set up a single page and lock those individual dashboards to that page. So you can, for example, have an operations page which contains all of the different dashboards that you want operations to see. So, some other things that were noted as well. There was a question in there around can you have subheadings? Yes, you definitely can. When Roger was creating headings, can simply move individual headings around. You can one hundred percent have an operations heading and then a subheading that has a particular thing flagged, for example. So, if you do have additional questions, please throw them into the Q and A now. Can see someone popping some stuff in and I'll ask Roger to have a look at those while I speak. If you do have additional questions, please pop those in. If you have questions after this session though, or if you want to investigate more, what are your options? I've got some links on the page for you. One of them is that you can learn more about Curator and check out live demos at the site that Roger was taking you through. That's curator. Interworks dot com. You're also more than welcome to reach out to either of us direct. Want to have a chat? I can see some existing clients in the participants list as well, so if you know us feel free to reach out. If you don't know us, please also feel free to reach out. You can also reach out to our sales team. One quick call out for me. I wanted to let you know about the common use cases I see. Curator is one of my favourite tools within IntoWorks because it solves such a known business problem, and it just does it so well. It's also, frankly, just a lot of fun. I spend a lot of my time building things in Curator because I enjoy it. I can have something that looks and feels the way I want with so much control over the user experience. So what are the most common use cases? One of them is that you want to curate what your users see, so only show production items and not allow your users to wander off into the sandbox. You might use Curator as your distribution method for final click. Another one is that you want to show different things to different people across the organisation. Roger mentioned that it inherits security from Tableau or the Origin tools. That's a really important call out. Inheriting security means that you can show finance people finance stuff and HR people HR stuff. You can also use those user groups to control the look and feel of the Curator instance, so that finance logs in and sees something that, for example, is bright pink, has finance y images and finance look and feel and finance dashboards, and that HR logs in and sees something that's yellow and has all of their stuff as well. So it can be customised to give a different look and feel to a different person. Another one is that you might want to build a one stop shop for analytics within your organisation. You might want a hub a hub that brings together content from across these three different sources, for example but that also contains dashboards, data dictionaries, documentation, contact points within your organisation. Or maybe you have clients yourself and you want each of them to log in and see something that looks and feels like them. These are the common reasons that I see people use Curator. A lot of the time, for any of these use cases, you want to present different items from different BI tools alongside each other in a very coherent way. You want it to be seamless, and you want the users to not even know that they're seeing things from different tools. So, hopefully, this was helpful to you. I'm going to chuck a poll back up on the screen. It asks you about some next steps. So, if you are interested in hearing a little bit more about Curator, or maybe you think 'I must know more about this and how it could be relevant for my organisation', please let us know in that poll and that will give us some next steps for you as well. And while you're filling in that poll, I'm going to have a look at the questions and things that have just popped into the chat. Beth, I can take a question that was asked by Bruno. I was just typing. Perfect. Thanks for that. I'll keep So here's the that If three reports are in different BI tools because that is in different databases, whether we would suggest to centralize the three databases in just a single source of truth or trust, where we can join the three databases in the same tool. So that's more a decision that has is not necessarily to be dictated by curator. So if you have these databases in the in, and you're building reports on it, using different BI tools, you can effectively connect these different BI tools to curator and effectively have them in their current form. Right. If you want instead, though, to effectively move all of those reports, so to speak, onto a single tool, and then embed that into curator, that's also absolutely fine. There's obviously considerations when it comes to whether you decide to join or centralise that data. And we can certainly discuss that. But it's not something that effectively curator would limit you on or not. So as I said, if you want to definitely embed the three reports in the current form, because you think that the BI tool of choice helps you get the answers that you want, then that's totally fine as well. It's more of a decision in terms of data architecture. And what sort of tool do you think is best suited to answer the questions that you're after. But again, this will be a conversation on on analytics and databases or architecture more than the limitations or the powers that create unlocks. So Bruno, hope that answers your question. Feel free to just give us a shout if if that doesn't. Perfect. Thanks, Roger. I can take the next one. So there's a couple of questions in here. So as of now, API is available to curate from Tableau, Power BI and Thoughtbot. Yes. That's not to say you can't bring in other things. You can embed other things, for example, in an iframe, but you won't get the level of native integration of options like filters that you've seen just now. It's around the level of interactivity the user has with something. But you can definitely embed other things. You can add dashboards and links through things like static images that Roger showed you, and you can also add things into an iframe direct. There's a question there around the speed and whether it will be as fast as what we've just shown you. Hopefully, but that depends on your environment. If your Tableau server doesn't run quickly, it won't run any faster in Curator, so that's a speed conversation. We can definitely help you if you are having speed issues in general. And then there's a question around security. Curator does definitely not copy and store your private data. Curator pushes authentication to the source system that's very deliberate. So what it is doing is that it is contacting the source system and saying 'can this person see this thing?' and then it is surfacing that thing to that person. Now, that said, security is not my domain, so if you are interested in Curator and you do have security questions, we have a whole team of people whose job it is to answer those and to step through how that might work for your organisation. So, we can definitely put you in touch with someone who knows a lot more about that than me. Now, if there are any further questions, now is your chance. Otherwise, I see a few of you have chucked answers into the poll around a free trial of Curator and a personalised demo. We'll reach out and have a chat with you about those. If you haven't filled in the poll and you do want to have another conversation, please do so now. That gives us the info that we should reach out. Alright, otherwise, that's it. Thank you so much for your time today, guys. I had a fantastic time with you and I really enjoyed the demo from Roger. Hopefully, this was as useful and interesting for you as it was for us. If you do want to reach out and have a chat after today, please do so. You can also learn more about what we do at our blog and if you think this is so cool and you must work on it with us, please also reach out through that link there on your screen. Thank you everyone, thank you so much for your time today. I hope you have an excellent rest of your day. Cheers.