Build a shared workspace, invite collaborators, and decide who can read, edit, or manage each project.

When to use this

You’re co-writing a series, running a writers’ room, or pairing with an editor and you need everyone working from the same canon. Use teams when more than one person needs ongoing access to your projects, or when you want to share a single project with another group without giving them the rest of your work.

Teams vs project collaborators

PlotLens has a two-tier collaboration model. Pick the right one for the situation.

Team membership. A team is a workspace with members and roles. Members keep access to every project the team owns until you remove them. Use this for the people you write with day-to-day.
Project shares. A project share grants one team access to a single project at a specific permission level — independent of their role inside their own team. Use this when you want to hand a draft to an editor’s team or open one project to a partner studio without merging workspaces.

A user’s access to any project is the highest of: direct ownership, their role on the team that owns the project, and the permission level on any share that reaches them.

Teams overview screen showing members list and shared projects

Roles

Every team member has one of four roles. Roles apply to team management; project shares carry their own permission level (viewer, editor, or admin) that overrides the team role for that one project.

Role	What they can do
owner	Everything: invite, remove, change roles, share projects, change billing, delete the team. One per team. Cannot be removed and cannot have their role changed.
admin	Invite and remove members, change roles (except owner), manage project shares. Cannot delete the team.
editor	Read and write inside team projects and shared projects. No team management.
viewer	Read-only access to team projects and shared projects.

How to create a team

Open the team switcher in the top navigation and choose Create team.
Enter a team name. Add a description if you want one to show up on the team page.
Click Create. You’re added automatically as the owner.
Land on the team setup wizard. From here you can invite your first members or jump straight to creating a project.

How to invite members

Invitations go out by email and expire after 7 days.

Open Teams and select your team.
Click Members, then Invite member.
Enter the invitee’s email address.
Pick a role: viewer, editor, or admin. (Only the team creator is owner; new members can’t be invited as owner.)
Click Send invite. They get an email with a one-time link.
The invite shows up under Pending invitations until they accept, you revoke it, or it expires.

Invite member dialog with email field and role selector

When the recipient opens the link, they sign in (or sign up) with that email and join the team. They get the role you picked.

Project shares let one team work on a specific project at a permission level you choose.

Open the project you want to share.
Click Collaborators in the project sidebar.
Click Share with team and pick the team you want to give access to.
Choose a permission level:
- viewer — read-only
- editor — read and write entities, canon, and validations
- admin — full project control, including managing shares
Click Share. Members of that team see the project in their dashboard immediately.

Project collaborators page with share team dropdown and permission selector

Changing roles

Only the owner and admins can change roles.

Go to Teams → Members.
Find the member and open the role dropdown next to their name.
Pick a new role. The change takes effect right away.

The owner role is fixed — you can’t promote anyone else to owner from this menu. To hand off ownership, see Transferring ownership below.

To change a project share’s permission level, open the project’s Collaborators page and use the dropdown next to the team name.

Removing members

Go to Teams → Members.
Click the menu next to a member and choose Remove from team.
Confirm.

Removing a member deletes their team membership row. It does not delete any of their work or any projects. They lose access to team projects and to any shares that depended on team membership.

To leave a team yourself, use the same menu and choose Leave team. The owner cannot leave.

Transferring ownership

There is no in-app ownership transfer today. The owner role is immutable: only the original owner can delete the team or manage billing for it.

If you need to hand a team off, contact support and we’ll move it for you.

Plan availability

Teams and project sharing are paid features.

Free, Lite, Plus, Pro — solo plans. No team workspaces or project sharing.
Small Team — teams unlock here. Per-seat pricing, 3 seats minimum, up to 5 seats. Includes shared projects, team dashboard, comment threads, and activity log.
Studio — adds custom roles, canon versioning, BYOK, and full audit logs. Up to 20 seats.
Production — adds SSO/SAML, advanced audit logs, and SLA. Up to 50 seats.
Enterprise — unlimited seats, multi-property canon, dedicated infra, custom SLA.

If you try to use a team feature on a solo plan, you’ll see an upgrade prompt. Existing team data is preserved if your plan changes.

Limits & edge cases

Pending invites. A pending invite stays valid for 7 days. You can revoke it anytime from Members → Pending invitations — the recipient’s link stops working immediately.
Duplicate invites. Sending a second invite to the same email while one is still pending fails with a conflict. Revoke the existing invite first, or wait for it to expire.
Expired invites. After 7 days the link no longer works. Send a new invite — there is no resend.
Already a member. If you invite someone who is already on the team, the invite is rejected. If they click an old invite link after joining, they’re told they’re already a member.
Owner removal. The owner can’t be removed and can’t have their role changed. Self-removal is blocked for the owner.
Cascading shares. Removing a member only revokes their personal team membership. It does not touch project shares granted to other teams. Unsharing a project is a separate action.
Seat limits. If you’re at your plan’s seat cap, new invites are blocked until you remove someone or upgrade.
Read-only mode. If billing falls behind, the team enters read-only mode. Members keep access but can’t make changes until billing is resolved.

Common pitfalls

Confusing team roles with share permissions. A user’s role inside their own team has nothing to do with the permission level on a share you gave them. If your editor’s team is shared viewer on your manuscript, even their team’s owner can only read it.
Inviting people one project at a time. If the same group needs access to several of your projects, add them to your team instead of stacking project shares. It’s fewer moving parts.
Hand-off planning. Because there’s no self-serve ownership transfer, decide who should own the team at creation time. Account changes for the owner are harder to undo.
Pending invites count too. Pending invites can consume a seat slot. Clean up stale invites if you’re near your cap.