Collaboration — writing as a team

Invite members to a project to work on it together (works for server-saved projects). Create an invite link from the Collaboration card on the project home and share it — there's no email sending yet, so send the link yourself. The planning screen has no invite button (invites work per project, so they live in one place: the project home).

When you're working alone, open that screen with Invite teammates; once you have members, it's Manage members (visible only to owners and admins). Changing permissions after inviting and assigning the writer are all done on this screen too.

An invite link is shown only when you create it. It isn't stored, so once you close the screen you can't bring that link back. If you missed it, press New link next to that person in the Awaiting acceptance list — you get a new link with the same permissions, and expiry resets to 7 days out. But links you sent earlier stop working from that moment, so if you already shared one, send the new link again.

• Choose permissions by "what they can do": Co-create (edit planning, script, and production,

with or without AI generation) · Review (comment, approve, request changes) · View (read and comment) · Admin (includes managing members).

• A project's AI credits come out of the project owner's wallet — the production company pays and teammates

use them. So the "AI generation" permission lets someone spend the owner's wallet, and only the project owner can grant it (for team projects, the team's billing account and team admins too). Admins can invite members and give editing access, but not AI generation. Image and video generations requested by any member show up in the "Tasks" panel for every member of that project, and ones requested by someone else are marked "Requested by <name>" (only the requester can cancel). Owners and admins can see this month's usage per member in the collaboration overview on the project home. When the project runs low on credits, members see no balance — just a prompt to "ask the owner to top up."

• There is one set of story settings and one co-writer conversation per project — invited members see and continue

the same story settings and the same co-writer conversation.

• Only one person, the "writer," can edit planning, the script, story settings, and the co-writer. If several people

edit the same manuscript and AI conversation at once, the story's premises diverge. The project owner picks the writer from the team with Assign writer in Manage members, and can hand it to someone else at any time (the default is the owner who created the project). Teammates who aren't the writer can still read, comment, review, and do AI image and video generation, video planning, and production — only the writing itself is handled by one person.

• When something looks read-only, the reason is shown with it — No edit permission. Note that this message appears

both when you lack permission and when you're not the writer. If you have Co-create permission and the script still looks locked, it's not your permission — someone else is the writer. Ask the owner to assign you.

• Task assignment: in "Team tasks" on the project home, [Assign task] lets you pick the episode, task type

and assignee. The task type defaults to "Video production". Every member is listed; people who can't take the task are dimmed with the reason — "Write / revise script" goes only to the lead writer, and "Video production" only to people with Co-create access (Review and View access can't be assigned). To give a script task to another teammate, change the lead writer with "Make writer" first.

• Review flow: when you request a review from the episode stage bar, someone with approval rights (Review or higher) responds with approve or

request changes. The reason for a change request stays in the review dialog and is sent to the requester as a notification.

• Scene comments: exchange feedback scene by scene in the editor's comments panel. Unresolved

comments show as badges — counts appear in the episode list on the left and on the comments button, so you can see which episodes have feedback piling up without opening the panel.

• Output comments: on an image or video card in the archive, open the ⋯ menu and choose "Comments" to leave feedback on that

output. For video, press "Attach current position" while playing to pin the time to the comment, and click a comment's time to jump there. The count of unresolved comments shows on the menu item. When you request changes in a video review, the reason is also saved as a comment on that video together with the playback position.

• Telling shared projects apart: projects you've joined by invitation get a Joined badge in the list and the project switcher.

Participants can't copy characters from someone else's project into their own library or export the full text (owner only).

• Leaving a shared project: press Leave project under Share on the project home, and the project

disappears from your list. To come back, you need a new invite. The project and manuscript aren't deleted — they stay with the owner and other members, and the owner and admins are notified. The project owner can't leave — that would leave a project with no owner. Transfer ownership to another member or delete the project.

• Transferring ownership takes two steps: an offer, then the recipient's acceptance. When the owner

presses Transfer on a member in Manage members, only an offer is sent, and that member's row shows Awaiting acceptance with Cancel. The recipient gets a notification, and when they open Members on the project home they see what will change along with Accept and Decline. Ownership moves only on acceptance; offers expire after 7 days (sending a new one cancels the previous one). Once accepted:

• All AI usage in the project, by anyone, is charged to the new owner's credits.
• The previous owner stays as an admin but loses AI generation — the new owner can give it back.
• The lead writer stays the same. If the previous owner was the lead writer, their co-writer usage is

also charged to the new owner, so change the lead writer after accepting if you don't want that.

• If another member is editing the same episode, a notice appears at the top to prevent save conflicts.

Back to the guide contents