Account Settings
This page explains the internal account surface for the shared rascher.online reader model.
The live protected account surface is:
https://rascher.online/account/
If your approved email can read the protected wiki today, your current invited-reader area is:
wiki
That means your approved email may read the protected GoingNinja manual on wiki.rascher.online.
1. What You Can See Here
The current lean account-settings scope is:
- which protected area you currently have
- first name and last name
- which email that approval is tied to
- when the account was registered
- when the account last signed in
- where account deletion starts
- which protected shell elements may reuse this session profile
The entry point is page-level, not bot-level:
- the protected wiki header shows the authenticated reader profile
- that profile opens the account-settings path on
rascher.online - the assistant keeps chat history only
The current protected area list is intentionally small:
| Area | Status | Meaning |
|---|---|---|
wiki |
active if you can read this page | invited reader access to the protected manual |
2. How Deletion Works
Deletion no longer starts on the public root entry surface. It starts from the internal account-settings path.
Use the protected account path above first. From there, the deletion flow continues through:
The deletion request still requires:
- first name
- last name
- email
That keeps the deletion request reviewable and aligned with the stored registry identity.
3. What This Does Not Mean
This page is not product member auth and not a general customer account center.
It is only the shared invited-reader account layer for:
- the protected manual today
- later protected preview surfaces when they are added
4. Relation To The Wiki Assistant
Account settings are not part of the chat bot.
The current shell split is:
- the wiki shell shows the authenticated reader profile in the page chrome and links to account settings
- the Mistral assistant keeps chat history and answer state
That keeps account management outside the bot while preserving conversation continuity inside the bot.