Teams

A team needs one draft that everyone is looking at, one world that every title agrees with, and an answer to "is this done?" that everyone can see. In Plotra the workspace holds the people and the projects. Members write in the same note at the same time, with cursors, comments and suggestions. One project can be the world that the others borrow their characters and places from. Stages of your own say who must approve a note and lock it when it is finished, and a changelog shows what changed since a release.

Start writing for freeEvery feature is on the Free plan. No card needed.

Set upCopy Anchor Link

1. Make a workspace for the team. Whoever creates it is its owner. Keep it apart from your personal workspace: every member of a workspace can open and edit every project in it. See Workspaces.
2. Invite the room. Under Settings → Members & invites, enter an address, pick Member or Admin and press Send invite. An invitation is good for 48 hours. See Inviting people to the workspace.
3. Decide who manages. Only the owner and admins can change a project's modules and workflow, share it, add review rules and cut a release. Make the leads admins.
4. Bring in outsiders by project. A freelance editor, a consultant or a beta reader is given one project by email, as Editor, Commenter or Viewer, and sees nothing else. See Sharing a project.
5. Set up the world. Create one project of the type Franchise / IP bible, which starts with World bible on. In each title's project, open Project settings → General and choose it under Shared world bible.
6. Make a template. Tick Offer this project as a template in its workspace on a project that has your folders, kinds, workflow and labels. New projects can then start in its shape. See Templates.

Typical workflowCopy Anchor Link

1. Build the bible. In the world project, give characters, places and factions their pages and mark what is Canon. See The world bible.
2. Start each title as its own project. A book, a season and a game each get a project of their own type, pointed at the shared world. Its pages appear in their Codex and link picker, read-only. See Shared worlds.
3. Choose a workflow. Under Project settings → Workflow, pick the preset Draft → In review → Approved → Locked or build your own stages. Tick Approval on a stage that needs sign-off and Locked on one that is finished. See Workflow.
4. Name the reviewers. Switch on Review & editorial, open Reviews → Rules and add a rule: a person must approve everything in a folder, everything with a tag, or the whole project. See Required reviewers and review rules.
5. Write together. Open the same note and type; text is merged as you go. Talk in comments, with @ to mention a member, and use suggesting mode for changes someone else should decide. See Writing at the same time.
6. Ask for review. In the note's Review section, choose the stage and press Request review. Each reviewer is notified and finds the note under Waiting for you. When the last one approves, the note moves to the stage by itself. See Requesting a review.
7. Lock what is finished. A note in a locked stage can be read and commented on, but changed only by its approvers: its required reviewers and the people who manage the project. See Locked content.
8. Cut a release. With Releases & reveals on, add the release in the roadmap. Then Reviews → Changelog → Cut release keeps a snapshot of every note. Later the changelog lists what was added, changed, removed and retconned since. See The changelog per release.
9. Keep up. The bell lists mentions, replies, review requests and decisions; the activity feed lists what changed in the project. Each person chooses a daily digest, an email for each one, or none. See Notifications.

Sizing the planCopy Anchor Link

A plan belongs to the workspace, not to a person, and nobody pays per seat.

Up to three people fit on Free. A room of four or more needs Pro, and so does a workspace whose world project and titles add up to more than 10 projects. A team that needs more than 25 members can arrange an Enterprise plan. See Plans and billing.

What to read nextCopy Anchor Link

Things to knowCopy Anchor Link

• A member can edit every project. A workspace role can't be narrowed for one project. To keep someone out of a project, don't make them a member: share the projects they should see one by one.
• There are no permissions on single notes or folders. Everything in a project follows the project.
• Reviewers and mentions go by the member list. A guest can't be named a required reviewer or mentioned with @, whatever their project role.
• Locks work without the module. A locked stage is enforced in every project. Review & editorial is what lets you name reviewers and record decisions.
• A shared world goes one level deep and must be in the same workspace. Only characters, locations and world entries are shared, not releases. Links into the world don't appear in backlinks or the graph, and the spoiler horizon doesn't apply to shared pages.
• Someone who can't open the world project sees its links as "Restricted note".
• Cutting a release needs someone who manages the project, and its snapshots count toward the workspace's storage.
• Word counts are for the project, not for each person. The Stats view's daily total includes everyone's words.
• Nobody can leave a workspace or change their own role. An owner or admin removes a member, and a project can't be deleted or archived.
• Open invitations use a seat until they are accepted, cancelled or expire.