2. Create and organise your projects
Last updated
Last updated
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.
Here are three aspects to consider:
If you've connected your database, you'll see an option to select which database connection you want associated with each project. All canvases within a project will have access to all databases connected to that project.
Read more about database connections here.
While you may want to have fewer projects when you initially start, keep these naming conventions in mind as you scale your usage in Count.
Per-analyst projects:
Name examples: "Harriet's Playground" or "Harriet's Sandbox"
Purpose: Start exploratory work without confusing others. Move it to a shared project when ready to share.
Company-wide projects:
Purpose: For training and MVP canvases.
Example: "Company Metric Tree"
Department/team projects:
Name examples: "[Team Name] Project Name"
Purpose: Helps organize projects by team, making it easy to find related projects.
Here's an example of this structure in action:
Permissions can be set at both the project and canvas levels, offering a lot of flexibility and control.
To update your project-level permissions:
Select the project
Click Manage access in the right-hand side menu
Set the workspace and/or individual permissions
Only projects a user has access to are visible in the sidebar (except for owners, who have access to all projects/canvases).
Read more about project-level roles and permissions here.
Read more about canvas-level permissions here.