Chapter 43 · Working With Others
Share Links, Reviewers, and Editors
Sharing in Storskarvia is one document at a time, by link, in one of two roles. There is no invitation email, no team account, and nobody to add to a seat. You mint a URL, send it however you like, and the first person who signs in with it holds it from then on.
Minting a link
Open the document and find Share ▾ in the editor toolbar, on the right, beside Versions ▾ and Export ▾. It appears only on a document you own. Open somebody else's shared document and there is a role chip in that spot instead.
The menu holds two buttons and the list of links you have already made:
- New reviewer link — suggests & comments
- New editor link — full edit
Click one and the link is minted straight away, copied to your clipboard, and the status area beside the title reads Invite link copied. There is no dialog and no confirmation step, because a link nobody has claimed yet does nothing. Every click makes another one, and a document can have as many as you need.
The link has the form storskarvia.com/share/ followed by a long random token.
Treat it as the credential it is: until somebody claims it, anyone holding it can.
A share is one document, not the project. The document picker, the research shelf and the Story Bible are never sent to a collaborator's page, so a reviewer of one chapter does not receive every character, place, and secret in the book. To show somebody three chapters, mint three links.
What each role can do
An editor is a co-writer. A reviewer is a reader with a pen that only writes in the margin.
| Reviewer | Editor | Owner | |
|---|---|---|---|
| Read the document | Yes | Yes | Yes |
| Comment and reply | Yes | Yes | Yes |
| Type into the draft | As suggestions only | Directly | Directly |
| Bold, headings, lists, tables, images | No | Yes | Yes |
| Accept or reject a tracked change | No | No | Yes |
| Title, fonts, layout, scene numbers, title page | No | No | Yes |
| Fact-check, continuity, Researcher | No | No | Yes |
| Versions and restoring | No | No | Yes |
| Where the document is stored | No | No | Yes |
| Export the document | Yes | Yes | Yes |
| Mint and revoke links | No | No | Yes |
The staff buttons are hidden for both collaborator roles, because a check is spent from the owner's allowance and there is no polite way to let a guest spend it. Chapter 41 covers how that allowance is counted. Other owner-held controls are disabled rather than removed, carrying the tooltip The document owner sets this., so you can at least see the control exists.
What the other person sees
Opening an invite link does one of five things, depending on who is holding it.
| Situation | What happens |
|---|---|
| Not signed in | Sent to the sign-in page with the invite remembered. Signing in lands them on the document. |
| No account yet | The Create an account link beside the sign-in form carries the invite with it. Create the account and you land on the document. |
| First signed-in person | The link becomes theirs. The document appears under Shared with you on their Studio page with the role and your address. |
| Anyone after that | This invite was already used by someone else. Mint a second link. |
| You, the owner | Straight to the document. Opening your own link never claims it. |
Signup is capped during the founding beta, so a reviewer arriving when the seats are gone reaches the waitlist. The invite keeps working and does not expire while they wait.
Once they are in, the editor toolbar carries a chip reading their role and your name, for example reviewer · mara's doc, with your full address in its tooltip.
Why a reviewer's edit gets refused
The reviewer role is enforced on the server, not only in the buttons. On every save from a reviewer, Storskarvia compares the structure of what arrived with the structure of what is stored, with suggestions resolved away: inserted text removed, and insertion, deletion and comment marks stripped off. If anything else moved, a word, a heading, a bold run, a link, a paragraph split, the save is refused with:
Reviewers can only suggest — turn your edit into a suggestion (Suggest is on for you).
This is why the editor forces suggestion mode on for a reviewer and disables the toggle, and why the formatting buttons carry the tooltip Reviewers suggest and comment. The owner formats and restructures. Formatting is not recorded as a suggestion: the change tracker marks ranges of inserted and deleted text, and a bold run is a different kind of change. One click on B would be an ordinary structural edit, and every save after it would land on the wrong side of that guard.
The plain-text copy of the document is also derived on the server rather than taken from the
browser, so a reviewer cannot quietly change what a .txt export or a fact-check reads
while leaving the document itself alone.
What stays yours
Some things are the owner's because they rewrite the document, others because they cost money or name a real address.
- Accepting or rejecting a tracked change. The buttons are not rendered for a collaborator at all. Resolving a suggestion rewrites the text, which is a decision, not a note.
- Versions. The Versions ▾ menu does not appear for a collaborator, and a PDF with revision stars is refused with Revision marks are for the document's owner: those marks are computed against your private history (Chapter 7).
- Production tools. Locking pages, issuing a revision, and omitting a scene change what a production office reads as an address, so they are yours alone. Chapter 17 covers them.
- Storage. Where the document lives is a decision about your Dropbox or your Drive, so the storage controls are hidden for collaborators. Chapter 3 explains the model.
Comments are the exception, deliberately. A comment belongs to whoever wrote it: its author or the document owner can edit it, resolve it, or delete it, and nobody else. Deleting a top-level comment deletes its replies with it, so read a thread before you clear it.
Exports stay open to both roles. A reviewer you asked for notes usually wants a PDF to write on, and the watermarked draft PDF is there for exactly that.
Copying, revoking, and changing a role
The Share menu lists every link on the document: the role, then either the address of whoever claimed it or the word unclaimed, the URL in a read-only field, and a Copy and a Revoke button.
A link's role cannot be changed after it is minted. If you sent an editor link and meant a reviewer link, revoke it and make the one you meant.
Revoking asks you to confirm, and the warning is literal: Revoke this link? The collaborator loses access immediately. Their next request is answered as if the document does not exist, and it leaves their Studio. Their comments and suggestions stay in your draft.
If a revoke fails, the status area reads That link was not revoked and the person still has access. Reload the page and revoke again.
When a link does not work
| What you see | What it means |
|---|---|
| This invite link is no longer valid | The token is wrong or the link was revoked. Repeated misses from the same place are limited to twenty an hour, so nobody can sit and guess tokens. |
| This invite was already used by someone else | Somebody claimed it. One link, one person. Mint another. |
| Signed up and landed in the Studio | The account was created somewhere other than the invite, so there was nowhere to send you. Open the invite link now that you are signed in. |
| That invite link was not created | Nothing was minted, and nothing was copied. Try again rather than pasting whatever is on your clipboard. |
| A shared document vanished from the Studio | The owner revoked the link, or you are signed in as a different account. An invite belongs to the account that claimed it. |
| A greyed control, tooltip The document owner sets this. | Working as intended. That setting is stored against the owner's document. |
Suggestion mode and comments, where a reviewer spends their time, are the next chapters in this part. Getting the marked-up draft back out as a PDF, a Word file, or a Final Draft script is Part VIII.
Updated 2026-09-19 · Full contents · Something wrong or missing?