Guides
People, roles and reviews
Invite people to the admin, give them roles per site, and let editors approve what authors and their agents publish.
People, roles and reviews
People reach Hollware through the admin at /admin/. They sign in with a passkey: there are no passwords.
Roles
A person has a role in each site they are a member of:
| Role | May |
|---|---|
| owner | everything, tokens and invitations included |
| editor | read, write and publish, and approve reviews |
| author | read and write; what they publish waits for an editor's approval |
A token never does more than the role of its person, as it is now: demoting someone takes the scopes away from their tokens at once.
In the admin, under People, an owner gives a member another role, or removes them from the site, with every token and app they had of it. A site always keeps one owner: make another person an owner before the last one steps down.
Invite someone
In the admin, under People, invite an editor or an author. You get a link, valid once and for seven days, where they set up their passkey. From the command line:
npx hollware invite --role author --remoteAn owner who needs a passkey on a new device gets a setup link with hollware invite --owner.
Reviews
When someone without content:publish calls publish, the entry is not published. A review opens instead, with the revision they asked for, and waits in the admin under Reviews.
An editor sees the diff against what is live and the verdict of the contracts, then:
- approves it: the contracts run again, as
publishruns them, and Hollware publishes that revision in the editor's name; - asks for changes, with a note the author and their agent read with
list_reviews: they save a new revision and ask again; - rejects it, with the reason (
reject_review): the change is not to be published at all, and the review closes asrejected. The entry stays as it was; to drop the draft too, restore the revision the site shows from its history.
A new revision of the entry cancels its pending review, and the author asks again: an approval is always of what the editor saw.
Your name
Each person changes their own name under Account: their revisions, reviews and comments show it. Nobody else can change it, an owner included. The same page renames their passkeys, such as "Work laptop", and removes one they lost.
Several sites
One person has one passkey for the whole deployment, and a role in each site. In the admin, switch sites from the header; an agent's grant is for one site, chosen on the consent page.