Settings
The settings are available under Settings in the menu bar.
Change password
This allows you to change your existing password. First enter your current password under Previous password, then the New password and once more under Confirm new password. If the two entries differ, the dialog cannot be saved. The requirements a password must meet are set by the administrator of the instance; the message below the input field states the rule in force. By default, a password has at least eight characters with at least one letter and one number. If the previous password is wrong, the change is rejected. After a successful change you remain signed in in the current session, including when you switched clients. All other browser sessions end at their next request. A security notice is sent by email and any pending reset code becomes invalid. Personal access tokens and AI-assistant authorizations remain in place; revoke them in AI assistants (MCP) if needed. A demo account cannot change its password. If you forgot your current password, use Forgot password on the sign-in page.
If the administrator tightens the password rule, your existing password may no longer meet it. In this case the Change password dialog opens by itself right after you log in and can only be closed once you have set a new, valid password.
Sign-in security
In the Sign-in security dialog you manage two sign-in methods that complement your password: passkeys and an authenticator app (TOTP). The password always remains; an account without a password does not exist. How signing in with these methods works is described in Register. Every change in this dialog, except renaming a passkey, ends all other browser sessions at their next request. You remain signed in in the current session. You also receive a security notice by email that names the event and the time, but never a code or a secret. Wrong passwords and codes entered in this dialog count toward the same lock as wrong codes at sign-in: after five errors within 15 minutes, GT accepts no further confirmation for your account for 15 minutes. Demo accounts see the menu entry but can neither register passkeys nor enable an authenticator app.
Passkeys
A passkey signs you in without password and without second factor: your device verifies you with fingerprint, face or PIN. A passkey is bound to the address of the instance. A fake sign-in page under a different address therefore cannot request it, which makes it safer than a password. The table shows for each passkey its Name, the date Created, the time Last used and whether it is Synchronized. A synchronized passkey was held at registration by a password manager that transfers it to your other devices; a passkey that is not synchronized exists only on the device where you created it. With Add passkey you first confirm with your password. While an authenticator app is enabled, you also enter one of its codes or a recovery code. Under Name you give the passkey a name of at most 40 characters, for example after the device. Your browser then asks for the device on which the passkey is to be created. If you cancel this browser dialog, the form stays open without an error message; for a new attempt enter the password and, if needed, a new code again, because the first confirmation has been used up. By default each user can have at most ten passkeys. With Edit you change the name, with Delete you remove a passkey. Neither requires confirmation with the password, because at most it removes an access. Also delete the passkey in your password manager or on your device, otherwise the browser keeps offering it although GT no longer accepts it. If a hint appears instead of the table, passkeys are not available on this page. Passkeys require that the administrator has configured the public address of the instance with a host name and HTTPS, and that you opened GT under this address. Passkeys do not work through an IP address. If the host name of the instance changes, all registered passkeys become unusable; the password remains valid and you can register new passkeys under the new address. In the phone application you can sign in with a passkey; passkeys are registered and managed only in the browser, in this dialog.
A passkey protects only the sign-ins made with it. Signing in with email and password remains possible. Your account is protected against a stolen password only when an authenticator app is enabled as well.
Authenticator app (TOTP)
An authenticator app on your phone generates a new six-digit code every 30 seconds. Once it is enabled, GT asks for this code in addition to the password at sign-in. Any app that supports time-based one-time codes according to the TOTP standard is suitable. The dialog shows whether the app is Enabled or Not enabled and, for an enabled app, the number of Recovery codes left. Setting it up takes four steps:
- Choose Set up authenticator app and confirm with your password. If an app is already enabled, also enter one of its codes or a recovery code.
- Scan the QR code with the app or enter the Secret manually. The app lists the entry under the name of the application and your email address.
- Within 10 minutes enter the current Code of the authenticator app and choose Enable. After 10 minutes the setup expires and you start again.
- GT now shows ten recovery codes. They are shown only this once. Take them with Copy codes and keep them in a safe place, separate from the phone.
Each recovery code replaces an app code once, in case you do not have your phone at hand. When one is used, you receive a security notice with the number of codes left. An app code can also be used only once. An app that is already enabled stays in force until a new setup is completed with Enable. A cancelled or expired setup therefore does not weaken your protection. When you change your phone, simply set up the app again. If the setup was started again in a second window, only the newest QR code counts. With New recovery codes you replace all previous recovery codes, for example when only a few are left. This requires a current code of the app; a recovery code is not accepted here. The new codes are again shown only once. With Disable authenticator app you turn off the second factor. This requires your password and an app code or a recovery code. The recovery codes are deleted as well.
Keep the recovery codes carefully. A password reset by email does not remove the authenticator app. Without app and recovery codes you can still sign in with a passkey, if you have one, but you cannot disable the app yourself. The second factor can then only be removed by an administrator, see User Settings.
Change nickname and country/language
This dialog adjusts three personal properties. The Nickname is between 2 and 30 characters long and must be unique on the instance; if it is already taken, the change is rejected. Language and country selects the language of the user interface and at the same time the country-specific format of numbers and dates. Entity ownership visible highlights in shared data, such as instruments or stock exchanges, the entries you created yourself; in tables they appear in bold, for example. After saving you are logged out. The changes take effect from your next login.
Language-model keys
Use Language-model keys to manage providers for AI-assisted suggestions for your custom fields. Keys belong to your home tenant. Requests made with these keys are billed by your provider. The administrator determines which providers are available; Ollama uses the instance’s hardware and must be explicitly allowed. Choose Add provider, select a provider and optionally enter a model. Leaving the model empty uses the default shown in the table. Lower numbers under Order of evaluation are tried first. Each provider can have one entry, with a default limit of four entries overall. Clear Active to skip a provider without deleting its key. Daily query limit caps the requests per UTC day over this key and thus your costs; empty means no limit. When the limit is reached, GT tries the next provider in the order, and a run stops only when every key has reached its limit. The column Requests today shows the use of the current day, failed attempts included. Independently of this, the instance limits the requests of each user per day to protect its computing time. Keys are stored encrypted. The table shows only their last four characters under Key ending. When editing, the key field shows the stored key ending as a placeholder, because the key itself is never returned to the browser; leave the field empty to keep the saved key. Test key checks only the selected entry, including inactive entries. The test counts against the query limit of the key and your personal daily limit of the instance and shows provider errors such as an invalid key, missing credit or an unavailable model. The menu entry is hidden and key management is blocked while using a simulation environment or a managed tenant. AI requests in those contexts still use your home tenant’s keys. Keys are excluded from exports and tenant transfers; enter them again on a new instance. Deleting the account removes the home tenant’s keys.
AI assistants (MCP)
With this menu item you allow an AI assistant such as Claude Code or ChatGPT to read your portfolios. It appears only when the administrator has opened the MCP server. The description is under AI assistants (MCP).
Export personal data
You can export your data at any time and then import it into a new MariaDB Grafioschtrader schema. With this procedure you can say goodbye to a shared GT instance and start a new personal instance of GT or edit or analyze the newly created database yourself with the appropriate tools.
The export is intended as a migration aid and is deliberately kept small: it contains everything that cannot be re-obtained and leaves everything reproducible to the data providers, which supply it again after the new instance is started for the first time.
Content of the export file
The export is downloaded as the file gtPersonalData.zip and contains three files.
- The file
gt_ddl.sqlcreates the empty database schema. - The file
gt_data.sqlcontains your actual data. - The file
broken_history_connectors.txtlists those still-active instruments whose connector for historical prices no longer works. This file is always present; if no such instruments exist, this is noted accordingly inside it.
What is exported
In addition to your personal data, most shared data is exported regardless of ownership. Always included are your structure (portfolios, accounts, transactions, watchlists, standing orders, correlations and transaction imports), the instruments you use together with your private securities, the currency pairs you need, and the dividends and splits. The structure also includes rule based trading with its hierarchy, the strategies and their settings, the rebalancing recommendations and the state of running strategies. The instruments used there are treated like those of a watchlist and are exported together with their dividends, splits and derived instruments. Shared reference data such as stock exchanges and trading calendars, asset classes, tax tables, the data-provider definitions and the global settings is exported as well.
The historical price data is exported only when it cannot be re-obtained: for instruments that are no longer active, for currency pairs, for risk-free-rate instruments, for the preserved legacy price archive and — newly — for still-active instruments whose connector no longer delivers prices. You will find the latter in the file broken_history_connectors.txt.
After the import, the historical prices of still-active instruments are re-obtained; they are loaded by the connectors a few minutes after the back-end first starts. The current daily or intraday prices are fetched live anyway, and your holdings are recalculated from the transactions during the import. Messages, the alarm messages of the strategies and the internal task list are not exported. Neither are the simulation environments together with the results and the event log of their historical replays. Grafioschtrader generates these itself; in the new instance you get them back by running the simulation again.
The following table summarises what the export contains.
| Data | Included in the export? |
|---|---|
| Personal structure, transactions, watchlists | Yes |
| Your own and private instruments, currency pairs | Yes |
| Dividends and splits | Yes |
| Rule based trading: hierarchy, strategies, recommendations and their instruments | Yes |
| Shared reference data (exchanges, asset classes, providers, settings) | Yes |
| Historical prices of inactive instruments, currency pairs, legacy archive | Yes |
| Historical prices of active instruments with a broken connector | Yes (new) |
| Historical prices of active instruments | No – reloaded after the import |
| Intraday / daily prices | No – fetched live |
| Holdings / positions | No – recalculated from transactions |
| Simulation environments, replay results and event log | No – restored by running the simulation again |
The historical price data of an instrument is not exported if it is still active at the time of export plus one month; it is loaded by the corresponding connectors a few minutes after the back-end of the new GT instance is started for the first time. An exception are still-active instruments whose connector for historical prices no longer works: their prices are exported as well, because otherwise they could not be restored.
From export to new instance
The following diagram shows the entire flow from the export to the running new instance.
flowchart TD
A[Trigger export in GT] --> B[gtPersonalData.zip]
B --> C[gt_ddl.sql – empty schema]
B --> D[gt_data.sql – your data]
B --> E[broken_history_connectors.txt – report]
C --> F[Create schema in new database]
D --> G[Import data]
F --> G
G --> H[Start back-end for the first time]
H --> I[Connectors load missing historical prices]
H --> J[Holdings recalculated from transactions]
I --> K[Running personal GT instance]
J --> K
Loading the historical prices requires the API keys of the connectors to be entered in the new instance, and it can take a long time. What to observe is described on the page Historical prices after the import.
Import export into database
If you want to process the export further according to your needs, you can proceed as follows. In the following the database grafioschtrader_s and not grafioschtrader is mentioned.
# Unzip file gtPersonalData.zip
unzip gtPersonalData.zip
# Create the database with your desired password for grafioschtrader
mysql -u root -p -e "create database grafioschtrader_s; GRANT ALL PRIVILEGES ON grafioschtrader_s.* TO grafioschtrader@localhost IDENTIFIED BY 'YOUR_DB_PASSWORD'"
# Create GT database schema, the password from above ('YOUR_DB_PASSWORD') is requested
mysql -ugrafioschtrader -p --default-character-set=utf8 grafioschtrader_s < gt_ddl.sql
# Import of personal data, the password from above ('YOUR_DB_PASSWORD') is requested
mysql -ugrafioschtrader -p --default-character-set=utf8 grafioschtrader_s < gt_data.sql
# MariaDB-InnoDB has an error, see MDEV-28327, hence the following command:
mysqlcheck -p -a grafioschtraderYou can evaluate or edit the GT database with phpMyAdmin, for example.
Use export as new GT instance
As mentioned, you can use your exported data as the basis for a new GT instance. To install GT, follow the wiki on GitHub. After installation, the export can be imported.
# Stop Grafioschtrader service if it is running
sudo systemctl stop grafioschtrader.service
# Unzip file gtPersonalData.zip
unzip gtPersonalData.zip
# Delete the existing database
mysql -u root -p -D grafioschtrader -e "DROP DATABASE grafioschtrader"
# Create the database with your desired password for grafioschtrader
mysql -u root -p -e "create database grafioschtrader; GRANT ALL PRIVILEGES ON grafioschtrader.* TO grafioschtrader@localhost IDENTIFIED BY 'YOUR_DB_PASSWORD'"
# Create GT database schema, the password from above ('YOUR_DB_PASSWORD') is requested
mysql -ugrafioschtrader -p --default-character-set=utf8 grafioschtrader < gt_ddl.sql
# Import of personal data, the password from above ('YOUR_DB_PASSWORD') is requested
mysql -ugrafioschtrader -p --default-character-set=utf8 grafioschtrader < gt_data.sql
# MariaDB-InnoDB has an error, see MDEV-28327, hence the following command:
mysqlcheck -p -a grafioschtrader
# Start Grafioschtrader service if it exists
sudo systemctl start grafioschtrader.serviceThe GT instance or source instance of the export must correspond to the same or lower version of the new GT instance or target instance.
Delete my data and the user account
You can delete your data together with the user account. After confirming this deletion action, you will be logged out of Grafioschtrader. All your simulation environments and their results are deleted together with the user account.
As long as you still look after other people or share your portfolio with someone, the deletion is blocked. You must dissolve these connections first. If, as an advisor, you look after separate clients, you have to delete them beforehand; the procedure is described under Managing multiple clients. If you have given another person read access to your own portfolio, you have to revoke those shares beforehand; see Share read access to your portfolio. An overview of both functions is given under Shared access – basics. If you attempt the deletion anyway, Grafioschtrader tells you with a corresponding message what still needs to be deleted or revoked.
This action cannot be undone!!!