Sharing a Project with Co-Owners

A co-owner works on your project as if it were theirs. They can edit the project, its components and its table setups, and host playtests from it. You stay its creator: only you can delete the project or change who owns it.

Co-ownership needs Pro on both sides.

Inviting a Co-Owner

1. Open the project and expand the Owners section.
2. Type the email your co-owner signs in with and click Invite co-owner.

They get an email, and the invite waits at the top of their My Projects page with Accept and Decline. If you invite the same person again, they get at most one email a day. Nothing is shared until they accept. While it waits, you can cancel it from the Owners section.

A project can have up to 5 co-owners. Invites that are still waiting count toward that.

What Co-Owners Can and Can't Do

When an owner joins a room another owner opened for the project, they join as co-host. Only the owner who opened a room can close it. Rooms opened from a share link, or by someone else from a public setup, work as they always have.

When Pro Ends

• If your Pro ends, every co-owner loses access, and the project leaves their My Projects. That includes the table setups, replays and print layouts they made for it: those stay with the project. It all comes back for them when you renew.
• If a co-owner's Pro ends, only they lose access. The Owners section marks them No access until they renew.

Leaving, or Removing Someone

A co-owner can Leave from the Owners section, and you can Remove any co-owner there. Table setups, replays and print layouts they made for the project stay with it and become yours. Rooms they opened for the project close, and a page they still have open stops showing the project's changes. A competition entry they made stays theirs.

A game can be entered in a competition once, whichever owner enters it. Only the owner who entered it can change or withdraw the entry, and its current owners can't rate it.

Working at the Same Time

Two people can edit the project at once without losing each other's work.

• Only what you changed is saved. A field you didn't touch is never written, so your save can't put back an old value someone else just replaced.
• When you both changed the same thing, nothing is saved yet. You see both versions and who made the other change. Choose Keep theirs or Use mine for those fields; your other changes go through either way.
• On the project's edit page, a clash brings you back to the form with a note and your version still filled in. Save again to replace theirs.
• In the Deck & Stack Builder, if someone changed the deck while you had it open, Save becomes Save anyway.
• Overwriting a table setup that someone saved after you opened the list asks first, with Overwrite anyway.
• In a text rulebook, a page someone else saved meanwhile is named in the editor. Save again to replace theirs.
• A few things are saved whole, so the last save wins: a die's faces, a spinner's sections, a pack's tiers, and Save to Project Component in a room, which writes the Table Component to its Project Component exactly as it sits on the table.

Seeing Each Other

On the project page, a small note in the bottom-left corner shows who else is on the project, and which card they have open ("Dana is editing Goblin"). When someone saves a change, you get a note naming it, with Show changes to bring the list up to date. The list never refreshes on its own, so nothing you're halfway through is swept away. When someone accepts an invite or leaves, you're told, and the Owners section updates by itself.

Files and Storage

A shared project's files live in your storage, in that project's own folder, and count toward your storage. When a co-owner picks an image, the file picker has two tabs:

• Project files: the project's folder. They can upload, rename and delete there, but can't see the rest of your files.
• My files: their own storage. A file they pick from here is copied into the project's folder, so the project never depends on their private files.

Images a co-owner adds in a room, rulebooks they import, and Tabletop Simulator imports they run are stored in your storage too. A link pasted straight to a file in a co-owner's own storage is refused, for component images and for the project's logo and backdrop; they pick it from My files instead, so it is copied in.

Custom Masks

Every owner's custom masks work on a shared project. In the shape lists, a mask someone else made shows their name, like "Swoosh (Dana)". Only the person who made a mask can edit or delete it, in their own Mask Editor (Tools menu).

If a co-owner leaves, is removed, or deletes a mask the project uses, a copy of it goes into your mask library first and the project's pieces and saved setups switch to the copy, so nothing loses its shape.

Related: Projects · My Files · Plans & Pricing