Introduction

Once you have published your notebook, you'll want to make sure you've shared it with the right people and make sure they have the desired permissions on that notebook. There are few different sharing options depending on your situation; this article will detail each of them so you can choose the one that fits your needs.

Sharing with the Team

Perhaps the most common way people tend to share notebooks is with their team. Each member of the team will need to be a Member or Owner of the workspace, and either an Admin, Editor, or Viewer of the project.

This ensures they can at least view all published notebooks in the project. Viewers can see:

  • Notebook text
  • Unhidden cells & parts of cells
  • Images

But they cannot see:

  • Hidden cells or parts of cells
  • Any of the project data

Editing The Notebook

If you want members of the team to be able to tweak the notebook, or fork it to find their own insights, then they will need to have Editor or Admin permissions in the project. This will allow them to both edit the published notebooks, and create their own.

Sharing Outside the Team

Often we have to share insights with people outside of our organization. There are 2 different approaches to this in Count.

Option 1: URL Sharing

Best for occasionally sharing notebooks.

If you are only occasionally sharing a small number of notebooks with those outside of your organization, you can choose to make your notebook visible to anyone with the hashed link. The notebook will appear as a view-only notebook and the guest will have no ability to see the underlying data nor any hidden elements in the notebook.

To enable (and disable) this feature on any published notebook, click the Share button and use the Share on the web toggle. Then you can copy and share the URL.

Option 2: Project-Based Approach

Best for frequently sharing notebooks.

Another option is to invite people outside of your organization into your Count workspace and give them access to a single project. Then you can make sure the data in that project is always filtered for data they can see (e.g. their data).

You can also set additional permissions--so some users could be editors while others can be viewers.

The advantage here is that if you have several notebooks you want to share, you have a common and single location to house them. You can also take advantage of views to make sure that if they do have edit access, they are only using data they should be able to query.

If you have any other questions or want to know more about how to share notebooks across organizations, reach out to us to schedule a session.

Did this answer your question?