Hi. This is Mitra from Count. We're delighted you're here, and we're excited to see what you're going to achieve with Count. In this video, I'll introduce to you the Count workspace and how to set this up before you start exploring further. If your organization doesn't have account workspace yet, you can create a free one on our website. You can come to the pricing page and just click to start a fourteen day trial. I'm going to show you around our demo workspace, which might look a little busier than yours at the moment. So what is a workspace? It contains data, members, projects, and canvases, and typically each organization only has one workspace. As a workspace owner, you can create and manage the workspace and its billing settings, and admins alongside owners can also invite other members and guests and assign their project roles. One very useful setting that I would recommend looking at straight away in your settings menu on the left hand side is our domain whitelisting. So here you can see that we have added our various email domains. You can do this just by clicking add domain and adding this. This will mean that users with an email address at these domains will automatically see an invitation to your workspace when they first create an account here. Whitelisted users join the workspace by default as a member. After they've joined, you can then upgrade the level of a user's workspace role. So for example, for your analysts or your engineers and to do that, you'll want to update their roles in the members tab. So here we can see a list of members in my workspace and the roles that they have. To change any, just simply use the dropdown and select the role that you would like. You can also remove members this way. There's a handy list at the right hand side with an explanation of each role and there's also a link to our docs if you would like further information about these. If you're undertaking a trial or a POC period with count, we would recommend setting all your evaluators to owners. This means that they'll have access to all canvases and projects, and this can be really useful as you're getting started so you can access everyone's work. Then after the POC, you could look to change this. Next, I will go back to the left hand panel and we will come down and look through these sections. So first of all, we have one called connections. This details any database connections that you have made with account. When you're ready to connect a database, you can just click connect database and then select the database type that you would like to connect. On each page, there is information specific to that database type that will help you to connect and put the right settings in. And on every page, there are also some useful links about our documentation relating to that database type, but also information about security and count if you need to reference that. If you aren't quite ready to connect your database you can then still connect data using our demo database instead. You simply select it and now you will see that it's appearing within our connections. You will notice that it's saying that it's not currently used for any projects or catalogues, and I'll explain what that means as we go through this menu on the left hand side. So we've added our database connection and then underneath, we see catalogues. You can use Count Metrics, our semantic layer, to define metric catalogues and when you do these appear here as further data sources. Next, I'll come on to projects. Once your workspace is set up you'll want to create projects. Projects house all your canvases, so you'll want to consider how to structure them effectively. We advise considering three types of project. Consider giving individual analysts their own sandboxes. This gives everyone the freedom to do exploratory work in that one space without confusing others. The work can then be moved to a shared project when it's ready to share. The next type we would recommend is projects by department. These help organize canvases by team and make it easier to find related canvases and finally consider company wide projects. So this could be used to keep training materials or to house key organizational canvases. Within each project you can then add data and people to it so essentially you decide which data sources are available within each project and who can access each project. I'm going to create a new project by clicking here. I will give it a name. Description is optional and I'll click next. And now it's prompting me to expose some data to it. We can see our data connections and our catalog. So as I mentioned, these are all considered data sources that can be exposed to a particular project. We can click multiple. I'm going to include the demo connection, which I added and a catalog, and I'll click next. Now we can decide which project members have access to this project. Using the drop down I can scroll or I can search. I'm going to add Holly. You can see that Holly is an explorer in our workspace but we can also define what Tully's role is in the project. You'll notice that I am unable to select anything above the level of explorer. So when we're defining a project role, it's only up to the level that you have been assigned in the workplace. To show you another example of this, we have a guest and you'll see here that I am restricted at only allowing them to be a Canvas viewer or a Report Only viewer. I can click update. Here's our project. It's empty because it doesn't have any canvases in it but it does have some members and some data connections. You can always come back and adjust these. So if I click manage access under members, you will see that we can add members here or we can edit the ones that we have already assigned. There are different levels that you can assign permission. You can assign permission at a workspace level, which is represented up here by this line. So we would choose this if we wanted to make this project open to everyone across the workspace. If we want more granular access in that and we only want to give access to certain teams or people, we would then use project level permissions. And that's exactly what we've done here already. And finally, we can also set permissions at a Canvas level. Our recommendation is, where possible, to rely on project level permissions. They are easier to keep track of, and it means that when you make changes, they are reflected in all canvases within the project rather than having individual canvases with different settings. I can click to go back into my project, and just as I did with members, I can click to manage data if I wanted to make any changes here. So now that we're set up with our project, I'll show you what adding a canvas within a project looks like. I simply go to new canvas. You will see that this new canvas is within my project and I'm going to add a title and then I'll click back and see what that looks like. Here we are still within our project, but now instead of telling me it's empty, we can see my canvas. And there's a few handy settings to be aware of. If I click on the three dots, you'll see some useful settings, and one of them is pinned to project. What this will do is it has pinned it to the top of my project view. I can pin multiple projects here. It's a really good idea to be able to do that if you want to prioritize key canvases that you're going to use over and over again and that you can select from here rather than going through your list. The last thing that I will show you is you will remember when we added our demo connection data. When we clicked on this, it told me that it was not associated with any projects or catalogs. But now if we come to it, I can see that it is connected to the sales team. So this can be a really handy view if you just need to keep track of which projects have access to which data sources. You can also use the drop down here if you then want to add more connections to different projects. I hope that was a useful introduction to the count workspace and that you feel more confident in how to set this up. Thank you.