Skip to content
Gilgamesh Documentation
Open Gilgamesh

Guide › Share

Sent versions and comments

A sent version freezes a version of the screenplay for readers: a producer, a script doctor, the crew. Each recipient receives their link, or the version arrives in their account; they read and comment. What you write afterwards does not change what they read.

Everything happens in Share, Sent tab.

The overview

At the top of Share, Documents and Sent. Sent shows what is waiting for the next version (the readers' notes with no answer, the answers ready to go), then each sent version, from the most recent to the oldest: where each reader stands (reading, reading received), their role, what they answered to your questions and their letters. Each sent version also manages its recipients there ("Edit recipients"), their access (revoke, create a link) and its deletion ("Delete the version"). The most recent version is unfolded, the others folded: the chevron opens them, as it does the list of recipients.

Prepare the next version

Sent › "Prepare" opens Prepare V4, the package of the next version, in three steps:

  1. The readers' notes waiting for an answer, sorted by scene, with what the rhythm says about them ("the readers disagree here", "several readers note a slow patch"): choose what happens to them and answer.
  2. Your questions to the readers.
  3. Your letter and the sending: the recipients, the letter, the title, the attached notes. What goes out sums up the package before "Send V4": the screenplay frozen as it is, your letter, your questions, your ready answers, the attached notes, the recipients and their role; nothing else (neither the Prep pages, nor what you write afterwards). Everything goes together; the links are shown once, to copy.

The package is saved as you write it, like the rest of the project: leave the page and you find it as it was. It starts empty again once the version has gone.

Create a sent version

  1. Share › Sent › "Prepare".
  2. The recipients, each one by Link (a name), by Email (the link goes to their address) or by their Gilgamesh Account (their username or their account's email address, checked straight away: green tick if it exists, red field otherwise). Each one has a role: Advisor or Production (the producer reads and annotates like an advisor); it no longer changes once the version has gone. Readers of previous sent versions are offered as chips: one touch brings them back, with their last role.
  3. The letter: a few words that open the version for each reader, before the screenplay (what has changed, what you expect from their reading). It goes with the version and can no longer be edited.
  4. Your questions to the readers, optional ("Does Paul move you?"): each one can target a scene. Each reader answers in their letter; in the sent version, the answers are shown side by side, under each question, and each letter received can be read in full ("letter received" on the recipient's row; an email lets you know).
  5. A title, optional: the version is numbered automatically (V1, V2…); a title is added to it ("V3: After the producer's reading").
  6. The attached notes: tick the notes (Notes page) that go with the screenplay; none is ticked by default.
  7. "Send V4": everything goes at once. Accounts find the version in their Readings; the links are shown, to copy.

Each recipient by link has their own link, shown when it is created. Copy it and pass it on to them by the means of your choice: the link is your responsibility. Copy it straight away: it will not be shown again. A recipient by Email receives theirs at their address, from Gilgamesh's address, with nothing from the project; you do not see it. Five sends by email at most each day.

  • The list shows whether each link has been opened, and when.
  • "Revoke access": the recipient can no longer read the version, and what they had not yet sent is lost; it is final. What they already sent you stays in the project. To keep working together, keep their access instead and send them the next version.

A link is personal: it must not be passed around. The PDF a reader prints carries their name as a watermark.

Recipients by account

If your reader has a Gilgamesh account, choose Account and type their username or their account's email address (you then only see the address, never their username): the version arrives directly in their Received, with no link to pass on. To add someone to a version already created: open the version › "Edit" › "+ Recipient".

Attempts with no match are counted: after several usernames not found in a row, a warning is shown; a few more and sharing locks for an hour. An account that searches for usernames one after another is suspended. Revoking an account's access removes the version from its Received.

Comments

Comments are anchored to the text and follow the rewrites.

  • Comment: select a passage, then "Comment". In Share as in Write.
  • What goes out, and when: a reader sends you their reading in one go (notes, answers, letter); you see nothing of their drafts. On your side, your answers and what happens to their notes go out with the next version you send them ("will go with the next version" until then): until then, everything can be changed.
  • Reply: open a thread, reply; your reader reads your reply with the next version.
  • What becomes of the note: on a reader's note, choose Taken into account, Set aside (always with your reason), Later or Thanks, and reply in one sentence. The reader receives this outcome with the next version you send them, not before: a note taken into account shows them the passage before and after. They answer "Fine by me" (the note is closed) or "Let's talk again" (it reopens on your side, marked). When you rewrite a scene a reader had commented on, their thread says so ("Scene changed since V2"): Taken into account in one move, or Not yet.
  • Done: on your own comments, mark a thread as done once it is settled; it can still be read ("Show done ones too").

If the commented passage disappears from the text, the comment stays, detached, with its quotation.

In Write's list, a dot marks the scenes that have open comments, and those changed since the last sent version.

A scene's history

In Write, under a scene's comments, "The scene's history" opens its timeline: its text in each sent version, then today, with the changes marked, and everything the readers and you said about it, version after version.

Compare two versions

Share › Documents › Screenplay, Compare bar above the pages:

  1. From: a sent version. To: another sent version, or the current state.
  2. "Compare": scenes changed, added, deleted or moved are marked on the pages, with the details of the text (additions highlighted, removals struck through).
  3. "Only what changed" hides the rest; "Close the comparison" goes back to the text.

Your readers have the same bar above their pages.

Delete a sent version

Deleting a sent version also deletes its frozen version: the links no longer open.

A mistake, something missing on this page? Tell us with the app's "Feedback" button.

Rémi Vauthrin - Legal notice (French) - Privacy (French)