Who can do this?
Only the owner can invite, revoke and restore access. The owner or the person concerned files a removal request for their own entry, and the other side confirms. Owners and co-authors see the list.
Managing co-authors
Co-authors write along with you: you invite them, set the book scope and can revoke access.
What is it for?
Co-authors get read and write access to the shared books of a project, including the characters, locations, factions and rules that appear in them, not just the chapter text. You reach the page in the “Collaboration” group through the “Co-authors” tile. Each entry shows DisplayName#Tag, a status chip, the date “since …” and the book scope.
When inviting, you choose “Existing user” or “Invite by email” and decide whether the person sees the whole project or only individual books. Before sending, a confirmation dialog explains what the invitation means: write access to related worldbuilding objects, possible spoilers and the retcon confirmation for lore-locked books.
You can revoke and restore access. Permanent removal only happens jointly: one side files a request, the other confirms. Inviting co-authors is part of the Vastitas studio.
How it works
-
In the “Collaboration” group, open “Co-authors” and choose “+ Invite co-author”.
What you see afterwards: The “Invite co-author” dialog opens.
-
Choose “Existing user” with DisplayName#Tag, or “Invite by email”.
What you see afterwards: The person is entered.
-
Under “Access to which books?”, choose “Whole project (including books created in the future)” or individual books.
What you see afterwards: The book scope is selected.
-
Read the notes, tick “I have read and understood this” and choose “Invite”.
What you see afterwards: The invitation is sent and the entry appears with the status “Active”.
Your data
People appear everywhere as DisplayName#Tag, and you do not see other people’s email addresses in the app. Contributions remain after access is revoked or removed. In a dispute, an objection remains possible through user administration.
Limits
Inviting requires an active Vastitas studio for the owner, and a trial period is not enough. What someone has already seen cannot be taken back after access is revoked. There is no separate role for editors only; editorial access shares serve that purpose.
Frequently asked questions
Can one side remove a co-author alone?
No. The “Remove permanently” request must be confirmed by the other side with “Confirm removal”. The requester can take it back with “Withdraw request”. If the other side does not respond, Illumentis offers “Escalate to admin”.
What is the difference between “Access revoked” and “Resigned”?
The owner triggers “Access revoked”, and it can be undone with “Restore access”. “Resigned” applies when the person has left the project themselves.
What happens if a book is lore-locked?
The co-author can still change sealed facts, but must confirm this as a deliberate retcon. The confirmation is logged, just as it is for you.