You may be new to Count or familiar with using count with your team. Whichever stage you're at on your Count journey, understanding how to structure your workspace allows you to confidently bring in new teams, scale usage, and have the whole business working together. This demo will walk you through this highlighting a number of key features and strategies you can implement to grow your workspace effectively. A key place to begin scaling your workspace whilst keeping it organized is to use projects. We can think of projects like folders. When creating projects, we can use naming hierarchies to organize as we scale. You can create projects for individual work, department and initiative work, and then company wide. Using name hierarchies will group canvases methodically, meaning less time spent searching and more time spent developing in the right space. Individual projects are areas for one user. Creating this type of project gives users space to experiment and play around with canvases without clogging up group projects. We call this our sandbox. The next hierarchy could be groups of people who want to create canvases together, and they will need access to the same datasets. This could be at department, for example sales, or initiative level, for example campaign for marketing. This provides each group with a dedicated space to collaborate and build together, creating canvases which will aid a common goal. We can also add folders within projects. Adding another layer of organization and saving time navigating to the right place. We can add members to the project and use project level permissions to give each user access to the projects they need to see without cluttering up their home page with every project. If you're on the enterprise and scale package, you could also create groups. Groups are useful to assign the same permission to a common group of people, reducing time spent setting individual permissions. If you're not on these plans, you can add teams individually. If you want to find out more, have a look at our knowledge base on permissions. An extra tip here is to create a data connection for each group. For example, you could create a sales data connection, providing them access only to the data they require. This would arm the sales team with a suite of the right datasets, making the data more accessible and speeding up time to analysis. Finally, company wide. Now this is a set of published reports. These canvases are purpose built live and in action. This space benefits from being used only for company wide final presentations, keeping canvases here pointed for nest and the space clean. You can use permissions to manage access for best practice. The default for new projects for members of demo workspace is no access. However, we want everyone in the workspace to be able to at least view the canvases, so we've changed this to viewer. You'll notice as well, once everyone in the group has permissions, this symbol will change to a hash from a lock. Next, we'll touch on using tags. Tags allow users to organize their canvas. Here we have used canvas status to easily convey the state of production. This ensures the right canvases are being used for editing, reporting, and old campuses are archived and moved out of production so old information is not being circulated. Here we've created some tags. Our tags are in progress, needs review, live, and archived. But these are also customizable so you can tailor them to your organization. Users can also click on tags to review all canvases which they have access to with those tags. This is helpful for housekeeping and wider accessibility. So let's have a look at an example for using tags for best practice. Here I've created a metric map for the sales team. It's been reviewed, and it's ready to go live. So I'm gonna move it to the sales team folder, and then I'm gonna change the tag to live and update the name. Enforcing these best practices now means the canvas is in the right place for the right people and users know when it's ready to use. Let's look at best practice on how to make changes to a live canvas. For example, we want to update our OKR metric tree, but we don't want any downtime on our company wide canvas. So we're gonna duplicate it, move it to sandbox, and change the tag. Once we finish the edits and the canvas is ready to go live, we can use the merge functionality to merge it back into the original. This also ensures any links to this report are still relevant and active. Using Duplicate and Merge also builds trust with stakeholders who can be assured their necessary reports are never broken during updates. Using Duplicate and Merge will also retain version history. This means it can be rolled back to the pre merged version if required. With version control analysts and editors are motivated to innovate and develop canvases without worrying about breaking something. If you want to adjust permissions you can also do it here in the share tab at a canvas level. Here you can see the default permissions mirror the project permissions, so we'll leave it this way. Unless we want to make any changes such as adding viewers from outside the organisation, and we can add them individually. You could also make use of present functionality, which will help you in the report on essential information whilst minimizing any noise from the canvas, including moving around to find your key point. Here, we can also toggle which frames you want to show. So we probably don't wanna show data analysis to our stakeholders, so we'll toggle that off. You can also set this report view by default, which means that anyone that opens this report will see this view by default. Another way to scale effectively is to make use of the count catalog and create a set of predefined metrics. Using predefined metrics means that logic is baked in so anyone can use it and feel confident with data, not just analysts, but everyone across the business. This breaks down data silos and means the organization can base decisions off consistent and trusted numbers. Another best practice is to encourage users to add in creator details to canvases. This could be name, role, and date of edits. Doing this will build trust across departments. People can rely on reports because ownership is visible. Once you're done editing, you can lock your canvas to prevent any accidental changes whilst letting members have independent sessions. So the OKR canvas is important. We use it weekly. So we can pin this project, which makes it appear at the top of the project for company KPI. And this is useful when we want to surface the most important or frequently accessed canvases for fast access, especially when there's lots of canvases in one space. Another tip to scale effectively is to build templates. Templates empower users to create and develop whilst maintaining consistency across a number of elements including aesthetic, branding, and content. One type of template we suggest building is a best practice template. In here, we've added in an overview pane, and this is perfect for summarising Canvas information. You could decide what is needed here but we've included a title, overview, purpose, how to use, methodology, quick link to frames, control cells including filters, and your Canvas log. Adding these elements in builds trust and accountability with other users who can immediately understand the purpose and methods used and who to contact for questions. You could also create frames to guide users through building a structured, logical canvas. You could also include a set of best practices as a checklist for users to review before publishing their canvases. Maybe you'd also want to brand your canvases. You could add a company logo for professional external presentations. You could also add share styles where you can define colors so people can use them. Doing this will give users access to brand their canvas with company colors quickly and ensure all text, visuals and other aesthetics are consistently themed. If you're on the enterprise or scale plan you can then publish these styles to Workspace. Otherwise, you can save them to templates for team access. Once you're done with your best practice canvas, you can save canvas as a template. You could also make it featured for one click access. Users can click into this template, add a name, and then easily start building with all best practices preloaded. You could also create a set of standard library templates with reusable logic, layouts, and metric cards for quick incorporation when needed. Using templates mean users spend time on content development rather than setup, while businesses maintain design consistency and quality. Finally, if you're on certain funds, you'll have access to telemetry data to monitor workspace usage and set alerts for workspace management. Whilst your workspace scales, telemetry data will help identify how to optimize activity to ensure workspaces are being used efficiently. Follow these simple practices to create an organized workspace, utilizing projects and features to create a workspace which can scale as you scale.