# Suggestion forks

**URL:** <https://talk.observablehq.com/t/suggestion-forks/3744>\
**Category:** Help\
**Created:** [August 21, 2020, 1:25am UTC](https://talk.observablehq.com/t/suggestion-forks/3744 "2020-08-21T01:25:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcmcclur](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mcmcclur/32/2364_2.png) [@mcmcclur](https://talk.observablehq.com/u/mcmcclur)\
**Post date:** [August 21, 2020, 1:25am UTC](https://talk.observablehq.com/t/suggestion-forks/3744/1 "2020-08-21T01:25:14Z")

</div>

Once you start editing another user’s notebook, the option to create a _Suggestion_ appears under the three dot “ellipsis” menu. If you do so, a shared fork is automatically created.

_What becomes of that fork?_ In particular, if I grab embed code from that fork, can I expect that it will continue to run reliably, as I do for my own shared notebooks?

I doubt that it matters, but here is the specific fork that I’m thinking of doing this for:

> **[Binomial Distribution](https://observablehq.com/d/813b0999cb50639b)**
>
> An Observable notebook by Mark McClure.

---

<div class="post-metadata">

**Author:** ![bgchen](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/bgchen/32/784_2.png) [@bgchen](https://talk.observablehq.com/u/bgchen)\
**Post date:** [August 21, 2020, 1:38am UTC](https://talk.observablehq.com/t/suggestion-forks/3744/2 "2020-08-21T01:38:09Z")

</div>

My understanding is that shared forks created via suggestions behave exactly like any other shared notebook with regard to embedding, importing, etc.

---

<div class="post-metadata">

**Author:** ![aaronkyle](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/aaronkyle/32/8106_2.png) [@aaronkyle](https://talk.observablehq.com/u/aaronkyle)\
**Post date:** [August 21, 2020, 1:41am UTC](https://talk.observablehq.com/t/suggestion-forks/3744/3 "2020-08-21T01:41:21Z")

</div>

Also possibly important: suggesting automatically triggers a change in your forked notebook from private to shared. (Your post implies this but just to be clear)

As @bgchen noted, my understanding is that the fork is like any other shared notebook. The fact it is a fork is irrelevant. It will work as if you created it from scratch and then shared.