Projects organise your notebooks around a common dataset and provide a space where multiple users can collaborate together.
Every project has a parent database connection which defines the range of data that can be used within the project.
A list of notebooks.
A group of users who can access the project with different levels of permissions.
A list of tables (these can be all or a sub-set of the tables available from the parent database connection).
Creating a project
There are four steps to creating a new project:
1. Choose a parent database connection
Projects have a parent database connection from which the data they can access comes from. First choose the database connection you want to use for the project and click create a project from the data base connection's home page.
Remember: You must be a workspace admin to create a new project.
2. Name the project and give it a description
Give the project a distinct name and description. This could be based around the dataset which the project could contain e.g. "Product telemetry" or "Marketing data" or the type of reports it will contain e.g. "Quarterly performance reports".
3. Invite members
You can invite users to your project and assign them a specific project role. Read more on managing project access below.
4. Define table access
By default, a project contains all the tables available from its parent database connection, but this list can be filtered to a subset of tables to restrict table access to the project's members. Read more on managing a project's data below.
The project home page shows all the notebooks stored within the project.
The project home page shows all the notebooks within the project.
To see available options for each notebook, right-click on the notebook, or click the notebook menu icon.
The notebook option menu.
The 'Access' column describes the three main visibility states for a notebook:
Unpublished - this notebook is editable.
Published - this notebook is not editable. It can only be changed by unpublishing it or forking and merging it.
Public - this is a published notebook which can be shared with anyone who has the notebook link, even if they are not members of the project or workspace.
You may pin any number of notebooks to a project by clicking the Pin to project option in the notebook option menu. When a notebook is pinned it always appears above the notebook list.
Un-pin a notebook by right-clicking on the pinned notebook and select 'Remove from pinned'. If a notebook is moved to another project, it will not automatically be pinned in that project.
Use pinned notebooks to highlight the main results you wish to emphasise in a project.
Only project admins can change the data accessible by a project. The list of tables within the project can be seen and edited from the "Manage data" button in the main project home page.
By default, a project has access to all of the tables available from its parent database connection. In this case, Count does not perform any checks on the tables being queried from notebooks within that project.
If the table list is filtered to include only a subset of the tables, Count will prevent queries from executing if they attempt to access a table outside of the subset.
By default a project contains all tables from a database connection, but this list can be restricted to a subset of tables.
How notebooks access data
Count does not persist query data on its servers. This means that every time that a user opens a notebook, Count sends the notebook queries to your database again and returns the results directly to the user.
Managing project access
The list of project members can be accessed from the "Manage access" button in the main project home page.
User access and permissions can be changed by project admins or workspace owners. All other project members can just see the list.
There are two ways to share a project with users.
Giving workspace access
Inviting users via email
1. Giving workspace access
Project admins are able to set a workspace-wide permission to a project from the members list in the project. Whilst this permission is active the project will be accessible to every workspace Member and Admin (not Guests).
There are two options for workspace-wide access:
View access (everyone in the workspace becomes a Project Viewer)
Edit access (everyone in the workspace becomes a Project Editor)
Assigning a workspace-wide Editor role may increase your subscription costs. Check the billable status of workspace members in the workspace settings.
You can set workspace-wide access to a project from within the project's members table.
Individual users (both Guests, Members and Admins) can still be specifically invited to the project. Their project role is determined by the highest role provided by their specific permission or the workspace-wide one.
2. Inviting users via email
Whether a new user can be invited to a project depends on the role of the user sending the invitation and what the project and workspace settings are.
Options for Workspace Admins and Owners
Workspace admins and owners can invite users to a project as either Admins (if the user is a Workspace Admin), Editors or Viewers.
If the workspace doesn't allow Guests then they can only invite current workspace users to the project. If guests are allowed then they can invite any user to the project as a Viewer.
If the user being invited has an email approved by the workspace domain whitelist then this user can be invited as either an editor or a viewer and is automatically added as a workspace Member (they cannot be added as a guest).
Options for Workspace Members & Guests
Workspace members (who are both editors or viewers) and Guests can invite users to the project as Viewers, only if the Allow Sharing option is enabled in the project settings. These users could be new users or current members of the workspace. New users could become either guests or workspace members depending on the workspace domain whitelist settings.