Collaboration
A campaign is written by its whole table: game masters and players alike write articles and discuss them in notes.
Campaign Roles
Every member has a role. The hierarchy is Creator > GameMaster > Player > Spectator, and each level adds to the one below it.
Role | Adds |
|---|---|
Creator | Campaign settings — name, visibility, status, theme and custom CSS — plus invitations, role changes and removals |
GameMaster | Calendars and the campaign's Current Date, and membership of the |
Player | Writing: their own articles, images and notes, plus groups, static assets and import and export, and membership of the |
Spectator | Reading whatever their visibility allows, and reacting to it. In neither built-in group |
The Creator adds members from Settings → Invite, searching for them by username and choosing a role. They are members straight away, and start following the campaign.
A role carries its group with it. Promote a Spectator to Player and they are in players from that moment; demote a GameMaster and they leave gm. The two built-in groups are the roster seen from the visibility side.
Article Ownership
Every article has one author, set at creation and shown on the article and in overviews. The author alone edits it and decides who reads it, and the me visibility target always means them. Ownership cannot be transferred.
Content Belongs to Its Author
Whatever the roles say, a member's content is their own. Not even the Creator can edit, delete or withdraw another member's article, note, or image.
The Creator's only lever is membership. Removing a member can hide everything that member wrote, all at once, but cannot edit any of it.
Notes
Notes are threaded discussions on an article: questions, clarifications, theories, plot hooks. They live under the article they discuss.
Only a note's author can edit or delete it, and notes keep no edit history.
What you can write
A note is Markdown, the same as an article. Headings, lists, tables, code, links and images from the campaign's gallery all work, and so do the formatting blocks: box, quote, columns, timeline, image and secret. Auto-linking runs on notes too, so naming an article in passing links to it.
The visibility directive is the only one a note reads. Any other directive is a validation error: it would describe an article rather than a comment on one. Unlike an article, a note needs no # title.
Visibility
A note declares its own visibility in its content, with the same targets as an article: everyone (the default), a group, or me.
The directive covers the whole note. Anyone the note doesn't address finds it in neither the article's Notes list nor the campaign's Notes feed. To restrict only part of a note, use a secret block; the rest stays open:
A note reaches the people it addresses who can also read the article. You never need to restate the article's visibility, and a note can never show an article to anyone new. A reply works the same way against the note above it. A thread is two levels deep: a reply cannot itself be replied to. The full rules are in Secrets.
The reply count on a note counts the replies you can open, so a thread never advertises a reply and then withholds it.
Campaign Notes feed
The Notes tab in the campaign navigation collects every note you may read, across all articles, sorted by latest activity; a new reply bumps its thread to the top. The feed is read-only: to reply, follow the card to its article.
Leaving and Removal
Because content belongs to its author, the only thing a campaign can govern is who is in it.
Any member can leave, from Settings → Leave campaign.
The Creator can remove any member, from Settings → User roles → Remove.
The Creator cannot leave. The campaign is theirs. To put a finished campaign to rest, set its Status to Concluded; to leave it behind entirely, export your work and delete the campaign.
When a member leaves or is removed, their campaign alias, secret-reveal preference and group memberships are deleted. A hand-made group they owned passes to one of its members who can still write, or to the Creator if it has no such member. Demoting someone to Spectator hands on their groups the same way. The gm and players groups are owned by nobody and pass to nobody. Everything the departing member wrote stays where it is, unless it is withdrawn.
Withdrawing
Withdrawing hides something you wrote without destroying it. A withdrawn item leaves the lists, search, the activity feed, the gallery, the map and automatic linking, but keeps its content, its key and its revisions, so restoring it brings back exactly what was there. An image can also be deleted outright, by its uploader alone.
Where | |
|---|---|
Article | Control panel → Withdraw article |
Image | Control panel → Withdraw image |
Note | Withdraw, beside Edit and Delete |
Replies to a withdrawn note go out of view with it. They render nested under their parent and have nowhere else to appear. Nothing of the replier's is deleted.
Who can withdraw and restore
Anything you wrote is yours to withdraw, one item at a time, whenever you like. Show withdrawn, in the sidebar's quick actions, brings your withdrawn work back into view, badged and with a Restore button.
Only one flow withdraws a member's work for them. The leave and remove dialogs have one checkbox, also hide everything they wrote here: the member ticks it on their way out, or the Creator ticks it when removing them. It takes every article, note and image that member wrote in the campaign, all of it or none.
Restoring is the author's right alone. Rejoin the campaign and Settings shows what of yours is withdrawn, with one button to bring it all back.