Managing users
Everything here lives in the Admin console, visible only to administrators.
Roles
| Role | What it can do |
|---|---|
| Administrator | Full access to the admin console: users, licensing, backups, updates, model and system settings. |
| Manager | Elevated access without full admin rights. |
| Member | Normal use: their own documents, collections and chats, plus whatever is shared with them. |
Adding a user
On a self-hosted server nobody can sign themselves up — that's deliberate. An administrator creates the account.
Admin → Users → Add user
Enter their name, email and role.
Copy the generated password
Chronicler generates a one-time password and shows it once. Copy it and give it to the person over a channel you trust. It isn't stored anywhere you can read it again, and it isn't emailed.
They set their own password
The account is flagged Must reset password, so their first sign-in forces a new one.
If you lose the generated password before handing it over, delete the account and create it again.
Access requests
When someone needs a document or collection they can't see, they can request it. Pending requests appear under Admin → Access requests (and are counted in Requests), where you approve or decline. Approving grants access without you having to find and re-share the item manually.
Suspending and removing
From Admin → Users, an account can be suspended — they can't sign in, but their documents and collections stay put — or deleted outright. Suspend when someone leaves and you still need what they filed.
Audit log
Admin → Audit log records administrative actions: accounts created and removed, roles changed, restores performed, licence activations. Useful when someone asks who changed what, and the first place to look if something is not as you left it.
What each user costs you
Your licence may cap the number of accounts. Admin → Licensing shows seats used against the limit; account creation fails once you're at the cap. See Licensing and activation.