A website we can
keep building.

The first sign-in

1. If there is no owner account yet, the person installing the site runs npm run activate at the application root with Node.js 24 enabled. It creates a private, single-use activation key.
2. Open Account administration, enter that key and choose your name, username and a password of 12 to 128 characters. You do not need to share that password with the person helping you install.
3. An existing owner is preserved: activation does not change their password or create an account above them. An original manager from an older installation may have become the owner with the same credentials.

What each role can do

• Owner: manages all accounts and publications and can read applications, including managing managers.
• Manager: manages publications and other accounts and can read applications. Cannot change or delete the owner.
• Editor: creates, edits and publishes their own and other people’s entries. Cannot manage users or read volunteer applications.
• Creator: creates, edits and publishes only their own entries. Cannot edit other people’s work or read applications.

Invite someone to help with the website

In Account administration, open Users and choose Create user. Enter their name, username, role and initial password. Activate the account when they should be able to sign in. Permissions can change later. Deactivating an account ends its sessions while keeping its publications.

Your account carries through to your work

After signing in, you can move between the tools your role allows without entering a password every time. My account lets you update your name and credentials; changing a username or password requires your current password. Use Sign out when you finish on a shared computer.

If sign-in does not work

Check the username and whether the account is active. A manager or owner can help within their permissions. Running initial activation again does not recover an existing owner’s password. Passwords are not included in this guide or the release files.