Daniele
c14cbc3626
Nightly Build / build (push) Successful in 9s
Four gaps off the coverage map, written for the in-app assistant: - file-viewer.md — what each kind renders to, the live reload, editing a Markdown file and the conflict banner, git history mode, and why a `.tex` must be shown instead of a PDF built from it. - tasks-page.md — the four sections, disable-vs-delete, where each kind's result lands, and that there is no "new task" button because tasks are created in conversation. - profile.md — display name, language, password, and what an encrypted account means when the password is forgotten. - users.md — creating a member and the irreversible encryption choice, the directory profile that feeds the agents' prompt, deactivating vs deleting, and the per-person event-triage interval. Indexed in docs/index.md, cross-linked from files.md, tasks.md and access.md.
47 lines
4.6 KiB
Markdown
47 lines
4.6 KiB
Markdown
# Your profile (name, language, password)
|
|
|
|
Every member has a Profile page — the avatar in the top-right corner → **Profile**. It is short on purpose: four things, all of them about that person's own account. Nothing here is admin-only, and nothing here affects anybody else.
|
|
|
|
## What is on it
|
|
|
|
**Account** — username and role, both shown but **not editable**. They are the admin's to change, from the Users page. If someone wants a different username or a different role, they are asking the admin, not the page.
|
|
|
|
**Display name** — the name they want to be called by. This is the one every screen uses, and it is also the name **you** are given in your prompt: change it and you should start using the new one. Leaving it empty falls back to the username.
|
|
|
|
**Language** — either an explicit choice or "Group default (…)", which follows whatever the admin set for the instance. It applies straight away, no reload, and it is stored on the **account**, so it follows them to any browser and any device. Two things it does:
|
|
|
|
- it translates the interface, and
|
|
- it is passed to you as their **preferred language** — which is why answering in it is the default, whatever language the last message happened to be in.
|
|
|
|
**Change password** — a new password, typed twice. Whether the **current** password is asked for depends on the account, and that difference is not cosmetic: see below.
|
|
|
|
## Passwords, and what "encrypted account" means
|
|
|
|
At the moment an account is created, the admin chooses whether it is **encrypted**. That single choice explains most of what a user will find surprising later.
|
|
|
|
**An encrypted account** keeps its database sealed with a key that only their password opens. Its consequences, which are worth saying plainly when asked:
|
|
|
|
- Changing the password asks for the current one, and the current one must be right — there is no way around it, because it is what opens the seal.
|
|
- The change is instant even on a large history: the data is not re-encrypted, only the seal around the key is replaced. Nothing is lost and nothing has to be re-read.
|
|
- **The admin cannot reset it.** The reset button on the admin's page refuses encrypted accounts outright. If the password is forgotten, the conversation history and private notes are unrecoverable — not "hard to recover": gone. Say this honestly if it comes up; do not offer hope of a recovery path, because there is none.
|
|
- Nothing in their private space can be read while they are logged out, by anyone, the admin included.
|
|
|
|
**A non-encrypted account** is protected by a password too — logging in still requires it — but the database is not sealed with it. The practical differences: the admin *can* set a new password for them from the Users page, and the account is available to the instance's background work even when nobody is logged in.
|
|
|
|
**The choice cannot be switched afterwards.** There is no toggle anywhere that turns an existing account from one into the other, in either direction. A user who wants to change it is really asking for a new account, and that is the honest answer.
|
|
|
|
## What a user might ask
|
|
|
|
- *"Change my name."* — the Display name field on this page. Ask what they want to be called; you cannot change it for them, and you should start using it once they have.
|
|
- *"Speak Italian to me."* — the Language field settles it for good, across devices. Doing it *only* in conversation lasts as long as the conversation does.
|
|
- *"Change my username."* — not from here. It belongs to the admin's Users page.
|
|
- *"I forgot my password."* — non-encrypted: the admin can set a new one. Encrypted: nobody can, and the data behind it is lost. Which one it is, is the first thing to establish.
|
|
- *"Is my stuff private from the admin?"* — an encrypted account, while they are logged out, genuinely is: nothing normal use of the software offers can open it. That is a real promise about ordinary use, not a mathematical one about somebody who owns the machine and is willing to modify the software running on it. Say it that way — the honest version is what makes it trustworthy.
|
|
- *"What does the app know about me?"* — the display name, the language, and the directory profile the admin filled in (date of birth, sex, notes). The last of those is on the admin's page, not this one, and they are entitled to ask what it says: see [users.md](users.md).
|
|
|
|
## Related
|
|
|
|
- [users.md](users.md) — the admin's side: creating an account, the encryption choice, resetting a password, the directory profile the agent is told about
|
|
- [settings.md](settings.md) — the instance-wide default language this page's "Group default" follows
|
|
- [memory.md](memory.md) — what is kept about a person, and where private ends and shared begins
|