# Invitations and secret links Open Sharing from the project menu or library card. Only the project owner manages access. Invite an existing account for continuing membership, or create an expiring secret link for a guest. An invitation grants access to the whole project. A secret link can cover the whole project or one book, chapter, or scene. The link follows the live manuscript, so it does not preserve a separate review copy. Coordinate edits by scene. Fablewright handles save conflicts, but it does not provide real-time co-editing. ## Permissions | Role | Read | Comment | Write prose | Plan | Export | Recovery | Manage sharing | Delete project | | ---------- | -------- | -------- | ----------- | ---- | ------ | -------- | -------------- | -------------- | | Owner | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | | Co-author | Yes | Yes | Yes | Yes | Yes | Yes | No | No | | Reader | Yes | Yes | No | No | No | No | No | No | | Guest link | Per link | Per link | Per link | No | No | No | No | No | A reader uses Read-through, the read-only outline, and the feedback reading view. Readers cannot open the writing workspace or response queue. Co-authors can change prose and planning and use project recovery. The instance admin is a separate role. Being an admin does not grant membership in another writer's project. Someone with shell access to the server can still read its database and backups. ## Invite an account The recipient needs an account on the same instance. An invitation does not create one. Sign-up is closed unless the admin opens it, so ask the admin for an account first. To invite: 1. Open Sharing as the project owner. 2. Enter the account's email address. 3. Choose Reader or Co-author. 4. Submit the invitation. 5. Ask the recipient to open their library and accept it. The invitation appears in that library and expires after 30 days. The app does not email it. Declining grants no access. Acceptance adds the project to the recipient's library. The owner can change a member's role or remove access on Sharing. Each request reads the current membership. Removing access stops future reads and writes. It cannot erase prose already copied or displayed in a tab. ## Create a secret link A guest needs no account. Anyone who holds the link can use its permission, and the name a guest enters is not verified. First choose what the link opens: the whole project, one book, one chapter, or one scene. A book link includes its front and back matter. A chapter link includes every scene in that chapter. A scene link includes only that scene. A scoped link reveals only that part. Its title and its parent titles are visible; other books and chapters are not. The scope is fixed when you create the link. To change it, revoke the link and create a replacement. Choose one permission: - Read only shows the current manuscript. - Read and comment also accepts feedback and suggested replacement text. - Edit manuscript and comment also allows changes to scene prose. Choose when the link expires: after 1, 7, 30, or 90 days. Use the optional label to remember who received the link. A label does not restrict the link to that person. Create the link and copy it before you leave the page. The confirmation shows the saved permission and expiry. Copy link uses the clipboard. If the browser refuses clipboard access, it selects the field instead. The server stores a hash of the secret, so you cannot retrieve a lost link later. Create a replacement instead. A secret link exposes the live prose in its scope. A whole-project or book link includes front and back matter. Secret links do not expose notes, planning fields, deleted work, archives, or recovery history. Guests cannot change structure or membership. A guest sees feedback left through that same link. Project members can see all project feedback. ### Send and revoke safely Use HTTPS outside localhost. Choose the shortest expiry that fits the review, and send separate links when you need separate revocation. Do not post a link in a public issue or public chat. Ask the operator to omit query strings for `/s/` requests from proxy and access logs. The first request contains the secret. The app exchanges it for a scoped browser cookie and redirects to a clean address, but an upstream log can record it first. If a link leaks, revoke it before creating a replacement. Revocation stops the next request, including a pending guest save. It does not erase prose already on screen or downloaded. Changing the manuscript or making a new link does not revoke the old one. To change a guest's permission, revoke the old link and send a new one. If an expired or revoked link refuses a save, the guest must download or copy unsaved words before closing the tab. ## Give feedback Readers and guests with comment permission can select a passage and choose Comment on passage. They can also respond to a whole scene or chapter that is in the link's scope. A scene link cannot take chapter feedback. Suggested replacement text stays in feedback until a writer applies it manually. Feedback records the scene revision and a saved quotation. It is not a tracked position that follows every edit. If the scene changes, the response reports changed context. Missing or ambiguous passages can lose their highlight while retaining the quotation. The server refuses new feedback against an older revision. Reload the manuscript and select the passage again before submitting. A recovered feedback draft retains its earlier revision until you explicitly choose fresh context. ## Work through responses For owners and co-authors, Feedback opens on the Responses tab. The queue groups scene and chapter feedback in manuscript order. Open lists unresolved responses. All includes resolved ones. Open scene opens the scene in the writing workspace. Resolve removes a response from the open queue without deleting it. Delete permanently removes it after confirmation. Readers and guests cannot moderate feedback. A project accepts up to 10,000 feedback items. If it reaches that limit, delete unneeded responses. Reading shows the manuscript with feedback in place and an index for navigation. Owners and co-authors can switch to it from Responses. Readers always receive the reading view and do not see the queue tabs. ## Guest editing An editing link uses the same prose editor, retries, local recovery, and revision checks as account-based editing. It can change only the scenes in its scope. A changed save keeps the previous prose in scene history. Guests cannot browse that history themselves. Finish editing saves your changes before it closes the editor. If the save fails, keep the tab open and download the unsaved words. Avoid simultaneous changes to the same scene. A conflict asks which copy to keep. It does not merge the edits. Guest edits do not count toward a registered writer's daily goal. Guest names and link labels are not reliable proof of who wrote a change. There is no audit log that establishes a guest's identity. ## Ownership and leaving Only the owner manages sharing and project deletion. There is no standalone ownership-transfer control. Ownership can pass to a chosen co-author when the owner deletes their account. A live project with other members needs a co-author to take ownership before account deletion. Readers alone cannot receive ownership. Add a co-author or delete the project before leaving. Secret links alone do not make a project shared for this handover rule. The only remaining admin must appoint another admin before deleting their account. The only account on an instance cannot delete itself through the web. [The operations guide](operations.md#deleting-an-account) covers account deletion and shell recovery. ## Archives and backups Project archives include feedback, quotations, suggestions, resolution state, and author names. They exclude memberships, invitations, and secret links. Import gives feedback new identifiers and connects it to the imported manuscript without granting anyone access. Whole-instance backups keep the sharing tables. Restoring one can bring back access permissions from the backup's time, including a link revoked afterward if it has not expired. Review membership and links after an instance restore. For a review without access to deleted work or history, use a reading link, Word, EPUB, or PDF instead of a project archive. [The import and export guide](import-export.md) explains that distinction.