# Sharing

## Introduction to sharing and forking notebooks

Gradient Notebooks makes it easy to collaborate with teammates. Notebooks are shared at the team level and can take advantage of [shared persistent storage](/gradient/explore-train-deploy/notebooks/file-organization.md) at the team level. Notebooks can also be made public or private. 

## How to share a notebook

The `Share` button in the notebook IDE provides a quick and easy way to generate a shareable link for a notebook.

![Use the Share button in the notebook IDE to generate a unique link for a notebook.](/files/tTiTH2C5v9rVUvSBpPQR)

If public access is granted, anyone with the link will be able to view the contents of the notebook.

## How to fork a notebook

Forking is useful to clone a public notebook into our workspace or to duplicate a notebook that is already in our workspace. Forking a notebook creates a new history for the notebook.

Fork a notebook from within the notebook IDE by using the hamburger menu in the top left of the IDE:

![Notebooks can be forked using the menu within the notebook IDE.](/files/49NFNdvMsBKAKynBjZtz)

Fork a notebook from the Gradient Notebooks console using the 3-dot menu:

![Notebooks may also be forked using the menu in the Gradient Notebooks console.](/files/YhvElhjRIX2nM7AUQRjS)

The files copied to the notebook are those listed in the [notebook include file](https://github.com/Paperspace/Docs/tree/9f5869e1aef4b75067075530e65c9764279782bf/notebook-include.md), which is explained in the next section.

## How to configure a notebook for forking

When a notebook is offline, some files are copied to the [storage provider](/gradient/data/data-overview/private-datasets-repository/storage-providers.md) to enable offline viewing. By default, the list of files includes `.ipynb` and `.md` files. Additionally, if the notebook was instantiated using a git repo as a workspace, Gradient will upload any files that are tracked by git. 

It's possible to specify exactly which files should be available offline by providing a `.notebookinclude` file in the `/notebooks` [directory](/gradient/explore-train-deploy/notebooks/file-organization.md). 

The file is similar to syntax found in a [`.gitignore`](https://git-scm.com/docs/gitignore) file, however in this case we will be *including* files instead of ignoring them. Negative patterns are supported. 

The default `.notebookinclude` file looks like this:

```
*.md
*.ipynb

# and all of the files from `git ls-files`
```

In the following example, we tell gradient to upload all `.png` files to the storage provider while skipping dataset files:

```
*.png # include all png files
!datasets/**/*.png # exclude the ones in my datasets
```

Now we will use a negative example to exclude `.md` files:

```
!*.md
```

## Reference for operations within .notebookinclude file

| Item       | Description                                        |
| ---------- | -------------------------------------------------- |
| `#`        | Comments out the line                              |
| `!`        | Negates the pattern                                |
| `/`        | Directory separator                                |
| `\*`       | Wildcard                                           |
| `?`        | Wildcard exactly one character                     |
| `[a-zA-Z]` | Range notation to match a character in the range   |
| `**/`      | Match in all directories                           |
| `/**`      | Match all files within a directory                 |
| `a\*\*/b`  | Match zero or more directories between `a` and `b` |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://paperspace.gitbook.io/gradient/explore-train-deploy/notebooks/share-a-notebook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.